USB-WiFi VS 8814au

For Wifi, things with the ath9k was the gold standard for a while, though then Qualcomm bought Atheros, but supposedly the followup ath10k/11k/12k drivers are decent too.

Mediatek MT76xx/79xx (mt76 driver) are also considered very good.

See https://github.com/morrownr/USB-WiFi/blob/main/home/USB_WiFi... (yes this is specifically about USB adapters, but usually the same driver is used for built-in WIFI in access points as well)

https://wireless.docs.kernel.org/en/latest/en/users/drivers....

I've already had a look at this but unsure how often it's updated, 6 months ago according to github: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

Just google "raspberry pi wifi adapter" or see https://github.com/morrownr/USB-WiFi

Just a note that if you're _serious_ about WiFi on the Raspberry Pi... you should use an external WiFi adapter—either PCIe or USB.

With the Compute Module 4, I've successfully tested a variety of adapters [1], from WiFi 6E to older mini PCIe and M.2 cards. There's even a board made for the purpose of multi-WiFi testing, the Seaberry [2].

The Raspberry Pi 5 works with all the PCIe WiFi chips I've tested (haven't had time to summarize testing on pipci database site yet, including a mt7921u-based WiFi 6E USB adapter (haven't written that up, but check out [3]).

[1] https://pipci.jeffgeerling.com/#network-cards-nics-and-wifi-...

[2] https://pipci.jeffgeerling.com/boards_cm/seaberry.html

[3] https://github.com/morrownr/USB-WiFi/issues/137#issuecomment...

Hey all, I've read the Github list of Linux WiFi adapters (https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md) but I've seen sporadic comments of certain users saying some haven't worked for them. I'm a bit risk averse buying something most likely from the USA and waiting a while for it to get to Australia and it not work, so I was hoping some people could comment with their specific models that have worked for them.

It would. These should work, as clients and in AP mode. https://github.com/morrownr/USB-WiFi

I ended up returning AWUS036ACM and buying AWUS1900 (based on Realtek chipset). Installed appropriate drivers https://github.com/morrownr/8814au and everything is working as expected! No issues so far. Working on both the Kali virtual machine and the raw Debian machine. Lesson learned - stay away from Mediatek.

I have same and got it to work using this driver on Github. The thing u/LoveFOSS recommended didn't work for me at all, but ymmv.

I've installed the driver for my NIC here

I'm trying to setup a local mumble server which clients can connect to over wifi, all provided by my AWUS1900 network card. I've gotten to the point where the NIC works with these instructions, and I setup a local AP following these instructions, but I cannot see the Mumble server running on the Pi3. I am able to connect to the hotspot but I can't ping any devices including the host of the whole server, strangely. When the pi is connected to ethernet to my local network, the mumble server works however.

However, if you're after long range or high speed with the Pi, and don't mind having to custom build a driver, I have this TP-Link Archer T9UH with the Realtek RTL8814au chipset. It needs this driver, which I was able to build by following the instructions on that page. It works like a champ, until there's a new kernel release, in which case it breaks until I rebuild that driver. It does however offer USB3 and 11ac, and has no trouble connecting and maintaining a high speed link (100+mbps) between where it lives in my RV parked in the driveway, and the AP in the back bedroom of my house. This is enough distance where the onboard Pi4 wifi could barely see my network and couldn't even sustain megabit speeds reliably.

I would recommend trying https://github.com/morrownr/8814au this driver, but honestly, the driver and that hardware are trash in terms of Linux support, and I’d highly recommend getting something from https://github.com/morrownr/USB-WiFi/blob/main/The_Short_List.md

It made no sense as to why it was scanning, it's my desktop adapter and only has to connect to a singular network. Anyway i figured it might've been due to roaming so i went and reinstalled the driver i use (i use an adapter with the rtl8814au chip and use this driver: https://github.com/morrownr/8814au), just to be sure i manually set the BSSID in the network settings.

Here's the driver.