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 13:52:03 +0000

Comment # 11 on bug 11204 from 
Alexis - I completely understand that Aruba delivers the FCS for RX and not for
TX.  This is true for all Types: 0, 1 and 3.  And that is an Aruba bug, not
something we should try to fix in Wireshark.

The REAL problem in Wireshark is that the dissectors do not behave
consistently.  Your proposed fix is going to make them even more inconsistent
because now all three Types will have different behavior.

>From the perspective of a Wireshark analysis it is vastly better if all three
Types behave similarly.  If all three assume the FCS then we will see the same
set of "malformed packets" and understand what we are seeing.  Then, when Aruba
starts delivering the FCS in TX, as they should, all three dissectors will
still report "malformed packets" but it will be due to an invalid FCS.  This
will again be something we can understand and, if we want, can adjust in our
approach to FCS validation.

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