Wireshark-bugs: [Wireshark-bugs] [Bug 9586] Peekremote dissector needs to handle "new" header as
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 02 Jan 2014 13:58:07 +0000

Comment # 19 on bug 9586 from 
(In reply to comment #14)
> (In reply to comment #11)
> > (In reply to comment #2) PLEASE SEE INLINED
> > > What is the meaning of the "Band" field in the 55-byte header?
> > > 
> > [emburey]  It is bandwidth for 11n/11ac, and can be shown in decimal format
> > (would be always 300, 301, 400, 401, or 402)
> 
> Nope.  In at least one capture ("Wireshark trace with new header"), the
> value in the first packet is, as 4 hex bytes, 30 30 30 30, the value in the
> third packet is 30 30 30 20 (the second packet wasn't a PeekRemote packet),
> and the value in the next-to-last frame is 36 33 42 31.

Please find a new capture of the same. Seems the previous one is corrupted. In
the new one you may refer, especially frame 3, and it has the value properly.

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