PDA

View Full Version : VMWare/Wireless Emulation - Still a problem?



hikkakaru
10-03-2008, 09:52 AM
I remember that running the VMWare edition BT3 would not allow proper use of any of the WiFi tools due to the fact that VMWare bridges the connection instead of trying to emulate hardware control over to the running virtual machine, thus gaining internet access from the wireless card but not gaining finer controls of the card (packet injection, etc.)..

Is this still the case? I tried searching to no real good answers.

Thanks guys.

imported_BaconZombie
10-03-2008, 10:02 AM
USB Wireless NIC's work perfect via VMWare.

hikkakaru
10-03-2008, 08:41 PM
USB Wireless NIC's work perfect via VMWare.

because VMWare most likely can get full control over USB devices, but that doesn't answer my question.

I can assume though that since your telling me that USB devices work properly, that internal NIC's do not work due to bridging?

imported_=Tron=
10-04-2008, 12:32 PM
because VMWare most likely can get full control over USB devices, but that doesn't answer my question.

I can assume though that since your telling me that USB devices work properly, that internal NIC's do not work due to bridging?This assumption is correct, VMware can only obtain full control of the wireless interface if it is connected through USB.

thoughtscreen
10-04-2008, 02:23 PM
Im having an issue with my alfa usb device only after upgrading vmware from 6.0 to 6.5. The device will disappear from vista's device manager and then show in backtrack in managed mode so it looks like backtrack has full control. But if i try to put it into monitor mode or scan for access points, it just hangs until I unplug the device after 5 minutes of waiting. If i try to bring up lan manager too it just hangs at initializing and then crashes.

I'll install ndiswrapper and see if i can do anything with that.

hikkakaru
10-10-2008, 02:21 AM
This assumption is correct, VMware can only obtain full control of the wireless interface if it is connected through USB.

Okay, I appreciate the clarification.

I assume that this is because bridging is more-or-less forwarding TCP/IP info from the windows controlled NIC instead of having the VM'd OS have fine controls of the NIC itself, thus every TCP/IP connection is emulated towards the VM OS to look as if its just a run of the mill , connected, TCPIP connection?

terminal86
10-10-2008, 02:35 AM
I assume that this is because bridging is more-or-less forwarding TCP/IP info from the windows controlled NIC instead of having the VM'd OS have fine controls of the NIC itself, thus every TCP/IP connection is emulated towards the VM OS to look as if its just a run of the mill , connected, TCPIP connection?

I tried about 5 times to read this sentence, but it's confusing :eek:

hikkakaru
10-10-2008, 03:29 AM
I tried about 5 times to read this sentence, but it's confusing :eek:

Haha I was waiting for that. Try as I might, I wasn't able to simplify it without going a different route. Lets try that this post.

In a normal Linux installation, the Linux kernel would be responsible for taking a piece of hardware, reading preset driver parameters in accordance to the detected hardware, and using and applying the options that are available with that set of hardware by itself.

In a Virtual Machine instance of Linux, the host machine is responsible for driving the hardware that the Virtual Machine Linux is going to be using. To make this easier on everyone for compatibilities sake, it seems as if VMWare lets the host machine take full responsibility of this and, for lack of a better way to explain my thinking process, shares generalized benefits of the hardware. An example . VMWare Linux CANNOT DIRECTLY CONTROL wireless network interfaces, HOWEVER, a Wireless Network Interface CAN be used to connect VMWare Linux to the internet via internet sharing made possible with bridging.

Is this thought process correct? I'm unsure, but from what I am gathering with my experience and others, that's about the gist of it.

imported_=Tron=
10-10-2008, 04:42 AM
Okay, I appreciate the clarification.

I assume that this is because bridging is more-or-less forwarding TCP/IP info from the windows controlled NIC instead of having the VM'd OS have fine controls of the NIC itself, thus every TCP/IP connection is emulated towards the VM OS to look as if its just a run of the mill , connected, TCPIP connection?Yes, in order for the guest OS to be able to take full control of the wireless interface it needs to be detached from the host OS first. WMware is able to recognize an USB card and take control of it, but only able to utilize the actual connection by bridging it from the host OS in case it is an integrated card.