When does Wireshark timestamp captured packets? -
when wireshark timestamp packets? after receiving frame? or @ receiving first bytes of frame? read following description wireshark timestamps text states: "while packets captured, each packet time stamped comes in".
consider following scenario , accurate os time:
sender ----> wireshark ----> receiver
the sender starts transmission of frame @ time x. frame received @ receiver @ time y (y = transmission start x + frame length / link speed). captured frame appear in wireshark timestamp close x or y?
best regards, jonas
well, wireshark doesn't time stamp packets itself; relies on libpcap them and, on operating systems, libpcap doesn't time stamp them itself, either, os's packet capture mechanism, used libpcap does. main exception windows, winpcap has provide own capture mechanism in kernel, atop ndis, mechanism behaves mechanisms inside un*xes, , give similar behavior. (the other exception hp-ux, os's capture mechanism doesn't time-stamp packets @ all, libpcap so; gives answers similar other oses, potentially longer delay before packets time-stamped.)
if wireshark (or other packet sniffer!) run on sender, packets "wrapped around" within os , handed capture mechanism; time stamp applied before sender starts transmitting packet, time stamp closer x y.
if wireshark (or other packet sniffer) run on receiver, time stamp applied @ time after entire packet has been received; involve delays due packet being queued up, interrupts being "batched", amount of network-stack processing being done before packet time stamped, etc.. time stamp closer y x.
if wireshark (or other packet sniffer) being run on third machine, passively sniffing network, time stamp closer y x, there's difference due receiver , sniffer being separate machines might see packet @ different times, have different code paths receiving, etc..
Comments
Post a Comment