Wireshark-bugs: [Wireshark-bugs] [Bug 10008] IPv6 Timestamp Mobility Option shows wrong Timestam

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 19 Apr 2014 18:35:12 +0000

changed bug 10008

What Removed Added
CC   [email protected]

Comment # 1 on bug 10008 from 
What is the expected timestamp?  Wireshark v1.6 had been end-of-lifed, but the
\trunk does dissect the timestamps per RFC 5213 (since
Iae4115bcdb445c3b8a97edc2317eaccdf2e0a83b).  But as you observed, honoring RFC
5213 does give you a "garbage" timestamp.

The timestamp Wireshark v1.6 produces (Mar 20, 2013 11:17:03.219258000 UTC)
treats the 8 byte timestamp as being NTP format.  And that's the only way I
could get those bytes into a sensible timestamp.  Is it possible the tool that
produced this packet is actually (incorrectly) using NTP format (from an older
RFC?)

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