| Bug ID |
12697
|
| Summary |
Possible incorrect FCS checksum display on 802.11 packets
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14781 [details]
Possible fix for 802.11 FCS problem
Build Information:
TShark (Wireshark) 2.3.0 (v2.3.0rc0-165-g50b56c8 from master)
Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with libpcap, with POSIX capabilities (Linux), with libnl 3,
with GLib 2.48.1, with zlib 1.2.8, without SMI, with c-ares 1.11.0, with Lua
5.2, with GnuTLS 3.4.14, with Gcrypt 1.7.2, with MIT Kerberos, with GeoIP.
Running on Linux 4.6.4-1-MANJARO, with locale en_GB.utf8, with libpcap version
1.7.4, with GnuTLS 3.4.14, with Gcrypt 1.7.2, with zlib 1.2.8.
Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (with SSE4.2)
Built using gcc 6.1.1 20160707.
--
I think the FCS calculation for 802.11 packets may be checking against the
wrong
endianess as a result of commit ad6fc87d6 on git head.
I've attached a patch that fixes the problem for me, but am entirely unfamiliar
with the wireshark codebase, so this is probably not the best way of doing
this.
Apologies if this is a duplicate or I am mistaken:-)
You are receiving this mail because:
- You are watching all bug changes.