I'm running Kali Linux 64bit 1.07 as a guest os through virtualbox 4.3.12 r93733. I've also installed the VirtualBox 4.3.12 Oracle VM VirtualBox Extension Pack. I have bridged my hosts network connection (Intel(R) Wireless-N 7260) with Kali and I have set up the Alfa 036nha as a usb device for Kali through virtualbox.
iwconfig in Kali gives no wireless extensions.
The Alfa AWUS 1900 looks like a dead spider, at first glance – a body with all legs in the air. But the four antennas that attach to the main body pull in wifi signals from the ether with surprising power for such a small, light little unit. To unload the 88XXau driver run the rmmod command: rmmod 88XXau. Followed by the modprobe command to load the 88XXau driver: modprobe 88XXau. Fire up airodump-ng again and you will see WLANs broadcasting around you! This is the end of part 2 on how to set up your Alfa Network AWUS1900 for wireless penetration testing using Kali Linux.
ifconfig shows my bridged connection and Local loopback.
lsusb shows:Bus 001...... Atheros Communications, inc. AR9271 802.11n
I thought that maybe it didn't have the right drivers so i tried to apt-get install firmware-atheros but it said that it was already installed.
I really don't know what I should do here.. anyone care to help me out?You should now that I'm not too good with Linux etc.
Edit:I found this https://www.youtube.com/watch?v=K1ETBeRQBs4Which helped me getting the Alfa card to work in Kali. The trick was to add a new custom USB device in virtualbox where you just take the vendor ID and product ID from the alfa device and leave the other boxes blank.
So now when i run ifconfig I get that wlan0 is up (Alfa) but eth0 is down (Intel(R) Wireless-N 7260).
Now however the problem is that when I plug in the Alfa device my network connection from my other wifi ceases to work (Intel(R) Wireless-N 7260) (the connection bridged from my host). It disconnects in the host aswell. If I connect to a wifi (with 7260) in the host with kali and alfa running the alfa stops working in Kali... I want to have them both running.
Anyone knows how to fix that?
![Alfa Awus 1900 Drivers Alfa Awus 1900 Drivers](/uploads/1/2/4/9/124990971/879835315.jpg)
grateful_n00bz0rgrateful_n00bz0r
6 Answers
Buy powered usb hub + Y cable, run adapter through thstUsually problem is electricity with usb can't provide enough for adapter.
BotmasterBotmaster
I tried everything on this post without success, the blinking green icon on the USB controller wasn't happening for me.
So after researching for some hours, and trying several ways to troubleshoot the issue, the answer for me was to set the USB 3.0 (xHCI) Controller under USB settings on virtual box, I believe this feature is available on Virtual box 5.0.16 and up.
bummi1,55133 gold badges1414 silver badges2222 bronze badges
Jaime PoloJaime Polo
This somehow solved my problem https://www.youtube.com/watch?v=K1ETBeRQBs4.The additional problem I talked about only seems to be present sometimes and most of the times both wlan interfaces work.
grateful_n00bz0rgrateful_n00bz0r
This answer fixed this issue exactly as described above.
Try to uninstall and reinstall the firmware if it already exists:
Kevin Panko6,0791111 gold badges3636 silver badges4848 bronze badges
NetsecNetsec
If anyone followed the video the OP posted, got wlan0 showing up in
ifconfig
but are stuck with the virtual box USB indicator blinking redFrom Youtube user Stas Sorokin posted in the Youtube comments of the video mentioned by the OP:
The trick is to go to your kali settings in VB go to network, select 'enable network adapter' and the 'not attached' option then run virtual box with kali linux, then after kali loads connect the network adapter, and let it load. After half a minute go to Devices -> usb devices -> and select your adapter
Then it should load.
CynapseCynapse
Running Kali 2019.1, on VirtualBox.
do
sudo apt update; sudo apt install realtek-rtl88xxau-dkms;
Once I did that, I heard my Alfa disconnect and reconnect from Windows, and all of a sudden, I had wlan0 interface. No reboot needed.
source:https://www.kali.org/releases/kali-linux-20171-release/
AriAri
Not the answer you're looking for? Browse other questions tagged linuxnetworkingwireless-networkingvirtualbox or ask your own question.
I think Windows 10 was released in a haphazard way by Microsoft even when there were so many bugs yet to be removed after getting feedback for technical preview version. I had no issue on my licensed Windows 7 Home and before upgrading to Windows 10. I carried out compatibility test with my already installed apps and drivers. And at that stage it gave me 1 incompatibility issue with an app. And once I upgraded to windows 10 my IDT sound driver, Alfa AWUS036H and so many other apps were corrupted / defunct. Windows 10 is an immature OS with a lot of backward compatibility issues. The installation of older apps in compatibility mode is seemed to be an eyewash. Only 1% apps successfully get installed in that mode. It's my biggest mistake that I trusted this OS and ruined my stable Windows 7 OS. I have more than 1500 Apps installed on my PC and startup shows only a few. Some services start up during boot and remains closed in next boot. I had a loss of huge amount of money coz of cancelling my contract with my client as a freelancer coz I ruined up my needed apps after upgrading it to windows 10. Sometimes system hangs up without any warning. Event viewer shows usb driver issue. Watch Dog blue screen of death. Stub error during Access Control. All **** is going on.
You can use AWUS036H by simply pointing to the win64 or win86 folder to update driver but now u cannot use your awus036h to control its power or as an AP.
![Alfa awus 1900 drivers free Alfa awus 1900 drivers free](/uploads/1/2/4/9/124990971/646928298.jpg)
But it hardly matters to Microsoft coz they are not having pain for you.
May be Mr Bill Gates being a Software Engineer get some time to develop empathy and feel some pain for us in which we engineers are entangled after getting this buggy OS installed in our machines.