Michael Mann
changed
bug 10008
| What |
Removed |
Added |
| Status |
UNCONFIRMED
|
RESOLVED
|
| Resolution |
---
|
FIXED
|
Comment # 3
on bug 10008
from Michael Mann
(In reply to comment #2)
> The tool that produced this packet gives a random
> timestamp.
> I'm not sure what do you mean by "garbage" timestamp. It's not a
> useful timestamp, but it's valid according to the RFC.
> Wireshark could say
Wireshark now displays its as "Not representable". I had assumed the tool was
trying to produce a "useful" timestamp (something in the not too distance
future/past), not a random one.
> it's a timestamp that is too large or unrepresentable, but giving some
> specific timestamp in 2013 even though the actual timestamp is some million
> years in the future doesn't make sense for me.
> Was this fixed in a
> different Wireshark version?
Yes, it was fixed in v1.10 and I'm guessing it was considered an "enhancement"
at the time (adding support for RFC 5312), so it wasn't backported.
You are receiving this mail because:
- You are watching all bug changes.
