The libpcap project / Bugs / #178 libpcap timestamps in virtual machine interfaces

#178 libpcap timestamps in virtual machine interfaces

Milestone: Git head

Status: closed

Owner: nobody

Labels: None

Priority: 5

Updated: 2013-11-20

Created: 2012-10-11

Creator: Ricardo

Private: No

Im not sure if this is related to libpcap or not, but in virtual machines (e.g. esxi) the timestamps captured when sending a train of packets from A to B are much more closer in time than the timestamps measured in the hypervisor. Any document/reference that talks about this effect?

Discussion

Guy Harris - 2013-04-14

That's probably a function of the way the hypervisor works. The timestamps you get from libpcap are applied to the packets by the OS, not by libpcap (except on HP-UX, but I suspect you're not running on HP-UX, as I don't think VMware ESXi runs on PA-RISC or Itanium).

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Denis Ovsienko - 2013-11-20

status: open --> closed

Group: --> Git head
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Denis Ovsienko - 2013-11-20

Administrators of the "libpcap" SourceForge project have superseded this tracker item (formerly artifact 3576423, now bug 178) with issue 182 of the "libpcap" GitHub project.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

libpcap timestamps in virtual machine interfaces

Group

Searches

Help

#178 libpcap timestamps in virtual machine interfaces

Discussion