VMware Communities: Message List - Bridged networking on /dev/vmnet0 not created at configuration

Re: Bridged networking on /dev/vmnet0 not created at configuration

Blind Tiger — Mon, 11 Aug 2008 00:06:58 GMT

I have the same issue, Ubuntu Hardy, XP guest OS, sonicwall can't acquire ip address, or can't connect at all using bridged networking.

~$ ps ax | grep bridge
6132 ? S 0:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0
6893 pts/0 R+ 0:00 grep bridge

Re: Bridged networking on /dev/vmnet0 not created at configuration

4Filler — Wed, 21 Nov 2007 12:40:07 GMT

Thanks a lot for helping, the problem was the activated port security in the switch configuration

Re: Bridged networking on /dev/vmnet0 not created at configuration

oreeh — Wed, 21 Nov 2007 10:43:10 GMT

Is it normal that it's not listed with ifconfig?

Yes

Because my major problem was that my guests could only ping my hosts IP address but nothing more.

There are a lot of possible reasons for this.
- firewall settings
- NIC driver issues
- switch settings (ignoring / denying additional MAC addresses on the port)
- ...

Re: Bridged networking on /dev/vmnet0 not created at configuration

4Filler — Wed, 21 Nov 2007 10:38:27 GMT

Is it normal that it's not listed with ifconfig? Because my major problem was that my guests could only ping my hosts IP address but nothing more.

Re: Bridged networking on /dev/vmnet0 not created at configuration

oreeh — Wed, 21 Nov 2007 10:20:18 GMT

Then eth0 is properly bridged to vmnet0 and you should be able to use vmnet0.

Re: Bridged networking on /dev/vmnet0 not created at configuration

4Filler — Wed, 21 Nov 2007 10:19:07 GMT

Hi, thanks for helping!

This is the result:

4586 pts/0 S 0:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0
4822 pts/0 S+ 0:00 grep bridge

Re: Bridged networking on /dev/vmnet0 not created at configuration

oreeh — Wed, 21 Nov 2007 10:17:08 GMT

There's no vmnet0 device.
To check if eth0 is bridged to vmnet0 check the output of

ps ax | grep bridge

it should be similar to

 3175 ?        S      0:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0

Bridged networking on /dev/vmnet0 not created at configuration

4Filler — Wed, 21 Nov 2007 10:13:35 GMT

Hello VMware community,

I have a problem when installing VMware Server (1.0.4 and also tried beta 2) on a Dual-Xeon Server running SUSE Enterprise Server 10 Linux:

The perl-configration script says it will install vmnet0 for bridged networking on eth0 (also confirmed via editor-configuration-mode) but it doesn't. The result is the following:

At starting vmware service:

Starting VMware services:
Virtual machine monitor done
Virtual ethernet done
Bridged networking on /dev/vmnet0 done
Host-only networking on /dev/vmnet1 (background) done
Host-only networking on /dev/vmnet8 (background) done
NAT service on /dev/vmnet8 done
Starting VMware virtual machines... done

The ifconfig -a one minute after service start:

eth0 Link encap:Ethernet HWaddr 00:30:48:34:46:42
inet addr:141.28.126.107 Bcast:141.28.126.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe34:4642/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:519 errors:0 dropped:0 overruns:0 frame:0
TX packets:448 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:95873 (93.6 Kb) TX bytes:64787 (63.2 Kb)
Base address:0x2000 Memory:d8200000-d8220000

eth1 Link encap:Ethernet HWaddr 00:30:48:34:46:43
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0x2020 Memory:d8220000-d8240000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1300 (1.2 Kb) TX bytes:1300 (1.2 Kb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.170.1 Bcast:172.16.170.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:172.16.31.1 Bcast:172.16.31.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

The result:

So I can't use bridged-networking...has anyone any ideas how to fix this?

Thanks a lot,

Andreas