Wireshark-bugs: [Wireshark-bugs] [Bug 11204] The Aruba ERM Type 1 Dissector inconsistent with Ty
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 21 May 2015 14:04:27 +0000

Comment # 13 on bug 11204 from 
Alexis -  That is the way Type 1 currently works.  It assumes there is always
an FCS and it reports "malformed packets".  Type 0 is not "buggy".

There are two bugs:

1. Aruba: Aruba AP does not include FCS bytes on frames transmitted by a
capturing AP.  Let's not try to compensate for that in Wireshark.  Let's fix
that on the Aruba end.

2. Wireshark: ERM Type 1 dissector handles FCS differently than Types 0 and 3
even though there is no difference in the way the FCS bytes are delivered by
Aruba.  The fix to this is to call Type 0 and Type 3 "withFCS" instead of
"withNoFCS".

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