nexmon – Blame information for rev 1

Subversion Repositories:
Rev:
Rev Author Line No. Line
1 office 1 If you are a registered user of VMware on Linux, you can contact their
2 support staff via e-mail and ask for a libpcap patch which will allow
3 you to sniff the virtual NIC of your virtual machine.
4  
5 vmware configures 4 devices, /dev/vmnet[0-3].
6  
7 /dev/vmnet0 is your ethernet bridge, giving your virtual machine its
8 own MAC address on your physical ethernet LAN.
9  
10 /dev/vmnet1 is for host-only networking. Your host OS will be routing IP
11 packets between the physical LAN and the guest OS. When up and running,
12 you'll see a 'vmnet1' interface from 'ifconfig'.
13  
14 /dev/vmnet2 and /dev/vmnet3 act as hubs for virtual machines, but are
15 not connected to anything else. That is, the VM's that are connected
16 to these devices can talk to each other (if connected to the same
17 virtual "hub"), but not to the outside world, or to your host OS
18 (as far as I understand).
19  
20 With the patch from VMware, you can sniff the packets on these
21 network devices. Note the distinction between "network device", where a
22 device driver file exists in /dev, and "interface", which is a namespace
23 private to the kernel (not on the filesystem). You have to supply the
24 full pathname of the device to Wireshark (i.e., "/dev/vmnetN").
25 When vmnet1 is up, you will be able to select it from the list of
26 interfaces, since it will have both a device name (/dev/vmnet1) and
27 an interface name "vmnet1"
28  
29 See also http://www.vmware.com/products/scenarios/networks.html