Yes the tenth digit, sorry English isn't my first language. SO yes 1.05
is printed as 1.5
Tcpdump is printing a good timestamp wrong, as far as i can tell.
The Timestamp in itself, if the 0 would be there, would be completely
okay and would make sense.
Am 28.07.2016 um 20:50 schrieb Guy Har
The Timestamp when tcpdump grabs the package off of the receiver is 36
seconds( +/- innaccuracy, here roughly +/- 5-10 µs) after the timestamp
when tcpdump grabs the package of the sender. resulting in an alleged
One Way Delay of 36 seconds which wouldn't make any sense in that
scenario, giv
Yes, one tcpdump entity per server, after Both are started I start a
Package Generator which sends a 900kbs Trace.
There shouldn't be a big buffering effect, if I'm not using the hardware
timestamp options the one way delay is at a few 100 µs, or am I
misunderstanding something?
The 36 seconds
