Wireshark-bugs: [Wireshark-bugs] [Bug 11204] New: The Aruba ERM Type 1 Dissector inconsistent wi
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 18 May 2015 14:48:38 +0000
Bug ID 11204
Summary The Aruba ERM Type 1 Dissector inconsistent with Type 0 and Type 3
Product Wireshark
Version 1.12.5
Hardware x86
OS Windows 8.1
Status UNCONFIRMED
Severity Minor
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter doug.wussler@fsu.edu 

Created attachment 13612 [details]
Screen shots showing FCS for Type 1 and absence of FCS for Type 3

Build Information:
Version 1.12.5 (v1.12.5-0-g5819e5b from master-1.12)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
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 GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built May 12 2015),
with
AirPcap.

Running on 64-bit Windows 8.1, build 9600, with WinPcap version 4.1.3
(packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz, with 8097MB of physical memory.


Built using Microsoft Visual C++ 10.0 build 40219

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
The Aruba ERM dissectors for Types 0 and 3 make a different decision for
handling the FCS than the dissector for Type 1 even though there is no
difference in the way ERM packages the packets.  This issue is compounded by a
bug on the Aruba side which fails to include the FCS with certain frames. 
Dissectors for Types 0, 1 and 3 should all handle the FCS the same way.

You are receiving this mail because:
  • You are watching all bug changes.