tcpdump mailing list archives
Re: Hardware Timestamping Problem
From: Michael Richardson <mcr () sandelman ca>
Date: Wed, 08 Jun 2016 09:25:28 -0400
Christian <christian.rupp.stuttgart () freenet de> 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 33333 -x -n -tt -v -j > adapter_unsynced --time-stamp-precision=nano -w name.pcap > 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. 36s between which point and which point? -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr () sandelman ca http://www.sandelman.ca/ | ruby on rails [ _______________________________________________ tcpdump-workers mailing list tcpdump-workers () lists tcpdump org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Current thread:
- Hardware Timestamping Problem Christian (Jun 08)
- Re: Hardware Timestamping Problem Michael Richardson (Jun 08)
- Message not available
- Re: Hardware Timestamping Problem Michael Richardson (Jun 08)
- Re: Hardware Timestamping Problem Christian Rupp (Jun 08)
- Message not available
- Re: Hardware Timestamping Problem Michael Richardson (Jun 08)
- Re: Hardware Timestamping Problem Guy Harris (Jun 08)
- Re: Hardware Timestamping Problem Christian Rupp (Jun 08)
- Re: Hardware Timestamping Problem Guy Harris (Jun 08)
- Re: Hardware Timestamping Problem Christian (Jun 09)
- Re: Hardware Timestamping Problem Michael Richardson (Jun 08)
- Re: Hardware Timestamping Problem Guenter Ebermann (Jun 08)
- Re: Hardware Timestamping Problem Michael Richardson (Jun 09)
- Re: Hardware Timestamping Problem Christian (Jun 09)
- Re: Hardware Timestamping Problem Christian Rupp (Jun 08)