Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On 8/26/07, Derek Atkins <warlord-3s7WtUTddSA at public.gmane.org> wrote: > Historically VMware has had trouble bridging to a wireless device. > I don't know if it's been fixed now, but think about it: the way > bridging works is by "faking" a new MAC address on the network. > But for Wireless devices, the mac address is part of the association, > so vmware would need to associate to the AP, which is probably doesn't > know how to do on its own. > > So I wouldn't expect bridging to work to a wireless device. I have been bridging VMware to wireless devices for many years, so that is not the issue :-) Generally, VMNet0 is your first bridged interface (eth0), VMNet1 is your Host-Only configuration interface, and if you have another interfeace, VMNet2 is bridged to your wireless device (eth1/wlan0/etc). You can configure this using vmware-config.pl if you like... However, your wireless may be flaky perhaps? -- Kristian Erik Hermansen -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |