Do you know some bug with Time Shift feature? When I right-click on the first packet in the trace file, I choose Time Shift... and write -0.000235 it does not work (uoy can user Reload button on the toolbar). I can use only full second for example +3.0. Miliseconds, and other, do not work. It is normal? Or I should set something more? asked 16 Oct '13, 13:48  net16 |
2 Answers:
I have the same effect on my system. However if I use a comma instead of a dot, it works. I run a german localized Windows. Works (comma): +/- 0,00001 I don't know if this is intended localized behavior of Wireshark or a bug. ++ UPDATE ++ I tend to say it is (kind of) a bug, as the help text in the "Time Shift" windows only mentions a dot, even on a localized windows. However, that behavior is the same since 1.8.0 !?! So, maybe it is intended localized behavior, but then the help text needs to be adjusted for a localized windows as well. Regards answered 17 Oct '13, 02:53  Kurt Knochner ♦ edited 17 Oct '13, 03:26 |
Which time-shift option did you use? I assume the pre-selected one on top? This makes all packets shift in time, which means the relative time won't change (as the time stamp of the first packet is also shifted). Could you look into the frame section for the absolute timestamp and check whether it has changed? BTW it is indeed possible to do changes in microseconds... answered 16 Oct '13, 14:14  SYN-bit ♦♦ Thank you SYN-bit. I use first option and anything does not change: time in Time column and [Time shift for this packet: 0.000000000 seconds] (in frame section). If I use 2, 3 seconds then it changes. But if I use 0.something it does not work. The smallest Tick interval is 0.001s (in Statistics->IO Graph). It is possible to take data to CSV in smaller intervals? It is needed to analising on microsecond field. (16 Oct '13, 14:30) net16 1 Which version of wireshark are you using? I just tried myself with 1.10.2 and timeshifting does work for -0.000100. In IO graphs, it is not possible to use a smaller interval without changing the source code. (it's better to start a new question for uhmmm... new questions :-)) (16 Oct '13, 15:13) SYN-bit ♦♦ I use 1.10.2 too. When I write -0.000100, I receive "Offset is zero." error. But if I write -1.000100 Arrival Time has decreased about 1 s (and [Time shift for this packet: -1.000000000 seconds]). Notice that it decreases with 1s, not 1.000100s. Value has been rounded to integer value. I have checked on different files and packets. What is the problem?? I have SVN Rev 51934 from/trunk-1.10. (17 Oct '13, 02:31) net16 |
Yes, a comma works. Thank you very much again.
You're welcome:
Hint: If a supplied answer resolves your question can you please "accept" it by clicking the checkmark icon next to it. This highlights good answers for the benefit of subsequent users with the same or similar questions.