Re: Hardware Timestamping Problem

[Michael Richardson <mcr () sandelman ca>]

Christian Rupp <christian.rupp.stuttgart () freenet de> 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 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

The timestamp on the sender is long before the hardware.
You are saying that the stamp is correct when you do not use the -j option?

if that's the case, then it seems like it's the hardware which is mis-stamping.

-- 
]               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