Re: [tcpdump-workers] Hardware Timestamping Problem

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,

Re: [tcpdump-workers] Hardware Timestamping Problem

On Jun 8, 2016, at 5:53 AM, Christian 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?

Re: [tcpdump-workers] Hardware Timestamping Problem

{please keep it on the list for archival purposes} Christian wrote: > between sender and receiver > so from the point when tcpdump grabs the time off of the Sender and to the > point where tcpdump grabs the time off of the receiver. So you are

Re: [tcpdump-workers] Hardware Timestamping Problem

Christian wrote: > My Setup: > 2 directly connected identical Servers. > Linux: Debian 3.16.7 > Network Interface: Intel i350-T4 > Used tcpdump command: > sudo /usr/sbin/tcpdump -i eth4 -s 59 port 3 -x -n -tt -v -j >