In my experience, the vmware bridge does not work if the interface is not connected to the network during host start up.
This could be your problem. When the system starts and the vmnet-bridge proces starts, wlan0 is not yet connected to the wireless lan.

You can restart the bridge by killing and then relaunching it's process as follows:

# ps -eaf|grep vmnet-bridge
root 4533 1 0 Jun03 ? 00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0

Note the process ID (4533 in my case). Kill the bridge process and then restart it using the same command line shown in the output from the ps command:

# kill 4533
# /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0

It would take a little work, but I suppose you could write a script to do this.... ping the gateway until it responds (at which point you know wlan0 is connected) and then kill and restart the bridge.

http://communities.vmware.com/thread/95630

The patch is working! I did following steps as root:

1) Download and apply the patch:

• cd /tmp
• tar xvf /usr/lib/vmware/modules/source/vmnet.tar
• wget http://www.hauke-m.de/fileadmin/vmware/vmware-wireless.patch
• patch -p0 < vmware-wireless.patch
• tar cvf vmnet.tar vmnet-only
• mv /usr/lib/vmware/modules/source/vmnet.tar /usr/lib/vmware/modules/source/vmnet.orig.tar
• mv vmnet.tar /usr/lib/vmware/modules/source/vmnet.tar

• vmware-config.pl

Everything works now. I wonder when VMware is going to make bridging to work offcially on wireless adapters as it used to work before.

BR,

-T

-T