clawhead
Contributor
Contributor

No Internet on VMWare WS w/ Linux 2.6.22 kernel

Jump to solution

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.

(1) Reboot - McCain (2) Reformat - Clinton (3) Install new OS - Obama
0 Kudos
63 Replies
k31k0
Contributor
Contributor

First, sorry for reopening the thread.

It seems that I can't download the patch. When I try to download the file , my browser is saying "Waiting for www.hauke-m.de..." and it never starts downloading Smiley Sad

Please help me...

0 Kudos
Hauke-m
Enthusiast
Enthusiast

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.

0 Kudos
imacamper
Contributor
Contributor

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

0 Kudos
MentholMoose
Enthusiast
Enthusiast

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

----- {color:#555555}Kirk Kosinski{color} [!http://www.kirkkosinski.com/li.png!|http://www.linkedin.com/in/kirkkosinski] {color:#999999}MCITP: EA / VA / EDA7, VCP 4{color}
0 Kudos
Chris_Morgan
Contributor
Contributor

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

0 Kudos
mrvanes
Contributor
Contributor

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.

0 Kudos
Unail
Contributor
Contributor

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

0 Kudos
clawhead
Contributor
Contributor

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.

(1) Reboot - McCain (2) Reformat - Clinton (3) Install new OS - Obama
0 Kudos
mrvanes
Contributor
Contributor

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

0 Kudos
Hauke-m
Enthusiast
Enthusiast

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:

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: and here

0 Kudos
mrvanes
Contributor
Contributor

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.

0 Kudos
2hansen
Contributor
Contributor

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

0 Kudos
Lxxa
Contributor
Contributor

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

0 Kudos
Hauke-m
Enthusiast
Enthusiast

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/

0 Kudos
Lxxa
Contributor
Contributor

Works great now! Thank You!

0 Kudos
2hansen
Contributor
Contributor

Excellent, thanks a lot!!

0 Kudos
jimbo45
Enthusiast
Enthusiast

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

0 Kudos
clawhead
Contributor
Contributor

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

(1) Reboot - McCain (2) Reformat - Clinton (3) Install new OS - Obama
0 Kudos
Chronniff
Contributor
Contributor

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

0 Kudos
LinuxFreakus
Contributor
Contributor

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!

0 Kudos