Dear All,
Hope all of you fine
my question is i have virtual network version 5.1.2, i am using windows 7, with host Linux Ubuntu.
i have one TPlink Wifi adopter N727 which is connect with my window's and working fine.
i use backtrack for Linux its working fine but which i use ifconfig its only given eth0 and lo
also when i use airmon-ng its not showing any wlan0
i watch many video and try BRIDGED ADOPTER in network option but still not work
i also try USB Setting but it not work
only given in Wicd network manager that no wireless network found
Please Please Guys Help me please
Wifi Adopter is not showing in Linux
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Wifi Adopter is not showing in Linux
We need to see the guests log file ( as an attachment ) to make sure you know the difference of host and guest, but if you are trying to get the guest to see a wireless adapter it does not. It only sees a wired virtual adapter unless you use USB and dedicate it to the guest.
-
JSA
- Posts: 26
- Joined: 25. Aug 2016, 03:24
- Primary OS: openSUSE
- VBox Version: OSE other
- Guest OSses: Windows Linux
- Location: USA
Re: Wifi Adopter is not showing in Linux
Shahzaib,
For Most applications using NAT will work fine. Some large UDP streams can cause a problem of stuttering and buffering.
It is not always possible to Alias a wireless nic, which is what Bridged requires.
So VirtualBox uses some special tricks to make this work, but the end result is that the Virtual Machine thinks it has a regular wired network card, and you will still have to configure the Wireless card in the host.
Really, you only want to define a wireless nic once, in the host, rather than once in each virtual machine anyway. So this works better.
For Most applications using NAT will work fine. Some large UDP streams can cause a problem of stuttering and buffering.
It is not always possible to Alias a wireless nic, which is what Bridged requires.
So VirtualBox uses some special tricks to make this work, but the end result is that the Virtual Machine thinks it has a regular wired network card, and you will still have to configure the Wireless card in the host.
Really, you only want to define a wireless nic once, in the host, rather than once in each virtual machine anyway. So this works better.