Re: [tcpdump-workers] Hardware Timestamping Problem

2016-06-09 Thread Christian
Yes, the exact same packet. Am 08.06.2016 um 22:40 schrieb Guy Harris: On Jun 8, 2016, at 1:29 PM, Christian Rupp wrote: 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 pa

Re: [tcpdump-workers] Hardware Timestamping Problem

2016-06-09 Thread Michael Richardson
Guenter Ebermann wrote: > Hardware timestamping of sending/receiving buffer descriptors is done > by NIC. Receiving I understand. Are you sure that the hardware is going to timestamp sent packets, and then turn around and send the back to the kernel? -- ] Never tell me th

Re: [tcpdump-workers] Hardware Timestamping Problem

2016-06-09 Thread Christian
The experiments I made today actually suggest that in my case tcpdump uses the hardware clock for incoming packages and the software/unix clock for outgoing packages. I changed the System clock of one Server with date -s and then looked at the capture of Ping packages. Incoming packages on the

Re: [tcpdump-workers] Hardware Timestamping Problem

2016-06-09 Thread Guenter Ebermann
> Am 09.06.2016 um 15:47 schrieb Michael Richardson : > > Guenter Ebermann wrote: >> Hardware timestamping of sending/receiving buffer descriptors is done >> by NIC. > > Receiving I understand. > > Are you sure that the hardware is going to timestamp sent packets, and then > turn around and se

Re: [tcpdump-workers] Hardware Timestamping Problem

2016-06-09 Thread Guy Harris
On Jun 9, 2016, at 1:19 PM, Guenter Ebermann wrote: >> Am 09.06.2016 um 15:47 schrieb Michael Richardson : >> >> Guenter Ebermann wrote: >>> Hardware timestamping of sending/receiving buffer descriptors is done >>> by NIC. >> >> Receiving I understand. >> >> Are you sure that the hardware is

Re: [tcpdump-workers] Hardware Timestamping Problem

2016-06-09 Thread Guenter Ebermann
> Am 10.06.2016 um 00:13 schrieb Guy Harris : > > But that doesn't mean that the packets time stamped by the hardware when > transmitted will be delivered to the PF_PACKET sockets used by libpcap *with > the hardware time stamp as the time stamp*. > > In order make that happen, if hardware tra

Re: [tcpdump-workers] Hardware Timestamping Problem

2016-06-09 Thread Guy Harris
On Jun 9, 2016, at 4:09 PM, Guenter Ebermann wrote: > >> Am 10.06.2016 um 00:13 schrieb Guy Harris : >> >> But that doesn't mean that the packets time stamped by the hardware when >> transmitted will be delivered to the PF_PACKET sockets used by libpcap *with >> the hardware time stamp as th

Re: [tcpdump-workers] Hardware Timestamping Problem

2016-06-09 Thread Guenter Ebermann
> Am 10.06.2016 um 01:35 schrieb Guy Harris : > > On Jun 9, 2016, at 4:09 PM, Guenter Ebermann > wrote: > >> >>> Am 10.06.2016 um 00:13 schrieb Guy Harris : >>> >>> But that doesn't mean that the packets time stamped by the hardware when >>> transmitted will be delivered to the PF_PACKET so

Re: [tcpdump-workers] Hardware Timestamping Problem

2016-06-09 Thread Guy Harris
On Jun 9, 2016, at 4:47 PM, Guenter Ebermann wrote: > They are only delivered to the socket on which the packet was sent, not to > all PF_PACKET sockets. Then Christian can't get what I think he wants with libpcap - or anything else doing PF_PACKET socket capturing on Linux - without doing so