File: README.vmware

package info (click to toggle)
wireshark 1.12.1+g01b65bf-4+deb8u14
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 234,068 kB
  • sloc: ansic: 1,912,971; xml: 84,598; cpp: 41,923; python: 30,175; perl: 25,286; lex: 6,416; sh: 6,406; pascal: 6,120; makefile: 3,968; yacc: 297; asm: 156; awk: 58; tcl: 35
file content (29 lines) | stat: -rw-r--r-- 1,423 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
If you are a registered user of VMware on Linux, you can contact their
support staff via e-mail and ask for a libpcap patch which will allow
you to sniff the virtual NIC of your virtual machine.

vmware configures 4 devices, /dev/vmnet[0-3]. 

/dev/vmnet0 is your ethernet bridge, giving your virtual machine its
own MAC address on your physical ethernet LAN.

/dev/vmnet1 is for host-only networking. Your host OS will be routing IP
packets between the physical LAN and the guest OS. When up and running,
you'll see a 'vmnet1' interface from 'ifconfig'. 

/dev/vmnet2 and /dev/vmnet3 act as hubs for virtual machines, but are
not connected to anything else. That is, the VM's that are connected
to these devices can talk to each other (if connected to the same
virtual "hub"), but not to the outside world, or to your host OS
(as far as I understand).

With the patch from VMware, you can sniff the packets on these
network devices. Note the distinction between "network device", where a
device driver file exists in /dev, and "interface", which is a namespace
private to the kernel (not on the filesystem). You have to supply the
full pathname  of the device to Wireshark (i.e., "/dev/vmnetN").
When vmnet1 is up, you will be able to select it from the list of
interfaces, since it will have both a device name (/dev/vmnet1) and
an interface name "vmnet1"

See also http://www.vmware.com/products/scenarios/networks.html