morrownr/USB-WiFi: a Linux reference for choosing a USB WiFi adapter
USB WiFi Adapter Information for Linux
At a glance
- What is it?
- USB-WiFi is not software you install. It is a documentation repository that tells Linux users which USB WiFi adapters work with in-kernel drivers, which chipsets sit inside them, and how to set up AP and monitor mode. It is useful precisely because it refuses to be a driver project.
- Who is it for?
- Adopt USB-WiFi as a reading step before you buy hardware, not as a package to install. It suits Linux users who want an adapter that works with in-kernel drivers, and anyone building an access point or using monitor mode on Kali.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 74 days ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- morrownr/USB-WiFi4,512 ★ · +51
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| morrownr/USB-WiFi | 4.5k | 4.5k |
51 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What USB-WiFi actually is, and who it is written for
The repository has three top-level entries: .github/, README.md and home/. That layout tells you most of what you need to know. There is no build system, no Makefile, no kernel module and no package manifest. USB-WiFi is a curated documentation set for Linux users who need to buy or troubleshoot a USB WiFi adapter, and the README states the mission directly: reviews of USB WiFi adapters, links to adapters known to perform well with Linux, technical support and educational information.
The audience is narrower than the topic suggests. The README says the site is maintained by Linux users for Linux users, and adds that Windows users are welcome but that support for USB WiFi adapter use on Windows will not be added. That is a deliberate boundary. If you are looking for a Windows driver bundle, this repository will send you to hardware that also happens to work in Windows, nothing more.
The practical value is in menu item 2, the Plug and Play List, described as USB WiFi adapters that are supported with Linux in-kernel drivers. In-kernel is the operative phrase. An adapter on that list works with the driver already shipped in your kernel, which means no DKMS rebuild after every kernel upgrade. That single property is why people read this repository instead of a shopping site.
How the documentation is organised, and why the structure matters
The README is a numbered menu, and the ordering is a recommendation, not a table of contents. Item 1, USB WiFi adapter information for Linux, is described as the place to start. Item 3 covers chipset information, item 4 covers Realtek out-of-kernel drivers, item 5 is a speed comparison test, and item 7 explains firmware installation for Mediatek and RTW88 based adapters.
The README also warns that the home directory contains out-of-date documents and testing documents, and recommends limiting your use to the linked documents. That is an unusual admission for a documentation repository and it is worth taking literally. Deep-linking into home/ from a search engine can land you on a page the maintainers no longer stand behind.
Support runs through GitHub Issues, which the README names as the place to post problems, ask questions and read news. There is no chat channel, no forum and no mailing list mentioned. For a site that, according to the README, averages 47,230 views per month across github.com/morrownr as of 09-01-2026, that is a thin support surface. Questions get answered in public and stay searchable, which helps the next reader, but it also means response time depends on volunteers.
The last push to the repository was on 2026-09-02, so the menu is being edited, but nothing in the README promises a release cadence. The repository has no published GitHub releases at all.
Installing nothing: how to use the Plug and Play List before you buy
There is no install step for USB-WiFi, because there is nothing to install. The README points you at documents. The first real use is a purchase decision, and the workflow is: read the adapter information document, then open the Plug and Play List, then check the chipset document for the chip inside the adapter you are considering.
If you want the documents locally rather than reading them on GitHub, clone the repository:
git clone https://github.com/morrownr/USB-WiFi.git
cd USB-WiFi/homeAfter cloning you are in the home directory described above. The README cautions against browsing it freely, so open the files the menu links to rather than listing the directory.
Once you have an adapter in hand, the first diagnostic step is confirming which driver claimed it. The repository's chipset document is the reference for mapping a chip to a driver name; compare the chip in your adapter against that document. If no wireless interface appears, the chipset document and the firmware document are the two places to look next. For Mediatek and RTW88 based adapters, menu item 7 covers installing or updating firmware.
AP mode and monitor mode: the two guides that carry real configuration
Most of the repository is prose and links, but the AP Mode folder contains actual configuration files. The README links example hostapd.conf files for three generations of hardware: WiFi 4 for mt76 and rtw88 chipset based adapters, WiFi 6 for mt7921 and mt7922, and WiFi 7 for mt7925. There is also a document on updating hostapd to the latest git.
That split by generation is the useful detail. A hostapd configuration that works for a WiFi 4 adapter is not the configuration you want for an mt7925, and the repository does not pretend one file covers everything. The bridged wireless access point document is the walkthrough that ties the adapter, the hostapd configuration and the bridge together.
Monitor mode is handled differently: the README links out to a separate repository, morrownr/Monitor_Mode. That is a clean separation. The adapter list tells you what hardware to buy; the monitor mode repository tells you how to put it into monitor mode. There is also a document on using a USB adapter in VirtualBox, which matters because passing a USB WiFi adapter through to a guest is a common source of confusion.
One thing the README does not document is rollback. If an AP mode configuration change breaks your setup, there is no stated procedure for returning to a working state, and no versioning of the example configuration files beyond the git history of the repository itself.
The out-of-kernel page is a signpost, not a driver
Menu item 4 covers USB WiFi adapters and Realtek out-of-kernel drivers. The name is precise, and so is the limitation. Out-of-kernel drivers live outside the kernel tree. They must be rebuilt against each new kernel, usually through DKMS, and a kernel upgrade that the driver has not caught up with leaves you without wireless until you fix it.
The repository documents this situation rather than solving it. If you are choosing hardware today, the Plug and Play List exists so you can avoid that maintenance burden entirely. The out-of-kernel page is for people who already own an adapter whose chip has no in-kernel driver, or who need a feature the in-kernel driver does not provide.
This is the clearest trade-off in the whole repository. In-kernel support means boring upgrades. Out-of-kernel support means access to hardware that is otherwise unusable on Linux, at the cost of a rebuild cycle you now own. The README does not claim otherwise, and anyone reading the menu in order will reach the Plug and Play List before the out-of-kernel page, which is the right order.
Where USB-WiFi is the wrong tool
If you want a driver, this repository will disappoint you. It contains no code. The in-kernel drivers it recommends are maintained in the Linux kernel, and the out-of-kernel drivers it discusses are maintained elsewhere.
It is also the wrong tool for non-Linux systems. The README is explicit that Windows support will not be added. The adapter list is still useful to a Windows user shopping for hardware, and the README says so, but nothing beyond the hardware links applies.
A third case is hardware that is simply too new. The WiFi 7 hostapd example targets the mt7925 chipset, and in-kernel support for a chip depends on your kernel version, not on the repository. The README does not publish a kernel version matrix, so you have to check your own kernel against the chipset document. If your distribution ships an older kernel than the chipset needs, the Plug and Play List is not a guarantee for your machine.
Finally, the repository is not a benchmark service. It links a speed comparison test, but the README does not describe the methodology in the menu itself, so treat the numbers as one data point rather than a ranking of every adapter on the list.
Compared with reading the kernel wireless documentation directly
The obvious alternative is the official Linux Wireless documentation, which the README links as menu item 6, alongside the wireless-next repository. That is the primary source: it describes the mac80211 stack, the drivers, and the subsystem as the kernel developers see it.
The difference in approach is audience and shape. The kernel documentation explains how wireless works in Linux and what each driver supports. USB-WiFi answers a narrower question: which specific USB adapter, on sale now, will work when I plug it into a Linux machine. It does that by naming adapters and chipsets rather than describing subsystems, and by linking example hostapd configurations for specific chips instead of explaining hostapd in general.
Neither replaces the other. You use the kernel documentation to understand why a driver behaves as it does, and USB-WiFi to decide what to buy. If you only read one and you are shopping for hardware, USB-WiFi is the faster path. If you are debugging a driver, the kernel documentation and the wireless-next log are where the answers live.
Licence, maintenance and what upgrading costs you
The repository does not state a licence. No licence identifier appears in the README or in the top-level entries, and the README does not discuss terms of use, redistribution or attribution for the documents and example configuration files. That is a gap worth knowing about before you copy the hostapd examples into a product or a published guide. It is not a legal problem for a reader who follows the links, but it is an unresolved question for anyone repurposing the content, and the right move is to ask in Issues rather than assume.
Maintenance is documentation maintenance. The last push was on 2026-09-02, and there are no releases, so there is no version number to pin and no changelog to read. Upgrading means pulling the repository again and re-reading the documents that changed. If you cloned it, git pull in the repository directory is the whole upgrade procedure; if you only read it on GitHub, there is nothing to do.
The cost that actually matters is hardware. Because the repository steers you toward in-kernel drivers, the ongoing cost after purchase is close to zero: kernel upgrades do not require rebuilding anything. Choosing an adapter from the out-of-kernel page instead moves that cost onto you, in the form of rebuilds tied to kernel releases. That is the real upgrade decision this repository helps you make.
Editorial conclusion
Adopt USB-WiFi as a reading step before you buy hardware, not as a package to install. It suits Linux users who want an adapter that works with in-kernel drivers, and anyone building an access point or using monitor mode on Kali. It is the wrong tool if you need Windows drivers or a supported out-of-kernel build, since the repository is documentation only and its out-of-kernel page is a pointer, not a maintained driver tree. Verify three things first: that your chosen adapter appears in the Plug and Play List, that your kernel version is new enough for the chipset, and that the firmware file named in the Mediatek and RTW88 firmware document is present on your system.
Frequently asked questions
What is morrownr/USB-WiFi and what does it do?
It is a documentation repository about USB WiFi adapters for Linux, with reviews, a list of adapters supported by in-kernel drivers, chipset information, firmware instructions and AP mode configuration examples. It contains no driver code.
How do I install morrownr/USB-WiFi?
There is nothing to install. The README presents a menu of documents, and if you want them locally you clone the repository and read the linked files in the home directory.
How do I use a USB WiFi adapter with morrownr/USB-WiFi on Linux?
Start with the adapter information document, check the Plug and Play List for adapters supported by in-kernel drivers, and use the chipset document to identify the chip. The AP Mode folder holds hostapd examples for WiFi 4, WiFi 6 and WiFi 7 chipsets.
Can I use a USB WiFi adapter in VirtualBox with Kali Linux using this repository?
The README links a document titled Using a USB Adapter in VirtualBox, and separately links Recommended Adapters for Kali Linux. Both are documents in the repository rather than tools.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/morrownr-usb-wifi)Star history chart for your README
[](https://hysenlabs.com/projects/morrownr-usb-wifi)Was this useful?