Wireshark-bugs: [Wireshark-bugs] [Bug 10008] New: IPv6 Timestamp Mobility Option shows wrong Tim
Date: Sat, 19 Apr 2014 10:13:49 +0000
Bug ID 10008
Summary IPv6 Timestamp Mobility Option shows wrong Timestamp
Classification Unclassified
Product Wireshark
Version 1.6.6
Hardware x86-64
OS Windows 7
Severity Normal
Priority Low
Component Wireshark
Assignee [email protected]
Reporter [email protected]

Created attachment 12713 [details]
Example IPv6 packet with Timestamp mobility option

Build Information:
Version 1.6.6 (SVNRev 41803 from /trunk-1.6)

Copyright 1998-2012 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO

Compiled (64-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, without
SMI, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.12.18, with
Gcrypt 1.4.6, without Kerberos, with GeoIP, with PortAudio V19-devel (built Mar
27 2012), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version, based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022

Wireshark is Open Source Software released under the GNU General Public

Check the man page and http://www.wireshark.org for more information.
Discovered while working on Pcap.Net (http://pcapdot.net).

In the attached pcap file, there's one packet with Mobility Options that
contain a Timestamp option.
The timestamp value is 0xd4f4192f38214e21.
According to RFC 5213 (https://tools.ietf.org/html/rfc5213#section-8.8), the
first 48 bits of this value should represent seconds since Janurary 1st, 1970
00:00:00 UTC and the rest are fraction of a second.
Looking at the first 48 bits 0xd4f4192f3821, they represent 234,144,859,633,697
seconds or about 7.4 million years.
Wireshark shows Timestamp: Mar 20, 2013 11:17:03.219258000 UTC.

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