Jonathan Ervine wrote: >> 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 >> >> >> > > As John Andersen mentioned, this all looks pretty much correct. When you run > through this script, and define the bridged network(s) - how many have you > set up? How many physical ethernet devices do you have? What I've had happen > is to have my wired interface (eth0) bridged and then tried to run VMware > when on a wireless network. When this has been done, obviously the wired > network is not available and you can get a message similar to the one you are > reporting. If you want to send along the output of ifconfig -a and ps -eaf | > grep vmnet-bridge that might help. > > Hi again Jon.
You can see above, that I have set up 2 bridged network. Vmnet1 and vmnet 8. I have one physical ethernet device. Here's the outputs: # ifconfig -a eth3 Link encap:Ethernet HWaddr 00:0B:6A:EC:05:21 inet addr:192.168.1.9 Bcast:255.255.255.255 Mask:255.255.255.0 inet6 addr: fe80::20b:6aff:feec:521/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15626 errors:0 dropped:0 overruns:0 frame:0 TX packets:12703 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:15271791 (14.5 Mb) TX bytes:1321587 (1.2 Mb) Interrupt:185 Base address:0xc000 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:1359 errors:0 dropped:0 overruns:0 frame:0 TX packets:1359 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:41221 (40.2 Kb) TX bytes:41221 (40.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:192.168.185.1 Bcast:192.168.185.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:6 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.104.1 Bcast:172.16.104.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:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) # ps -eaf |grep vmnet-bridge root 3323 1 0 07:10 ? 00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0 root 4872 4817 0 09:32 pts/1 00:00:00 grep vmnet-bridge >> # lsmod | grep vmnet >> vmnet 45484 12 >> lajka3:/home/erikja # modprobe vmnet >> >> I still have the problem with the bridged Ethernet >> > > The above is fine - the vmnet module is already loaded, so modprobe vmnet is > not necessary. > > Very good. -- Med venlig hilsen / Best regards Erik Jakobsen [EMAIL PROTECTED] openSuSE 10.2 (i586) -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]