Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9586] Peekremote dissector needs to handle "new" header as well as "legacy" he

Wireshark-bugs: [Wireshark-bugs] [Bug 9586] Peekremote dissector needs to handle "new" header as

Date: Wed, 25 Dec 2013 23:06:08 +0000

Comment # 13 on bug 9586 from Guy Harris

(In reply to comment #12)
> I *VERY STRONGLY* suspect that the field should be fetched as an *8-byte*
> field, containing a value in microseconds - probably the TSF timer value.

And that appears to be the case with the attached captures, so I changed the
field to an 8-byte field, labeled "TSF timestamp".

You are receiving this mail because:

You are watching all bug changes.

References:
- [Wireshark-bugs] [Bug 9586] New: Need more classification of fields within Airopeek/Omnipeek encapsulated IEEE 802.11 header
  - From: bugzilla-daemon

Prev by Date: [Wireshark-bugs] [Bug 9586] Peekremote dissector needs to handle "new" header as well as "legacy" header and dissect more of the "legacy" header
Next by Date: [Wireshark-bugs] [Bug 9586] Peekremote dissector needs to handle "new" header as well as "legacy" header and dissect more of the "legacy" header
Previous by thread: [Wireshark-bugs] [Bug 9586] Peekremote dissector needs to handle "new" header as well as "legacy" header and dissect more of the "legacy" header
Next by thread: [Wireshark-bugs] [Bug 9586] Peekremote dissector needs to handle "new" header as well as "legacy" header and dissect more of the "legacy" header
Index(es):
- Date
- Thread