Alfa Wifi Adapter Driver Linux

0 views

Skip to first unread message

Lorna Schildt

unread,

Aug 3, 2024, 4:52:54 PM8/3/24

to otcihalnea

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.

Edit:I found this =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.

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.

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.

after installed this driver (need run installed file "an administrator" and "compatibility mode for Vista" (maybe can mode for Win7 - i not tested it) AWUS036NHA device was detected by Win10 as TP-LINK Wireless USB Adapter

AWUS036NHA (TP-LINK Wireless USB Adapter) switches between systems without any problems. at boot VB Kali - disconnected from Win10 and connect to Kali, after Kali shutdown, device connected to Win and show in device manager again.

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

hey
I have a problem with wifi adapter Alfa AWUS036ACS based on chipset Realtek RTL8811AU. I tried install kmod-rtl8xxxu , kmod-rtl8812au-ct but my device is only visable when I put ifconfig -a , when I putting ifconfig only visable in terminal is wlan0 basic chipset Raspberry Pi 4 B. Anyone have idea what is wrong?

I have an Alfa AWUS036ACS dongle with RTL8811AU chipset which I used as my daily driver WAP for over a year on a GLi router with rock-solid reliability. So whatever driver GL-iNet had produced for their firmware (for the Brume devices) is rock solid stable, but I have not figured out how to tell if those patches will be, or are, upstreamed.

The driver claims that can be compiled with OpenWrt and also have been tested against a recent version. Here the problem is that there is not a compiled package from to where install it. Hope that someone merge the code and it should work...

The RTL8812AU chipset is great, but almost no linux distro supports it out of the box. Android does support some OTG ethernet adapters, but since all phones and tablets have wifi integrated, there is no need to provide support for external wifi adapters. So if even linux support is thin and Androids support for external wifi is too, your chances of getting the Alfa adapter to run with a android tablet are also not very high.
And there is no version of QGC for Edge on Android.

You are right, QGC is supported by Android, but Emlid uses a specific version of QGC, QGC for Edge and they do not provide an Android version, because the Alfa adapters used with the Edge (which are an integral part of the advertised features of the Edge) are not supported by Android. Android is based on Linux, but you can not just install missing drivers, wifi adapters do not all use the same basic drivers, like external storage or usb cams do and as I said before, every Android device has build in wifi. Why should the manufacturer bother to include third party wifi drivers.

you will certainly understand that I am taking the first steps in Edge / Px4 systems etc coming from DJI systems that I decided to abandon. I am not a novice of APR but of Edge, PX4 etc. unfortunately yes