VMware Communities
Hauke-m
Enthusiast
Enthusiast

Bridged network not working on Linux

Hi

I want to run a Windows XP installation in VMware Player on a Ubuntu host.

At first I used the VMware Workstation Beta 6 and RC but now I want to use the Player and at first everything worked very well, for some days. After some weeks or so I noticed that the network isn't working anymore I am only able to ping the host machine and not the other IP addresses in the network, but everything is switched to bridged.

The dmesg output is the following:

\[ 384.894916] /dev/vmmon\[3971]: VMCI: Driver initialized.

\[ 384.896308] /dev/vmmon\[3971]: Module vmmon: registered with major=10 minor=165

\[ 384.896519] /dev/vmmon\[3971]: Module vmmon: initialized

\[ 385.520278] /dev/vmnet: open called by PID 4024 (vmnet-bridge)

\[ 385.520285] /dev/vmnet: hub 0 does not exist, allocating memory.

\[ 385.520293] /dev/vmnet: port on hub 0 successfully opened

\[ 385.520300] bridge-wlan0: enabling the bridge

\[ 385.520303] bridge-wlan0: up

\[ 385.520305] bridge-wlan0: already up

\[ 385.520307] bridge-wlan0: attached

\[ 396.160678] ISO 9660 Extensions: Microsoft Joliet Level 3

\[ 396.318996] ISO 9660 Extensions: RRIP_1991A

\[ 453.826730] /dev/vmnet: open called by PID 4431 (vmware-vmx)

\[ 453.826741] device wlan0 entered promiscuous mode

\[ 453.826745] audit(1181749328.958:2): dev=wlan0 prom=256 old_prom=0 auid=4294967295

\[ 453.826747] bridge-wlan0: enabled promiscuous mode

\[ 453.826748] /dev/vmnet: port on hub 0 successfully opened

\[ 453.936626] /dev/vmmon\[4434]: host clock rate change request 0 -> 19

\[ 458.468998] /dev/vmmon\[4434]: host clock rate change request 19 -> 83

\[ 470.440335] device wlan0 left promiscuous mode

\[ 470.440343] audit(1181749345.459:3): dev=wlan0 prom=0 old_prom=256 auid=4294967295

\[ 470.440346] bridge-wlan0: disabled promiscuous mode

\[ 470.440391] /dev/vmnet: open called by PID 4434 (vmware-vmx)

\[ 470.440397] device wlan0 entered promiscuous mode

\[ 470.440400] audit(1181749345.459:4): dev=wlan0 prom=256 old_prom=0 auid=4294967295

\[ 470.440402] bridge-wlan0: enabled promiscuous mode

\[ 470.440403] /dev/vmnet: port on hub 0 successfully opened

\[ 814.607405] device wlan0 left promiscuous mode

\[ 814.607415] audit(1181749690.187:5): dev=wlan0 prom=0 old_prom=256 auid=4294967295

\[ 814.607418] bridge-wlan0: disabled promiscuous mode

\[ 814.607466] /dev/vmnet: open called by PID 4434 (vmware-vmx)

\[ 814.607472] device wlan0 entered promiscuous mode

\[ 814.607476] audit(1181749690.187:6): dev=wlan0 prom=256 old_prom=0 auid=4294967295

\[ 814.607478] bridge-wlan0: enabled promiscuous mode

\[ 814.607480] /dev/vmnet: port on hub 0 successfully opened

\[ 817.890523] /dev/vmmon\[4434]: host clock rate change request 83 -> 19

\[ 817.918961] device wlan0 left promiscuous mode

\[ 817.918969] audit(1181749693.687:7): dev=wlan0 prom=0 old_prom=256 auid=4294967295

\[ 817.918971] bridge-wlan0: disabled promiscuous mode

\[ 817.961207] /dev/vmmon\[4431]: host clock rate change request 19 -> 0

\[ 817.972077] vmmon: Had to deallocate locked 63698 pages from vm driver f4311000

\[ 817.974238] vmmon: Had to deallocate AWE 4020 pages from vm driver f4311000

\[ 851.915591] device wmaster0 entered promiscuous mode

\[ 851.915600] audit(1181749727.688:8): dev=wmaster0 prom=256 old_prom=0 auid=4294967295

\[ 851.931541] device wlan0 entered promiscuous mode

\[ 851.931547] audit(1181749727.688:9): dev=wlan0 prom=256 old_prom=0 auid=4294967295

\[ 851.947498] device lo entered promiscuous mode

\[ 851.947504] audit(1181749727.688:10): dev=lo prom=256 old_prom=0 auid=4294967295

\[ 867.307875] device wmaster0 left promiscuous mode

\[ 867.307882] audit(1181749743.189:11): dev=wmaster0 prom=0 old_prom=256 auid=4294967295

\[ 867.327823] device wlan0 left promiscuous mode

\[ 867.327828] audit(1181749743.189:12): dev=wlan0 prom=0 old_prom=256 auid=4294967295

\[ 867.363730] device lo left promiscuous mode

\[ 867.363734] audit(1181749743.189:13): dev=lo prom=0 old_prom=256 auid=4294967295

\[ 867.403665] device wmaster0 entered promiscuous mode

\[ 867.403673] audit(1181749743.189:14): dev=wmaster0 prom=256 old_prom=0 auid=4294967295

\[ 881.004727] device wmaster0 left promiscuous mode

\[ 881.004735] audit(1181749757.189:15): dev=wmaster0 prom=0 old_prom=256 auid=4294967295

\[ 884.738914] device wmaster0 entered promiscuous mode

\[ 884.738922] audit(1181749760.689:16): dev=wmaster0 prom=256 old_prom=0 auid=4294967295

\[ 884.758861] device wlan0 entered promiscuous mode

\[ 884.758867] audit(1181749760.689:17): dev=wlan0 prom=256 old_prom=0 auid=4294967295

\[ 884.782804] device lo entered promiscuous mode

\[ 884.782812] audit(1181749760.689:18): dev=lo prom=256 old_prom=0 auid=4294967295

\[ 888.094255] device wmaster0 left promiscuous mode

\[ 888.094263] audit(1181749764.189:19): dev=wmaster0 prom=0 old_prom=256 auid=4294967295

\[ 888.118195] device wlan0 left promiscuous mode

\[ 888.118200] audit(1181749764.189:20): dev=wlan0 prom=0 old_prom=256 auid=4294967295

\[ 888.166069] device lo left promiscuous mode

\[ 888.166075] audit(1181749764.189:21): dev=lo prom=0 old_prom=256 auid=4294967295

\[ 888.190052] device wlan0 entered promiscuous mode

\[ 888.190061] audit(1181749764.189:22): dev=wlan0 prom=256 old_prom=0 auid=4294967295

\[ 899.050292] /dev/vmnet: open called by PID 4623 (vmware-vmx)

\[ 899.050303] bridge-wlan0: enabled promiscuous mode

\[ 899.050305] /dev/vmnet: port on hub 0 successfully opened

\[ 899.112401] /dev/vmmon\[4626]: host clock rate change request 0 -> 19

\[ 902.624828] /dev/vmmon\[4626]: host clock rate change request 19 -> 83

\[ 906.381392] bridge-wlan0: disabled promiscuous mode

\[ 906.381429] /dev/vmnet: open called by PID 4626 (vmware-vmx)

\[ 906.381434] bridge-wlan0: enabled promiscuous mode

\[ 906.381436] /dev/vmnet: port on hub 0 successfully opened

I have logged want traffic passed the wlan0 interface and I saw that the virtual Windows sends broadcast to get to now the MAC address of the IP he want's to ping but no responds comes back.

0 Kudos
2 Replies
Hauke-m
Enthusiast
Enthusiast

I am using Ubuntu 7.04 with the standard kernel 2.6.20-16 and with kernel 2.6.22-rc4

When starting the virtual Windows it shows up the Welcomepage for about 90 seconds

Message was edited by:

Hauke-m

0 Kudos
oreeh
Immortal
Immortal

Did you update the Ubuntu host (especially the kernel)?

If yes you have to rebuild the VMware kernel modules.

0 Kudos