ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 11204] The Aruba ERM Type 1 Dissector inconsistent with Ty

Date: Thu, 21 May 2015 21:02:10 +0000

Comment # 18 on bug 11204 from
(In reply to Doug Wussler from comment #14)
> So from the ERM dissectors you are doing this:
> ieee80211_handle = (find_dissector("wlan_withoutfcs") 
> or this
> ieee80211_handle = (find_dissector("wlan_withfcs")
> 
> Would it be possible to make the call in a way that references the value of
> the “Assume packets have FCS” checkbox in the IEEE 802.11 dissector?  If you
> could do that for Type 0, 1 and 3 that would allow the end-user to decide
> how they want to deal with the missing FCS.

By which you mean "allow the end-user to decide which not-always-correct
behavior they want"; the problem isn't, as far as I can see, that the FCS is
always missing or always present, the problem is that the FCS is always present
on frames received by the Aruba device and always absent on frames transmitted
by the Aruba device, and that there's no "Tx vs. Rx" flag in any of the flavors
of metadata headers, so, unless *all* frames are transmitted or *all* frames
are received, you're *guaranteed* to have at least one frame misdissected.

You can't fix that with a global preference such as "Assume packets have FCS".


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