I am running Virtual-Box (VB) 4.3.18 in Opensuse 13.2
From the outset all VB’s dependencies were installed through Opensuse’s Software manager, including host modules and Extension Pack. VB is set to Bridged Adapter, (enp3s0) and the USB Alfa adapter is checked under VB’s USB settings.
I am running KDE’s Network Manager,(NM) not Wicked and on starting up VB I plug in the Alfa and it is not recognised, despite the fact that KDE’s NM recognises it as wireless device looks for Wireless Networks.
Moving on, when I run Kali 1.09 in VB and run ‘airmon-ng start wlan0’ in terminal I get this output;
Found 2 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
2274 dhclient
2399 NetworkManager
I have only had this problem in Opensuse and not in other distro’s that are Ubuntu/Debian based.
I really like using OpenSuse and would like to go on using it as my main OS and would appreciate any help in advance.
This is due to the fact that you are using the Bridged Adapter setting as enp3s0 rather than wlan0.
The wireless card it not getting passed on to kali as “wlan0”. It is not being understood. Shutdown VB and start Yast.
The name needs to be changed in Yast Network Settings.
What I would try is:
Navigate to Yast–>Network Devices–>Network Settings
Click on the Global tab and switch to Wicked to edit the name of the wireless card
Click on the Overview tab and select enp3s0
Click on Edit and then the Hardware tab
Next to Device Name - click on the Change button
Change the name from [FONT=Courier][size=2]enp3s0 to wlan0 and click on the OK and Next buttons[/size]
[/FONT]
You should see the changes immediately. Now switch from Wicked Service to Network Service.
The next you start up VB, wlan0 will be recognized.
stevecrt,
You should post the results of either following command (only one is sufficient) to verify how your HostOS identifies your USB adapter. If your adapter was a PCI device I would agree with Romanator but because it’s a removable USB device I can’t know for sure
ip addr
ifconfig
I haven’t tried to run a wireless pentest suite from a virtualized Guest recently, so I don’t know if you can just configure your USB NIC the normal way instead of configuring a pass through (direct hardware access). Direct hardware access was required years ago, but I think that may have been resolved within the past few years. You could also run the above command(s) from within your Guest to identify your interface labels and simply modify your “airmon-ng” command line.
When you say you are able to run your airmon-ng command for a short period of time, are you actually able to do anything like do a capture (or for that matter scan for available
A clean and easy alternative is to run your pentest from within a Linux container (LXC using YAST or Docker) if your HostOS is Linux. That way Kali gets direct hardware access while still being isolated from your HostOS (if that is your objective).