Workstation 6/linux host//wireless/bridged networking

[pvl]

Is bridged networking supposed to work for VMs in workstation 6 on linux? I'm running on SLED sp1 and everything seems to be working well, except that I cannot get bridged networking to work.

Any tips/suggestions?

Peter

[pvl]

Nothing?

Do others with linux host have bridged working?

Where can I go to look at why it might be failing?

[SandyGray]

I just install the eval for Workstation 6 on Linux and cannot get bridged networking either. I can ping from guest xp to the host linux but not in other direction or to any other computer on the network. Have you found a solution yet?

Thanks

[louyo]

Well, a search for bridged on the forums will probably bring some solutions. I run bridged all the time, I am running a Linux host (OpenSUSE 10.3 now) and several Vista, XP, W2003, and W2K guests. All work bridged or NAT.

For testing purposes, make sure you turn off all firewalls. If that "fixes" it, then you can make the appropriate settings in the firewall.

You should also post the results of "ipconfig/all" from Windows hosts and guests and "ifconfig -a" from Linux hosts and guests. When you say you can't ping, what is the error? Time out, etc.

Make sure all OS's are on the same subnet and all share the same gateway and DNS server. In Linux, that can be found in /etc/resolv.conf. It will show up in the ipconfig from Windows.

It may also help if you post the network entries in your vmx file, or just the whole file.

These forums are a little slow and many hesitate to respond to "it doesn't work" messages as opposed to "when I try do this command, the error message is: blah, blah and the Vmware log has this entry: more blah blah. For network stuff, you need to post settings and results from ping and ipconfig/ifconfig and (if pertinent) the route print command.

Lou

[pvl]

I have not found a solution. Since nobody responded at all, and since I was aware that bridged networking with wireless had been a problem, I switched my vm to nat. Not what I wanted, but I don't have hour after hour after hour to play with it, either.

[pvl]

Well Lou a seach for bridged on the forums really did not return much or anything that was helpful, except questions that, like mine, went unanswered.

I will certainly try the turning off the firewall .... I had no idea that the firewall might play a role, here. If that fixes it than thank you, despite your snotty attitude. If the firewall does not address the issue, I could certainly manually configure an ip address on the guest, in order to attempt pings, but my intention is to have the guest use DHCP to gain an address. At this point, the DHCP request goes un-fulfilled if the host network is wireless, while it succeeds if the host network is wired. I will gladly post ifconfig -a from the host, if the problem persists.

Either you have heard of this problem, or you have not ... either you have constructive suggestions or you do not.

[pvl]

disabling the firewall produced no change in the behaviour. If I connect my host to a cabled ethernet, the guest can immediatly get an IP address from DHCP. If I then disconnect from wired and make a wireless host connection, the guest can no longer get an ip address from dhcp.

Here is the host ifconfig -a result:

p02-2199SLED:~ # ifconfig -a

eth0 Link encap:Ethernet HWaddr 00:17:A4:D5:4A:03

UP 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)

Interrupt:177

eth1 Link encap:Ethernet HWaddr 00:19:D2:5E:6B:CB

inet addr:192.168.2.101 Bcast:192.168.2.255 Mask:255.255.255.0

inet6 addr: fe80::219:d2ff:fe5e:6bcb/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:53356 errors:60 dropped:180 overruns:0 frame:0

TX packets:14522 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:19976358 (19.0 Mb) TX bytes:2719184 (2.5 Mb)

Interrupt:185 Base address:0x4000 Memory:f4000000-f4000fff

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:578 errors:0 dropped:0 overruns:0 frame:0

TX packets:578 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:21584 (21.0 Kb) TX bytes:21584 (21.0 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.97.1 Bcast:172.16.97.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:192.168.10.1 Bcast:192.168.10.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:116 errors:0 dropped:0 overruns:0 frame:0

TX packets:15 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

p02-2199SLED:~ #

[louyo]

This patch fixed it for me, that is what I thought you would find:

Note that it may be broken by the newest kernel, I have not updated.

If that fixes it than thank you, despite your snotty attitude.

<plonk>

good-bye

Lou

[pvl]

I recieved a useful response, but for some reason it came to my private email (it irritates me that my email addressed is exposed on this forum, by the way ...). At any rate, here it is for Sandy or others that may be wondering.

"This patch fixed it for me, that is what I thought you would find: http://communities.vmware.com/thread/95630?tstart=0&start=0

Note that it may be broken by the newest kernel, I have not updated. "

This looks promising, though I haven't the time to try for the next couple days. In this thread is a patch that, depending on your kernel, may fix bridged networking. I have SLED sp1 with no updates beyond SP1 and am running 2.6.16.46-0.14-bigsmp -- so that I am hopeful that the issue for me will be resolved.

Note that I do not know if this patch is an official VMware patch, or provided by some helpful user.

Peter