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.

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

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

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/

Excellent, thanks a lot!!

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!