VMware Communities: Message List - No Internet on VMWare WS w/ Linux 2.6.22 kernel

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

fuzZzball — Tue, 06 Jan 2009 20:40:25 GMT

Confirmed, works on ubuntu hardy 8.04 (2.6.24-22)

VMware Server 1.08 (I used "Hauke's" vmnet patch for Workstation 6.03 for kernel 2.6.24)

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Tokolosh — Wed, 09 Jul 2008 15:50:36 GMT

I've just swapped my base os from xp to ubuntu having recently (re)joined the linux community but I seem to have hit the same snag, i.e. wired connection works fine, wireless doesn't, I've re-run the config and manually set vmnet0 to wlan0 but I just don't get any traffic on the vmnet0 adapter.

I've tried leaving vmnet0 as eth0 and configuring vmnet2 as wlan0 but still nothing.

I've downloaded and applied the patch but still no traffic at all.

Are there any updates to the patch for vmware 6.0.4 on Linux 2.6.24(-19-generic)?

Do these patches normally get included in the full releases and if so how long does that normally take?

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

derekliang — Fri, 02 May 2008 06:17:15 GMT

it worked for on ubuntu 64 8.04. thanks alot.

Re: Patch for Kernel 2.6.24

LinuxFreakus — Mon, 14 Apr 2008 02:36:05 GMT

Oh my goodness, I just spent probably 5 or 6 hours souring these forums and google and was about to give up when I noticed a link to this thread from another thread...

I knew the bridge mode must work contrary to many posts I found which flatly stated that bridge to wireless is not supported at all, this was all working fine for me when I used a windows host machine... but I got tired of windows hogging so many resources when I never used it for anything, I do all my work in VMs. So now I have a slim and trim linux setup and thanks to this patch, the wireless bridge WORKS!!!! yes!!!

Incidentally, you can almost get a working alternative by using host only with ip masquerade, but it just isn't elegant to have to add routes to all other machines on the lan in order to reach each of the VMs through the host IP address. (yes, the nat interface might have been simpler, but my VPN stuff wouldn't work with it)

Thanks a bunch!

Re: Patch for Kernel 2.6.24

Chronniff — Fri, 28 Mar 2008 22:08:55 GMT

Hauke, Thanks for the tip, I knew the config wasn't compiling a new module with the patch, and I knew that was the problem.....what I couldn't figure out is why or how to make it do that....and you have given me glory....much thanks

Re: Patch for Kernel 2.6.24

clawhead — Fri, 21 Mar 2008 09:42:40 GMT

Hauke-m,

Thanks to Google's translation feature, I can tell you this:

Du der Mann!

-clawhead

(1) Reboot - McCain
(2) Reformat - Clinton
(3) Install new OS - Obama

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

jimbo45 — Fri, 21 Mar 2008 02:48:30 GMT

I'm using SUSE 10.3 x_64 bit Host and Windows XP guest and now it works perfectly both for Wired (eth0) and Wireless (wlan0) .

Thanks

blackdog:~ # uname -r
2.6.22.17-0.1-default
blackdog:~ #

Cheers

-J

Re: Patch for Kernel 2.6.24

2hansen — Thu, 20 Mar 2008 11:09:41 GMT

Excellent, thanks a lot!!

Re: Patch for Kernel 2.6.24

Lxxa — Wed, 19 Mar 2008 21:26:35 GMT

Works great now! Thank You!

Re: Patch for Kernel 2.6.24

Hauke-m — Wed, 19 Mar 2008 18:56:41 GMT

I had the same problem with my notebook, but I have solve it.
I have tested the modules with kernel 2.6.24 on a x86_64 system and with kernel 2.6.22 on a i386 system and both are working in bridged modus with a wireless LAN device

Now VMware has support for Ubuntu 7.10, so there is a pre-compiled kernel module. In the installation process ( vmware-config.pl ) it searches at first for a binary modules to install and with version 2.0.3 (Player) 6.0.3 (Workstation) it finds some for Ubuntu 7.10 so it takes them and don't compile them out of the sources. These modules ware build out of the default sources, so the wireless problem still exist.

You have to rename the UtsRelease property in the properties file in the folder for the kernel module the system wants to take to something not matching your installed kernel, so vmware can't find the binary and builds a new one. For Ubuntu 7.10 with x86_64generic kernel the property file is at /usr/lib/vmware/modules/binary/bld-2.6.22-14-x86_64generic-Ubuntu7.10/properties and the UtsRelease property can be renamed to 2.6.22-10-generic or something else.
Now you can run vmware-config.pl and it will build the kernel module with the wireless LAN patch if you have placed the right vmnet.tar at /usr/lib/vmware/modules/sources/

Re: Patch for Kernel 2.6.24

Lxxa — Wed, 19 Mar 2008 11:29:10 GMT

The same at me. Kernel version: 2.6.22 VMware: 6.0.3

Wired adatpter network bridge is working, wireless not.

btw I'm using Lenovo X60s, I tried both with 602 and 603 patch (just replace the vmnet.tar) but guest OS has "limited or no connectivity"

Any idea?

Thanks

Re: Patch for Kernel 2.6.24

2hansen — Tue, 18 Mar 2008 10:01:47 GMT

Is it possible to use this patch for the 2.6.22 kernel? I am using Ubuntu 7.10 and have so far been able to acces my host's wireless LAN from my guest (Windows Vista Enterprise 32-bit). However after upgrading to Workstation 6.0.3 the network is unaccessible - both with http://www.hauke-m.de/fileadmin/vmware/6.0.3/vmnet.tar and the "old" patched vmnet.tar (which worked with 6.0.2)...

Is a special 2.6.22 and 6.0.3 patch needed?

Thanks...

B:)

Patch for Kernel 2.6.24

Hauke-m — Sun, 16 Mar 2008 17:55:27 GMT

The new version of VMware Player 2.0.3 supports the kernel 2.6.24, but it doesn't include the wireless LAN bridged support. So I applied the patch to this version and it works for now. You can download the patched vmnet.tar here: http://www.hauke-m.de/fileadmin/vmware/6.0.3/vmnet.tar

If you don't want to upgrade your hohle VMware Player or Workstation then you can use these packages to get it compile with kernel 2.6.24, if you have VMware Player 2.0.3 you don't need them.The other packages for VMware, which I havened changed can be found also here: http://www.hauke-m.de/fileadmin/vmware/6.0.3/vmmon.tar and here http://www.hauke-m.de/fileadmin/vmware/6.0.3/vmblock.tar

Re: Patch for Kernel 2.6.24

mrvanes — Sun, 16 Mar 2008 18:58:56 GMT

I had to patch vmmon.tar with 2.6.24 patch as well. That patch yields 2 hunks that fail, but vmmon compiles without errors and vmplayer 2.0.3 runs like a charm, including wireless bridge.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

mrvanes — Mon, 03 Mar 2008 09:36:20 GMT

Checked and confirmed to work (with out-of-kernel ipw3945). THX al lot!

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sat, 01 Mar 2008 18:28:58 GMT

Thanks for the good info, unail. I've been making do with NAT wireless while running kernel 2.6.24, but I'll give your solution a shot as soon as I have time. At any rate, it's good to see a more complete explanation of the problem's cause.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Unail — Sat, 01 Mar 2008 18:12:41 GMT

Hi. I have found the solution to wireless bridge problem here: http://liken.otsoa.net/blog/

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

mrvanes — Wed, 06 Feb 2008 19:36:25 GMT

This patch stopped working for me on 2.6.24.
I am not 100% sure if 2.6.24 alone is to blame, because I had to switch wireless driver from ipw3945 to iwl3945 (built-in) in the process.

vmnet builds correctly with any-any-116, and after applying the patch. vmnet-bridge is up for the wireless interface, but dmesg never shows eth1 going into promisc mode, although it perfectly can do promisc when I ask it to do so (ifconfig eth1 promisc). Putting eth1 in promisc by hand doesn't help.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Chris Morgan — Fri, 25 Jan 2008 22:05:26 GMT

Great patch man. Any plans to update it against 2.6.24?

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

MentholMoose — Sat, 19 Jan 2008 07:48:48 GMT

Thanks for the patch! It fixed wireless bridging for me.

VMware Workstation 6.0.2 build-59824
Gentoo Linux host, kernel 2.6.22.15
Intel 2915ABG (ipw2200)
IBM Thinkpad T42p

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

imacamper — Sun, 09 Dec 2007 16:18:09 GMT

I have been through this thread over and over but can't get bridged networking going on my laptop with Workstation 6.0.2 or 6.0.1. I have tried kernels 2.6.23-r2, 2.6.23-r3, and 2.21-r4. I have a Gateway laptop with and ATI chipset. lspci reports the wireless card as:

05:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)

I use the bcm43xx driver as a kernel module.

Any ideas? Should my wireless be capable of bridged networking? From guest (Win XP) I can ping host but nothing beyond. Other nodes on my local LAN are not reachable. NAT works just fine.

Thanks,

Drew

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Hauke-m — Mon, 12 Nov 2007 16:07:44 GMT

I had a problem with my server. It ran out of memory, because of a gameserver also running on the server.

Now everything is working as it should.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

k31k0 — Mon, 12 Nov 2007 09:19:52 GMT

First, sorry for reopening the thread.

It seems that I can't download the patch. When I try to download the file http://www.hauke-m.de/fileadmin/vmware/vmnet.tar, my browser is saying "Waiting for www.hauke-m.de..." and it never starts downloading

Please help me...

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

franske — Tue, 06 Nov 2007 14:58:13 GMT

My Atheros Madwifi is set at ath0. And I have tried a lot of config incl. the one you mention.

I think I :

better use the org vmnet.tar,
set my eth0 to a static address,
set vmnet0-bridge to eth0 (vmware -wants- one bridge) and
try to use NAT or Host-only to/on ath0

Bridge on ath0 is a no-go it seems with VMwareServer 1.04
Annoying, all of this.
I would use Virtualbox (no problems there) but it uses much more cpu-power.

It's now 21.22 hr over here. Finished the setup:

eth0 static setup & start at boot !
vmnet0-bridge set to eth0
vmnet8 NAT+DHCP on ath0

It works & good enough for me.

Pity I cannot do with just the bridge to ath0, but I can live with it.

Franske

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Tue, 06 Nov 2007 09:34:13 GMT

Is the vmnet device you're using bridged to the correct network adapter? I.e., if you're using vmnet0 and your wifi adapter is at eth1, have you instructed VMWare to bridge those two devices? This is usually done when you run vmware-config.pl, although it can be partially adjusted in Settings.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

franske — Tue, 06 Nov 2007 07:53:04 GMT

Sorry,

Looks like I was too quick: it seemed to be working, but after a restart it doesn't anymore.

I'll look into it.

BTW: Virtualbox-1.5.0-OSE has no problems whatsoever, could look at that source-code..

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

franske — Mon, 05 Nov 2007 20:51:48 GMT

Thank you -very- much for this patch!

Now bridging works on my Asus A6M with a Atheros 5006XS Wifi-miniPCI card (I ditched the broadcom 4318), Mandriva 2008.0 AMD64, kernel-laptop-2.6.22.9 with VmwareServer 1.04.

All FYI.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clive_long — Wed, 31 Oct 2007 17:41:07 GMT

smear3 wrote:I'm doing something wrong here. I renamed the original vmnet.tar to vmnet.tar.old Then as root I copied the patch file to: /usr/lib/vmware/modules/source/. Next I went to /usr/bin/vmware-config.pl and ran that script as root. After clicking enter on everything [1] I restarted my virtual machine but the nic on the xp sp2 still thinks it's connecting to the LAN [2}. I am running Ubuntu Gutsy Kernel 2.6.22 and Workstation 6.0.2. The only thing that I can think I'm doing wrong is not enabling NAT in the config.pl [3]. The reason I don't want NAT [3] is I want my virtual machine to get it's ip from DHCP on the Windows network so I can test etc. with it. Why do you think that my wireless isn't working? Basically my problem is like the others here. It works wired but not on the wifi. Thanks in advance for any help.

[1] May well be your problem. Have you run two NICs before? If not, then you need two bridged NICs. By hitting enter and accepting all defaults you will end up with vmnet0 as bridged, vmnet1 as NAT and vmnet8 as host. You do not want this default config if you want both NICs to connect to a physical network. See also [3].

[2] this is fine. Guest OS always see the NICs as wired connections - no matter whether they are physically wired or wifi.

[3] I'm not quite understanding what you have written. I am assuming you don't want NAT but want both NICs to take there IP Address from a DHCP server. This is a fine simple setup. I just wanted both virtual NICs to be on the same subnet as the DHCP server in the router. So when I ran vmware-config.pl I set both vmnet0 and vmnet1 to be bridged and deleted all other vmnet2. In the virtual machine parameters I mapped eth0 to vmnet0 and eth1 to vmnet1. The detailed instructions and lots of variants to create subtle and easy-to-get wrong subnets are documented in the WS User Guide Chapter 13, configuring a virtual network > Setting Up a Second Bridged Network Interface on a Linux Host, works under Linux

Clive

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

smear3 — Wed, 31 Oct 2007 05:09:09 GMT

I'm doing something wrong here. I renamed the original vmnet.tar to vmnet.tar.old Then as root I copied the patch file to: /usr/lib/vmware/modules/source/. Next I went to /usr/bin/vmware-config.pl and ran that script as root. After clicking enter on everything I restarted my virtual machine but the nic on the xp sp2 still thinks it's connecting to the LAN. I am running Ubuntu Gutsy Kernel 2.6.22 and Workstation 6.0.2. The only thing that I can think I'm doing wrong is not enabling NAT in the config.pl. The reason I don't want NAT is I want my virtual machine to get it's ip from DHCP on the Windows network so I can test etc. with it. Why do you think that my wireless isn't working? Basically my problem is like the others here. It works wired but not on the wifi. Thanks in advance for any help.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clive_long — Fri, 26 Oct 2007 08:46:14 GMT

It works!

I can now take my laptop back into my office and run off wifi.

Thanks to those people who worked out this and fixed it.

Thanks for open source.

Clive

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Thu, 25 Oct 2007 23:17:05 GMT

clive_long wrote:

Hauke-m wrote:Thank you for this patch. Now bridged network is working with my kernel 2.6.23-rc8 with Wireless LAN.

I have updated the patch to also work when no wireless network is used. You can download it here:
http://www.hauke-m.de/fileadmin/vmware/vmware-wireless.patch

The patched vmnet.tar can be found here:
http://www.hauke-m.de/fileadmin/vmware/vmnet.tar (it is based on the vmnet out of the VMware Workstation 6.0.1)

Hi,

Can you please explain how to apply this? Looks like exactly the problem I am experiencing with wifi.

Ta, Clive

If I remember correctly:

(1) Download Hauke-m's patched vmnet.tar file from here:

http://www.hauke-m.de/fileadmin/vmware/vmnet.tar

(2) Go to /usr/lib/vmware/modules/source and rename the original vmnet.tar to vmnetOLD.tar or something like that.

(3) Copy Hauke-m's patched vmnet.tar to /usr/lib/vmware/modules/source/.

(4) Run vmware-config.pl.

That should do it.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clive_long — Thu, 25 Oct 2007 22:03:25 GMT

Hauke-m wrote:Thank you for this patch. Now bridged network is working with my kernel 2.6.23-rc8 with Wireless LAN.

I have updated the patch to also work when no wireless network is used. You can download it here:
http://www.hauke-m.de/fileadmin/vmware/vmware-wireless.patch

The patched vmnet.tar can be found here:
http://www.hauke-m.de/fileadmin/vmware/vmnet.tar (it is based on the vmnet out of the VMware Workstation 6.0.1)

Hi,

Can you please explain how to apply this? Looks like exactly the problem I am experiencing with wifi.

Ta, Clive

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

coenkd — Thu, 25 Oct 2007 21:19:00 GMT

Works too on workstation 6.0.0 build-45731. Thanx! (wireless Broadcom BCM4318 802.11g)

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sun, 21 Oct 2007 09:22:14 GMT

Hauke-m wrote:
From version 6.0.1 to version 6.0.2 VMWare made no changes in the vmnet.tar !

The patched version for wireless will work in version 6.0.2 as in version 6.0.1

That's good news, Hauke-m. Thanks.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Hauke-m — Sat, 20 Oct 2007 14:59:35 GMT

From version 6.0.1 to version 6.0.2 VMWare made no changes in the vmnet.tar !

The patched version for wireless will work in version 6.0.2 as in version 6.0.1

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sat, 20 Oct 2007 12:01:47 GMT

I can confirm that, on my system at least, Hauke-m's pre-patched vmnet.tar for WS 6.0.1 works equally well for WS 6.0.2. I've gotten both wifi and wired Internet working with no probs (Host = Arch Linux, Guest = WinXP SP2, bridged networking). I haven't done any additional testing.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sat, 20 Oct 2007 11:36:04 GMT

Hey, Hauke-m, have you by any chance had time to produce a pre-patched vmnet.tar for WS 6.0.2-build 59824? If not, can we assume that the vmnet.tar you patched for 6.0.1 will work also for 6.0.2?

Thanks again for your help with this worse-than-annoying problem.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sun, 30 Sep 2007 22:07:29 GMT

Thanks for the pre-patched vmnet.tar, Hauke-m. That makes life easier.

I went ahead and re-upgraded to 6.0.1 and replaced the stock vmnet.tar with your patched one. I can verify that, on my system at least, both wireless and wired bridged networking appear to function properly with Linux kernel 2.6.22.9 on the host and WinXP Pro SP2 as the guest.

I really appreciate this fix, funderburg (from linuxquestions.org), daguerre and Hauke-m. I was really frustrated before.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Hauke-m — Sun, 30 Sep 2007 18:47:58 GMT

Thank you for this patch. Now bridged network is working with my kernel 2.6.23-rc8 with Wireless LAN.

I have updated the patch to also work when no wireless network is used. You can download it here:
http://www.hauke-m.de/fileadmin/vmware/vmware-wireless.patch

The patched vmnet.tar can be founfd here:
http://www.hauke-m.de/fileadmin/vmware/vmnet.tar (it is based on the vmnet out of the VMware Workstation 6.0.1)

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Daguerre — Sun, 30 Sep 2007 02:22:38 GMT

Fixed!
http://www.linuxquestions.org/questions/showthread.php?p=2905568
VMWare 6.0.1 WinXP guest can now bridge my madwifi 0.9.3.2 interface, on Fedora using kernel 2.6.22.7.
Well, that was annoying!

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

2hansen — Sat, 29 Sep 2007 14:34:10 GMT

Thanks for the quick response. However, I did a clean install of 6.0.1 and my vmnet.tar does include the smac_linux.x{386|86_64}.o_shipped files - so I guess that is not the issue. (And sorry if "my" issue is different from the one discussed in this thread - but the symptoms seem identical.)

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sat, 29 Sep 2007 13:58:56 GMT

2hansen wrote:
Same goes for my Compaq nw8440. No bridging when host is using wireless, no problems when host uses wired... (Host: Ubuntu 7.10; Guest: XP Prof.)

You may be helped by this info from KevinG:

If you used the vmware-any-any-update, it replaced the original /usr/lib/modules/source/vmnet.tar file with a one that does not include vmnet-only/smac_linux.x386.o_shipped vmnet-only/smac_linux.x86_64.o_shipped. You will need to exact the vmnet.tar and insert the vmnet-only/smac_linux.x386.o_shipped
vmnet-only/smac_linux.x86_64.o_shipped that is included with the orginal
/usr/lib/modules/source/vmnet.tar in WS 6

These comments are from this thread:

http://communities.vmware.com/thread/104681?tstart=15

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

2hansen — Sat, 29 Sep 2007 11:56:03 GMT

Same goes for my Compaq nw8440. No bridging when host is using wireless, no problems when host uses wired... (Host: Ubuntu 7.10; Guest: XP Prof.)

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Daguerre — Mon, 24 Sep 2007 02:27:06 GMT

I'm using a Netgear WG311T. I just upgraded madwifi to the latest trunk, and no luck.

This is the first I've heard of ath5k! Sounds promising, but I could find any code. Is there an actual working development version for Linux?

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sun, 23 Sep 2007 18:37:55 GMT

No wifi Internet connection with my PCMCIA wifi adapter, either (Broadcom Corporation BCM4318 AirForce One 54g 802.11g Wireless LAN Controller).

My guest OS is Windows 2000 Pro SP4, by the way.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sun, 23 Sep 2007 18:18:33 GMT

Daguerre, you're right, at least according to my tests. Using kernel
2.6.22.6 (under Arch Linux) running WS for Linux 6.01 (build 55017) with a wired ethernet connection, I
get full networking, Internet included. When I have a wifi connection, I'm connected to
the LAN but not to the Internet.

My wifi adapter is Intel Corporation PRO/Wireless 2200BG internal. My machine is a Thinkpad T43.
Does this information lead us closer to a solution?

I also have a PCMCIA wifi adapter that I can test with to see if the problem is adapter-specific.

Note again that wifi and wireless work equally well with kernel 2.6.20 and WS for linux 6 as well as 6.01.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

KevinG — Sun, 23 Sep 2007 04:41:53 GMT

Have you tried using the ath5k?

What exact physical wireless network adapter are you using? (make/model..etc)

Are you using WS 6.0.1?

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Daguerre — Sun, 23 Sep 2007 04:00:39 GMT

I still have no internet from the guest OS with WS build 55017 on Fedora kernel 2.6.22.5-76.fc7. Note that my bridge is wireless, using madwifi 0.9.3.2. Perhaps ethernet bridges are working, but the wireless isn't.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Wed, 19 Sep 2007 14:43:56 GMT

Does anyone know if Build 55017 takes care of this
problem? I'm too lazy to install a new kernel to test
it.

Thanks.

An answer to my own question: Yes, my initial installation and tests show that bridged networking is working properly with VMWare Workstation for Linux 6.01 (build 55017) running on a 2.6.22 kernel. I have a functioning Internet connection using the same VMWare bridged networking configuration that I had been using with kernel 2.6.20.

Others will want to verify.

Thanks.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Wed, 19 Sep 2007 12:01:40 GMT

Does anyone know if Build 55017 takes care of this problem? I'm too lazy to install a new kernel to test it.

Thanks.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Davi-jvs — Sat, 08 Sep 2007 21:19:26 GMT

I get same problem and a create a second network connection host only to comunicate with host until we have a fix to this issue.

davi

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Wed, 05 Sep 2007 13:41:53 GMT

Has anybody got this problem solved, yet? I'm still holding off on a kernel upgrade until a solution appears.

Thanks.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

dkmaster — Mon, 06 Aug 2007 08:57:59 GMT

Having also problems with:
* Linux 2.6.22.1 for amd64 (SMP)
* VMWare Workstation 6.0.

My problem is that, network (bridge) works fine, except betwen host and client machine. If i set an "static route" to the virtual machine via my router, it starts working, i mean:

Host IP: 192.168.0.50 (linux 2.6.22.1)
Client IP: 192.168.0.150 (another linux machine, or windows or whatever)

Host: route add 192.168.0.150 gw 192.168.0.1 (route through my firewall)
Client: route add 192.168.0.50 gw 192.168.0.1 (route through my firewall also)

If i setup this way, the net works fine.

Note: Ping always works fine

Any new ideas?

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Hauke-m — Sun, 05 Aug 2007 11:51:25 GMT

The same problem with an rtl8187 based Wireless LAN Card with a mac80211 based driver.

wlan0 = rtl8187
ath0 = atheros (madwifi)
ifconfig -a

ath0 Protokoll:Ethernet Hardware Adresse 00:11:95:91:E4:C5
inet Adresse:192.168.0.2 Bcast:192.168.0.255 Maske:255.255.255.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:26788 errors:0 dropped:0 overruns:0 frame:0
TX packets:27677 errors:1 dropped:1 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:21942415 (20.9 MiB) TX bytes:4178869 (3.9 MiB)

eth0 Protokoll:Ethernet Hardware Adresse 00:17:31:68:7C:9B
inet Adresse:192.168.1.21 Bcast:192.168.1.255 Maske:255.255.255.0
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
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18

eth1 Protokoll:Ethernet Hardware Adresse 00:18:F3:2E:02:DA
inet Adresse:192.168.1.22 Bcast:192.168.1.255 Maske:255.255.255.0
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
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17

lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:112 errors:0 dropped:0 overruns:0 frame:0
TX packets:112 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:158460 (154.7 KiB) TX bytes:158460 (154.7 KiB)

vmnet1 Protokoll:Ethernet Hardware Adresse 00:50:56:C0:00:01
inet Adresse:172.16.104.1 Bcast:172.16.104.255 Maske:255.255.255.0
inet6 Adresse: fe80::250:56ff:fec0:1/64 Gültigkeitsbereich:Verbindung
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
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Protokoll:Ethernet Hardware Adresse 00:50:56:C0:00:08
inet Adresse:192.168.139.1 Bcast:192.168.139.255 Maske:255.255.255.0
inet6 Adresse: fe80::250:56ff:fec0:8/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wifi0 Protokoll:UNSPEC Hardware Adresse 00-11-95-91-E4-C5-00-00-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:148568 errors:112 dropped:1942 overruns:0 frame:110
TX packets:30326 errors:5778 dropped:1 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:199
RX bytes:35681373 (34.0 MiB) TX bytes:5504605 (5.2 MiB)
Interrupt:19

wlan0 Protokoll:Ethernet Hardware Adresse 00:15:AF:03:AB:79
inet Adresse:192.168.0.7 Bcast:192.168.0.255 Maske:255.255.255.0
inet6 Adresse: fe80::215:afff:fe03:ab79/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2125 errors:0 dropped:0 overruns:0 frame:0
TX packets:2599 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:1731552 (1.6 MiB) TX bytes:363285 (354.7 KiB)

wmaster0 Protokoll:UNSPEC Hardware Adresse 00-15-AF-03-AB-79-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING 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
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

Hauke-m — Sun, 05 Aug 2007 11:28:02 GMT

Hi
I' m using VMware Player with vmware-any-any-update-113 and kernel 2.6.22.1. The Host is Ubuntu and Windows XP SP2 is running in the VM. The network is bridged to a Atheros Wifi card with madwifi driver svn r2625.

I have got the same problem with the bridged network, witch isn't working. I can ping host computer from the VM but I can't ping any other computer in the network. At first the ping to the host computer doesn't work either (the first packeges get lost) but ater some time every package gets to the host.
But pinging to or from an other client in the network to the VM wasn't working, I had a 100% package lose.

In dmesg I saw this:

[ 33.728813] Capability LSM initialized
[ 34.170709] ppdev: user-space parallel port driver
[ 38.602161] /dev/vmmon[4108]: VMCI: Driver initialized.
[ 38.602377] /dev/vmmon[4108]: Module vmmon: registered with major=10 minor=165
[ 38.602511] /dev/vmmon[4108]: Module vmmon: initialized
[ 39.312700] /dev/vmnet: open called by PID 4155 (vmnet-bridge)
[ 39.312706] /dev/vmnet: hub 0 does not exist, allocating memory.
[ 39.312713] /dev/vmnet: port on hub 0 successfully opened
[ 39.312718] bridge-ath0: enabling the bridge
[ 39.312721] bridge-ath0: up
[ 39.312722] bridge-ath0: already up
[ 39.312724] bridge-ath0: attached
[ 39.503973] /dev/vmnet: open called by PID 4171 (vmnet-dhcpd)
[ 39.503981] /dev/vmnet: hub 1 does not exist, allocating memory.
[ 39.503989] /dev/vmnet: port on hub 1 successfully opened
[ 39.545852] /dev/vmnet: open called by PID 4182 (vmnet-dhcpd)
[ 39.545861] /dev/vmnet: hub 8 does not exist, allocating memory.
[ 39.545870] /dev/vmnet: port on hub 8 successfully opened
[ 39.574474] /dev/vmnet: open called by PID 4187 (vmnet-natd)
[ 39.574484] /dev/vmnet: port on hub 8 successfully opened
[ 40.119746] ath0: no IPv6 routers present
[ 49.382333] /dev/vmnet: open called by PID 4327 (vmnet-netifup)
[ 49.382343] /dev/vmnet: port on hub 1 successfully opened
[ 49.479258] /dev/vmnet: open called by PID 4338 (vmnet-netifup)
[ 49.479351] /dev/vmnet: port on hub 8 successfully opened
[ 60.285972] vmnet8: no IPv6 routers present
[ 60.313897] vmnet1: no IPv6 routers present
[ 179.153537] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 179.153545] PCI: Setting latency timer of device 0000:01:00.0 to 64
[ 179.153917] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 18:21:22 PDT 2007
[ 285.679408] PCI: Setting latency timer of device 0000:01:00.0 to 64
[ 285.679854] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 18:21:22 PDT 2007
[ 5144.265295] /dev/vmnet: open called by PID 7604 (vmware-vmx)
[ 5144.265319] device ath0 entered promiscuous mode
[ 5144.265325] audit(1186306837.941:2): dev=ath0 prom=256 old_prom=0 auid=4294967295
[ 5144.265327] bridge-ath0: enabled promiscuous mode
[ 5144.265328] /dev/vmnet: port on hub 0 successfully opened
[ 5144.376053] /dev/vmmon[7607]: host clock rate change request 0 -> 19
[ 5148.506779] /dev/vmmon[7607]: host clock rate change request 19 -> 83
[ 5159.119272] device ath0 left promiscuous mode
[ 5159.119280] audit(1186306852.941:3): dev=ath0 prom=0 old_prom=256 auid=4294967295
[ 5159.119282] bridge-ath0: disabled promiscuous mode
[ 5159.119324] /dev/vmnet: open called by PID 7607 (vmware-vmx)
[ 5159.119339] device ath0 entered promiscuous mode
[ 5159.119342] audit(1186306852.941:4): dev=ath0 prom=256 old_prom=0 auid=4294967295
[ 5159.119344] bridge-ath0: enabled promiscuous mode
[ 5159.119346] /dev/vmnet: port on hub 0 successfully opened
[ 5363.546770] device eth0 entered promiscuous mode
[ 5363.546779] audit(1186307057.936:5): dev=eth0 prom=256 old_prom=0 auid=4294967295
[ 5363.606614] device eth1 entered promiscuous mode
[ 5363.606624] audit(1186307057.936:6): dev=eth1 prom=256 old_prom=0 auid=4294967295
[ 5363.622597] device vmnet1 entered promiscuous mode
[ 5363.622605] audit(1186307057.936:7): dev=vmnet1 prom=256 old_prom=0 auid=4294967295
[ 5363.638523] device vmnet8 entered promiscuous mode
[ 5363.638531] audit(1186307057.936:8): dev=vmnet8 prom=256 old_prom=0 auid=4294967295
[ 5363.654481] device lo entered promiscuous mode
[ 5363.654488] audit(1186307057.936:9): dev=lo prom=256 old_prom=0 auid=4294967295
[ 5402.988610] device eth0 left promiscuous mode
[ 5402.988619] audit(1186307097.436:10): dev=eth0 prom=0 old_prom=256 auid=4294967295
[ 5403.004574] device wifi0 left promiscuous mode
[ 5403.004578] audit(1186307097.436:11): dev=wifi0 prom=0 old_prom=256 auid=4294967295
[ 5403.036483] device eth1 left promiscuous mode
[ 5403.036490] audit(1186307097.436:12): dev=eth1 prom=0 old_prom=256 auid=4294967295
[ 5403.052439] device vmnet1 left promiscuous mode
[ 5403.052445] audit(1186307097.436:13): dev=vmnet1 prom=0 old_prom=256 auid=4294967295
[ 5403.068398] device vmnet8 left promiscuous mode
[ 5403.068404] audit(1186307097.436:14): dev=vmnet8 prom=0 old_prom=256 auid=4294967295
[ 5403.100316] device lo left promiscuous mode
[ 5403.100325] audit(1186307097.436:15): dev=lo prom=0 old_prom=256 auid=4294967295

In Wireshark I saw that vmware is sending an arp request 3 times "Who has 192.168.0.1? Tell 192.168.0.113" (192.168.0.1 is the IP of my router with OpenWRT and 192.168.0.113 is the IP of the Windows in the VM) but he doesn't get an response. At the same time the ping to the host is running very well.

Is there any kernel configuration with witch vmware's bridged network isn't working?

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Fri, 03 Aug 2007 13:42:09 GMT

Also tried with any-any patch 113, same results
(compiles fine, but no network on XP guest...)

Really no idea ??? As clawhead, when I boot on a
2.6.21 kernel and reconfigure vmware (without
changing network parameters), it works perfectly...

Yep, I tried any-any patch 113 and still get exactly the same results as lbalogh.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

lbalogh — Fri, 03 Aug 2007 10:21:21 GMT

Also tried with any-any patch 113, same results (compiles fine, but no network on XP guest...)

Really no idea ??? As clawhead, when I boot on a 2.6.21 kernel and reconfigure vmware (without changing network parameters), it works perfectly...

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

lbalogh — Mon, 30 Jul 2007 13:22:04 GMT

Hello,

I have the same problem here : bridged networking works perfectly with kernel <= 2.6.21, and not since 2.6.22.

VMware version
Workstation build 45731 with any-any patch 112

Host OS
Debian SID 32-bit, Kernel 2.6.23 rc1 git 5 (but same problem with 2.6.22)

Guest OS
Windows XP Home 32-bit

ifconfig -a from host
eth0 Link encap:Ethernet HWaddr 00:15:C5:4F:03:2B
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:3

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:60 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3028 (2.9 KiB) TX bytes:3028 (2.9 KiB)

wlan0 Link encap:Ethernet HWaddr 00:18:DE:6F:F1:FD
inet addr:192.168.1.34 Bcast:255.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9871 errors:0 dropped:0 overruns:0 frame:0
TX packets:8140 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8316260 (7.9 MiB) TX bytes:1241949 (1.1 MiB)

wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-6F-F1-FD-00-00-00-00-00-00-00-00-00 -00
UP BROADCAST RUNNING 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)

ipconfig /all from guest
Configuration IP de Windows

Nom de l'hôte . . . . . . . . . . : twinky
Suffixe DNS principal . . . . . . :
Type de noud . . . . . . . . . . : Inconnu
Routage IP activé . . . . . . . . : Non
Proxy WINS activé . . . . . . . . : Non

Carte Ethernet Connexion au réseau local 2:

Suffixe DNS propre à la connexion :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

Adresse physique . . . . . . . . .: 00-0C-29-02-72-B1
DHCP activé. . . . . . . . . . . : Non
Adresse IP. . . . . . . . . . . . : 192.168.1.125
Masque de sous-réseau . . . . . . : 255.255.255.0
Passerelle par défaut . . . . . . : 192.168.1.1
Serveurs DNS . . . . . . . . . . : 195.186.1.162
195.186.4.162

Result of ps -ef | grep bridge
root 3198 1 0 13:18 ? 00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 wlan0

.vmx file of guest
#!/usr/bin/vmware
config.version = "8"
virtualHW.version = "6"
scsi0.present = "FALSE"
memsize = "512"
MemAllowAutoScaleDown = "FALSE"
ide0:0.present = "TRUE"
ide0:0.fileName = "Windows XP Home Edition-000002-cl1.vmdk"
ide0:0.writeThrough = "TRUE"
ide1:0.present = "TRUE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
ethernet0.present = "TRUE"
usb.present = "TRUE"
sound.present = "TRUE"
sound.virtualDev = "es1371"
displayName = "Win XP - Ludo"
guestOS = "winxphome"
nvram = "Win XP - Ludo.nvram"

numvcpus = "1"
floppy0.present = "FALSE"

ide0:0.redo = ""
ide1:0.startConnected = "FALSE"
ethernet0.addressType = "generated"
uuid.location = "56 4d 7b 2c 46 a2 fe 07-15 df ab 9e 12 02 72 b1"
uuid.bios = "56 4d 7b 2c 46 a2 fe 07-15 df ab 9e 12 02 72 b1"
ethernet0.generatedAddress = "00:0c:29:02:72:b1"
ethernet0.generatedAddressOffset = "0"
tools.syncTime = "TRUE"

virtualHW.productCompatibility = "hosted"
tools.upgrade.policy = "manual"
checkpoint.vmState = ""

uuid.action = "create"

checkpoint.vmState.readOnly = "FALSE"

extendedConfigFile = "Win XP - Ludo.vmxf"

isolation.tools.hgfs.disable = "FALSE"

sharedFolder.option = "alwaysEnabled"
sharedFolder.maxNum = "1"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.writeAccess = "TRUE"
sharedFolder0.hostPath = "/media/sda4"
sharedFolder0.guestName = "D"
sharedFolder0.expiration = "never"

pciBridge0.present = "TRUE"
ehci.present = "TRUE"

pciBridge0.pciSlotNumber = "17"
ethernet0.pciSlotNumber = "32"
sound.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"

usb.autoConnect.device0 = ""

usb.autoConnect.device1 = ""

usb.generic.autoconnect = "TRUE"

ide1:0.autodetect = "TRUE"

inVMTeam = "FALSE"

ethernet0.connectionType = "bridged"
ethernet0.vnet = "/dev/vmnet0"

-----------------------------------------

I can post more informations if needed. Thanks for your help.

edit : forgot to say that I have messages like :
Jul 30 13:18:17 twinky vmnet-detect[3203]: Unable to initialize the daemon

in /var/log/syslog, don't know if it is "normal"...

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sat, 28 Jul 2007 18:33:11 GMT

Hi,

Without the /usr/bin/vmnet-bridge process running you
will not be able to use Bridged networking. You may
be able use NAT if that's an option for you.

But I am able to use bridged networking with kerneal 2.6.20.

It's possible that you had compile errors with vmnet
module and this is why /usr/bin/vmnet-bridge is not
running.

Have you tried Petr's any-any-update112 patch?

Yes, that's what permitted me to compile modules against the 2.6.22 kernel. At least it appeared that the modules all compiled correctly. The compilation process appared to complete when I used the any-any-update112 patched kernel 2.6.22. But maybe I missed an error message.

I'll run the tests again later today and report back.

Thanks.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

KevinG — Sat, 28 Jul 2007 18:00:08 GMT

Hi,

Without the /usr/bin/vmnet-bridge process running you will not be able to use Bridged networking. You may be able use NAT if that's an option for you.

It's possible that you had compile errors with vmnet module and this is why /usr/bin/vmnet-bridge is not running.

Have you tried Petr's any-any-update112 patch?

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sat, 28 Jul 2007 15:08:21 GMT

Thanks, KevinG, for the help with this. Unfortunately, I still don't have proper networking with a 2.6.22 kernel even after I ensure that vmnet0 is bridged to eth1.

As I said, when I use the same configuration but with a 2.6.20 kernel, all is well. Strangely, however, the output of "ps auwww | grep -i bridge" still doesn't display as you said it would, even though networking and Internet are working fine. Here's what I get from "ps auwww | grep -i bridge":

root 8024 0.0 0.0 3180 772 pts/2 R+ 11:04 0:00 grep -i bridge

I think I'll drop this for now and just wait for the community and/or the VMWare people to get things jiving again.

Regardless, I learned more about VMware's inner workings thanks to your suggestions.

Re: No Internet on VMWare WS w/ Linux 2.6.22 kernel

KevinG — Sat, 28 Jul 2007 13:45:00 GMT

Hi clawhead,

The output from " ps auwww | grep -i bridge " should have looked something like the following

root 6841 0.0 0.0 1504 160 pts/0 S 21:38 0:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth1

In your case, vmnet0 is not Bridged to any interface on the host and this is why you have no networking.

Run vmware-config.pl script again and select the "Editor" option when making network changes. When prompted for the network # to change, select 0 (zero) and configure for "Bridged" using "eth1"

No Internet on VMWare WS w/ Linux 2.6.22 kernel

clawhead — Sat, 28 Jul 2007 05:51:02 GMT

I'm able to use VMWare WS v. 6.x with no problems on kernel 2.6.20, but not with the current 2.6.22 kernel. I've applied the any-any patch build 112, which permitted me to compile all modules. VMWare loads and will boot my guest OS (Win2K Pro). All is fine with the guest -- but no Internet connection. If I revert to an older kernel and recompile modules, everything is hunky-dorey again.

Here's the pertinent info:

(1) Output from ifconfg -a on host:

eth0 Link encap:Ethernet HWaddr 00:15:58:2F:B2:AA
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:16

eth1 Link encap:Ethernet HWaddr 00:16:6F:BA:6E:5A
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::216:6fff:feba:6e5a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39303 errors:0 dropped:2 overruns:0 frame:0
TX packets:38288 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:33077558 (31.5 Mb) TX bytes:8409858 (8.0 Mb)
Interrupt:22 Base address:0xe000 Memory:b4001000-b4001fff

irda0 Link encap:IrLAP HWaddr 00:00:00:00
NOARP MTU:2048 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:8
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

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:1711 errors:0 dropped:0 overruns:0 frame:0
TX packets:1711 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2344355 (2.2 Mb) TX bytes:2344355 (2.2 Mb)

(2) Using bridged networking.

(3) Output from psauwww | grep -i bridge:

username 16693 0.0 0.0 3176 768 pts/4 R+ 01:41 0:00 grep -i bridge

(4) .vmx file for virtual machine:

#!/usr/bin/vmware
config.version = "8"
virtualHW.version = "6"
scsi0.present = "TRUE"
memsize = "1024"
MemAllowAutoScaleDown = "FALSE"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "Windows 2000 Professional.vmdk"
ide1:0.present = "TRUE"
ide1:0.autodetect = "TRUE"
ide1:0.deviceType = "cdrom-raw"
floppy0.startConnected = "FALSE"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.wakeOnPcktRcv = "FALSE"
usb.present = "TRUE"
ehci.present = "TRUE"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
svga.autodetect = "TRUE"
pciBridge0.present = "TRUE"
isolation.tools.hgfs.disable = "FALSE"
displayName = "Windows 2000 Professional"
guestOS = "win2000pro"
nvram = "Windows 2000 Professional.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "hosted"
RemoteDisplay.vnc.port = "0"
tools.upgrade.policy = "useGlobal"

floppy0.fileName = "/dev/fd0"

ide1:0.startConnected = "TRUE"
ethernet0.addressType = "generated"
uuid.location = "56 4d 8a 9a c8 f4 fd e6-37 23 07 ea 06 d6 b5 ee"
uuid.bios = "56 4d 8a 9a c8 f4 fd e6-37 23 07 ea 06 d6 b5 ee"
scsi0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
scsi0.pciSlotNumber = "16"
ethernet0.pciSlotNumber = "32"
sound.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
ethernet0.generatedAddress = "00:0c:29:d6:b5:ee"
ethernet0.generatedAddressOffset = "0"
ide1:0.fileName = "auto detect"
tools.syncTime = "FALSE"

extendedConfigFile = "Windows 2000 Professional.vmxf"
sharedFolder.option = "alwaysEnabled"
sharedFolder.maxNum = "2"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.writeAccess = "TRUE"
sharedFolder0.hostPath = "/home/claw/Docs"
sharedFolder0.guestName = "Home-Claw-Docs on Arch Linux"
sharedFolder0.expiration = "never"

ethernet0.connectionType = "bridged"
#ethernet0.vnet = "/dev/vmnet0"

ethernet0.startConnected = "TRUE"

sharedFolder1.present = "TRUE"
sharedFolder1.enabled = "TRUE"
sharedFolder1.readAccess = "TRUE"
sharedFolder1.writeAccess = "TRUE"
sharedFolder1.hostPath = "/home/ftp"
sharedFolder1.guestName = "Home-Ftp on Arch Linux"
sharedFolder1.expiration = "never"

(5) ipconfig /all on guest OS (Win2K Pro):

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : vmware-arch
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-D6-B5-EE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.47.239
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

Thanks for any advice. Meanwhile, it's not that big a deal to revert to an older kernel, but this is the sort of thing that I like to get to the bottom of if possible.