https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6179
--- Comment #13 from Sake <sake@xxxxxxxxxx> 2011-08-04 13:47:53 PDT ---
(In reply to comment #9)
> Nice enhancement.
+1 :-)
> 2) I also think there should be some way to determine that the timestamps (i.e.
> the "Arrival Time") has been time shifted. But I'm not sure how one would
> indicate that the time-stamps within the trace file has been
> "cooked"/"modified" but not yet saved.
>
> Perhaps a new generated field such as frame.time_shift could be added to the
> tree that documents the time shift value that has been applied to the current
> trace.
And maybe also a frame.time_non_shifted
This could be even more important with (option c in) the following enhancement
request to this enhancement request ;-)
Why not have three options:
a) Enter in a time shift as a delta (same time shift for all the packets in the
file)
b) Enter a frame number and an absolute time for that frame number and let
Wireshark do the math (also same time shift for all the packets in the file)
c) Enter two frame numbers, each with an absolute time and let Wireshark
calculate the time shift and the drift in time shift (which would make it
possible to even synchronize traces that were made on systems that have a clock
that run slightly slower or faster than they should :-)
After live time-shifting has been added, I think there should also be an check
mark in "File -> Save As..." to save the new timestamps to file...
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
