Open-source project
open-sdr/openwifi avatar
open-sdr/openwifi

openwifi: an AGPL 802.11n baseband, a subscription for 802.11ax, and an SD image on a personal web page

open-source IEEE 802.11 WiFi baseband FPGA (chip) design: driver, software

4,872 stars829 forksCAGPL-3.0

At a glance

What is it?
openwifi is a full-stack IEEE 802.11 design on software defined radio, with the Linux driver and software in this repository and the FPGA design in a companion one. Its own README puts spectrum regulation in the reader's hands, gates the newest Wi-Fi generation behind a paid subscription, and links its prebuilt image from a personal university page.
Who is it for?
openwifi fits a research group that wants a full Wi-Fi stack in FPGA rather than a Wi-Fi chipset, and that can supply the hardware, since the whole design assumes an SDR board and, on three of the thirteen supported boards, a licensed Vivado installation. Three things to weigh first.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 24 days ago.
What is it written in?
Mainly C, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • open-sdr/openwifi4,872 ★ · +63
Star history
Repository2026-09-232026-11-15
open-sdr/openwifi4.8k4.9k

63 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The open source part stops at 802.11n and the subscription covers 802.11ax

The first line of the README states the foundation, open source, and then immediately a business line: to access advanced features (Wi-Fi6, OFDMA, RFSoC, JCAS/ISAC, different bandwidth, etc.), consider a subscription. The feature list closes the same way, with 802.11ax and more advanced features pointed at a separate site. So the division is legible. What the AGPL code covers is 802.11a, g and n, at 20MHz bandwidth, across a frequency range from 70MHz to 6GHz, in ad-hoc, station, access point and monitor modes, with the DCF low MAC layer implemented in the FPGA and a 10 microsecond SIFS claimed as achieved. What the subscription covers is the current Wi-Fi generation and the advanced features the README names: Wi-Fi6, OFDMA, RFSoC, JCAS/ISAC and different bandwidth. The licence section makes the same split explicit, describing a dual licence setup where AGPLv3 is the open source licence and a commercial licence covering non-open-source use and advanced features is arranged through a contact form. If your requirement is 802.11ax, this repository is the wrong place to look for it, and that is a licensing fact rather than a technical gap.

The prebuilt SD image is hosted on a personal university page

The quick start is the ordinary one for an FPGA Wi-Fi project: download an image, unzip it, and write it to an SD card of at least 16GB. The interesting part is where the file lives. The link is a `.img.xz` sitting under a personal page at the university that hosts the maintainers, under the first author's username, and the filename carries the version and a codename: `openwifi-1.5.0-shahecheng.img.xz`. The codenames are worth noting because they run through the release titles too. The three most recent releases are named for shahecheng at 1.5.0, notter at 1.4.0 and wilsele at 1.3.1, and the known-issues document linked at the top of the README is named after one of them, `doc/known_issue/notter.md`. So this is a project that names its milestones, and the dates on those tags are uneven, from 2025-08-06 for 1.5.0 back to 2022-05-16 for 1.3.1. For anything beyond a first evaluation, build the image yourself from the from-scratch and Buildroot instructions for anything beyond a first evaluation.

Spectrum regulation is the reader's problem, and a cable is the answer

One sentence in the README carries more weight than the rest of the feature list, and it is written as a warning: it is your responsibility to follow your local spectrum regulation, or to use a cable, to avoid potential interference over the air. That is the honest framing for a project that transmits on unlicensed spectrum, and it applies to more than the transmitting functions. A baseband design with packet injection and fuzzing documented in its own application notes, with CSI fuzzer tooling to create an artificial channel response in the transmitter, and with CSI radar for joint radar and communication, is a research platform that transmits. Every one of them is a decision you make before you flash: which channels you are permitted to use in the country you are in, what power limits apply, whether your testing stays on cable, and whether the test network you transmit on is one you own. Treat that sentence as part of the installation instructions rather than as boilerplate, because the project put it there instead of in a separate safety section.

Twelve boards are supported and three of them need a licensed Vivado

The supported hardware table has three columns, board name, description and whether a Vivado licence is required, and the split is the useful part. The Xilinx ZC706 with an FMCOMMS2, 3 or 4 needs a licence, as do the ZCU102 with the same carrier and the ADRV9361-Z7035 with its daughter card. Everything else does not: the ZED board, the ZC702, the ADRV9364-Z7020, the three MicroPhase variants built on an enhanced ADALM-PLUTO including a smaller and cheaper one, the Raspberry Pi sized sdrpi from HexSDR, two low cost Zynq 7020 plus AD9361 boards that the table marks as unofficial, one of which is LibreSDR, and the PlutoSky R2, another low cost Zynq 7020 plus AD9361 board. Two more facts about the naming. The board name is the identifier used to pick the FPGA design in the hardware repository's board directory and the image in its image repository, so it is a string you will type. And if your board is not in the list there is a porting guide, plus a test bed tutorial for anyone without a board at all or who prefers JTAG boot over an SD card.

CSI is the centre of gravity: equalised channel estimates, in the computer

Looking at the feature list tells you what this design is for. CSI, channel state information, is described with its companions, frequency offset and an equalizer, delivered to the computer, and the same list has a CSI fuzzer that creates an artificial channel response in the Wi-Fi transmitter and a CSI radar application for moving detection, framed as joint radar and communication. Around that sit the capture features: IQ capture with real-time AGC, RSSI and IQ samples to the computer, plus a dual antenna version, and a time slicing feature that schedules FPGA queues by MAC address. The channel access parameters are configurable in detail, from the CCA threshold and receiver sensitivity through RTS and CTS duration, CTS-to-self, and the SIFS, DIFS, slot time and contention window values, which is the kind of knob that only matters if you are experimenting with medium access itself. Changing bandwidth and frequency is a supported exercise rather than a redesign, from 2MHz for 802.11ah in sub-GHz to 10MHz for 802.11p vehicle use at 5.9GHz.

Buildroot builds the root filesystem, and four assistant files sit at the root

The repository's layout tells you how the system is put together. `driver/` is the Linux driver, `host-tools/` holds the host-side utilities, and `user_space/` is where userspace lives. `kernel_boot/` is the boot side, and the root filesystem is Buildroot: `buildroot/`, `buildroot-external/` and `buildroot-build.sh` are all at the root, which matches the README's separate sections for building a Linux image from scratch and for building small Buildroot SD images. There is also `doc/` for the project document, application notes and videos, and `.gitmodules`, so parts of the build arrive as submodules. The root also carries `adi-linux` and `adi-linux-64`, which are the vendor kernel trees named after the radio hardware. Four files there are not part of the design at all: `AGENTS.md`, `CLAUDE.md`, `GEMINI.md` and `QWEN.md`, one instruction file per assistant tool. And licence hygiene is visible too, with a `LICENSES/` directory at the root and a `.license` sidecar beside the architecture diagram.

AGPL-3.0 in the metadata, AGPL-3.0-or-later in the file header

The licence facts need care, and the first thing to notice is that they are not the same. The repository metadata reports AGPL-3.0, while the header comment at the top of the README carries `SPDX-FileCopyrightText: 2019 UGent` and `SPDX-License-Identifier: AGPL-3.0-or-later`. Version 3 only and version 3 or later differ in a way that matters when you combine code, and the per-file detail is in the `LICENSES/` directory rather than in the README text. The README is also explicit that the project leverages third-party modules and that it is the user's duty to check and follow those licences according to the purpose, pointing at an Analog Devices repository as an example of how a compound licence is explained. The attribution line names the authors, Xianjun jiao, Michael Mehari and Wei Liu, with the copyright year and holder as 2019 and UGent. Two release facts to close on: the newest tag is v1.5.0 from 2025-08-06, before it v1.4.0 from 2023-01-28 and v1.3.1 from 2022-05-16, and the branch's last push was on 2026-10-22, so the code is moving ahead of the last named release.

Editorial conclusion

openwifi fits a research group that wants a full Wi-Fi stack in FPGA rather than a Wi-Fi chipset, and that can supply the hardware, since the whole design assumes an SDR board and, on three of the thirteen supported boards, a licensed Vivado installation. Three things to weigh first. Spectrum compliance is yours, and the README says so in capitals: follow local regulation or use a cable. The open licence covers 802.11a, g and n, while 802.11ax and what the project calls advanced features are pointed at a subscription, so a product plan that assumes Wi-Fi 6 is a commercial conversation. And the prebuilt SD card image is not a release artefact, it is a file on a personal page at the university hosting the maintainers, so treat it as a convenience for evaluation and build your own image from the Buildroot instructions for anything else. AGPL, with per-file licence terms in `LICENSES/`.

Frequently asked questions

What is openwifi?

openwifi is an open source, Linux mac80211 compatible, full-stack IEEE 802.11 and Wi-Fi design based on software defined radio. This repository contains the Linux driver and software, while the FPGA design lives in the companion openwifi-hw repository.

Which Wi-Fi standards does openwifi support?

The feature list covers 802.11a, g and n at 20MHz bandwidth and a frequency range from 70MHz to 6GHz, in ad-hoc, station, access point and monitor modes. 802.11ax and further advanced features are listed separately and pointed at a subscription rather than the open source repository.

Which SDR boards does openwifi support?

Thirteen are listed with a Vivado licence requirement. The Xilinx ZC706, the ZCU102 and the ADRV9361-Z7035 need a licensed installation, while the ZED, ZC702, ADRV9364-Z7020, the three MicroPhase ADALM-PLUTO variants, the sdrpi, two unofficial Zynq 7020 boards and the PlutoSky R2 do not. A porting guide covers boards that are not listed.

What licence does openwifi use?

The repository metadata reports AGPL-3.0 while the source header carries the SPDX identifier AGPL-3.0-or-later. The README describes a dual licence arrangement in which AGPLv3 is the open source licence and a commercial licence for non-open-source use and advanced features is arranged through a contact form, and it asks users to check the licences of the third-party modules it leverages, with `LICENSES/` in the repository.

What performance does the README report for openwifi?

In the best case with aggregation enabled, iperf TCP of 40 to 50Mbps and UDP of 50Mbps, EVM at -38dB, MCS0 sensitivity at -92dBm and MCS7 at -73dBm. Those figures are given for an FMCOMMS2 at 2.4GHz with cable and over-the-air testing.

Official sources

  1. Issues
  2. License: AGPL-3.0
  3. open-sdr/openwifi on GitHub
  4. README
  5. Releases
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/open-sdr-openwifi.svg)](https://hysenlabs.com/projects/open-sdr-openwifi)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/open-sdr-openwifi.svg)](https://hysenlabs.com/projects/open-sdr-openwifi)

Was this useful?