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, given that the software timestamping option and the -j adapter
option both result in a ~ 100-200µs one way delay
Am 08.06.2016 um 22:13 schrieb Guy Harris:
On Jun 8, 2016, at 5:53 AM, Christian <christian.rupp.stuttg...@freenet.de>
wrote:
Now, my results in itself make sense and would give me the desired results, but
they have a big offset to them. 36 seconds to be exact.
So you're saying there's a 36-second offset between which two times?
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers