CLI tool
lakinduakash/linux-wifi-hotspot avatar
lakinduakash/linux-wifi-hotspot

linux-wifi-hotspot: sharing one adapter as an access point on Linux

Feature-rich wifi hotspot creator for Linux which provides both GUI and command-line interface. It is also able to create a hotspot using the same wifi card which is connected to an AP already ( Similar to Windows 10).

4,453 stars394 forksShellBSD-2-Clause

At a glance

What is it?
The project wraps hostapd and create_ap behind a GTK app and a command line script, and it targets the adapter restrictions that break 5GHz hotspots. It suits a Linux user who needs to reuse a single WiFi card as an AP, and it does not suit anyone whose adapter firmware blocks AP mode outright.
Who is it for?
Adopt it if you need an access point from the same card that holds your uplink and you want a GUI over hostapd rather than your own config. Do not adopt it on Broadcom hardware in T2 Macs, where clients associate and drop regardless of any create_ap option, and do not expect the 5GHz path to work on Intel cards without first reading the lar_disable guide.
Can I use it commercially?
Yes. BSD-2-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 13 days ago.
What is it written in?
Mainly Shell, 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

  • lakinduakash/linux-wifi-hotspot4,453 ★ · +59
Star history
Repository2026-09-232026-11-15
lakinduakash/linux-wifi-hotspot4.4k4.5k

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

Editorial analysis

One adapter doing uplink and access point at once

The interesting claim here is not that Linux can host a WiFi network, since hostapd has done that for years. It is that the same radio can stay associated with an existing network while beaconing its own, the trick Windows 10 popularised. The project names that capability first in its feature list and then backs it with a band selection that can hand a 2.4GHz client to a laptop sitting on 5GHz.

Everything the project builds sits on top of two programs. hostapd is the access point daemon. create_ap is the wrapper that configures hostapd, sets up dnsmasq for DHCP and NAT, and prints a log. The top level Makefile does almost nothing itself; the all target creates a build directory, prints a reminder to run sudo make install, then delegates into src. install-cli-only goes further down and delegates into src/scripts, which is how you get the command line side without the GUI.

The primary language of the repository is Shell. The GUI is GTK3, and the QR code generation comes from libqrencode and libpng. Read that dependency set before you install anything, because it decides whether a source build is cheap or a half day of distro package hunting.

Installing from source, COPR, and two paths the README now calls deprecated

The source path is the one the project still steers toward. Clone, build, install:

bash
git clone https://github.com/lakinduakash/linux-wifi-hotspot
cd linux-wifi-hotspot
make
sudo make install

The build needs a toolchain that the README lists explicitly, and on Ubuntu or Debian that is one command:

bash
sudo apt install -y libgtk-3-dev build-essential gcc g++ pkg-config make hostapd libqrencode-dev libpng-dev

If you never want the GUI, the project tells you to run make install-cli-only as root instead, which skips the src GUI build entirely.

Now the catch. In the README's Installation section, the Debian/Ubuntu and Arch sections each carry the parenthetical "deprecated - build yourself". Yet a Fedora COPR repository is still offered as a live path:

bash
sudo dnf copr enable zinix01/linux-wifi-hotspot
sudo dnf install linux-wifi-hotspot

So on Ubuntu you get a PPA and on Arch an AUR package, both under a deprecation notice, and on Fedora a COPR. Read the parentheticals as guidance about the maintainer's confidence in those packages, not as evidence they were removed.

Starting it: pick the interface, then pick the band the adapter will accept

Once installed, the GUI appears under the name Wifi Hotspot in the application menu, or you launch it from a terminal:

bash
wihotspot

The first useful thing the newest release does is preselect the WiFi and Internet interfaces, so creating a hotspot works without hunting through dropdowns. Beyond that the GUI exposes the options that matter to a decision: channel, gateway IP, hidden SSID, MAC filter, a QR code for the password, a list of connected clients, and toggles for the ac and ax wireless modes.

The band selector deserves a warning. Band selection in the GUI once fell back to 2.4GHz with nothing telling you, and the maintainer treats that as fixed. If you have deliberately picked a band and want a hotspot, read the band field before you read anything else on screen.

Why a 5GHz hotspot refuses to start on iwlifi

This is the failure the project spent its recent work on. On Intel adapters the 5GHz hotspot often simply does not start, and the explanation given is that the adapter firmware keeps every 5GHz channel flagged no IR, which forbids beaconing. That is a firmware policy, not a missing package. The project ships a guide at docs/howto/intel-5ghz-lar.md with helper scripts that restore the iwlwifi lar_disable parameter the kernel removed, and a quick workaround if you would rather not run those scripts: unselect Auto and choose 2.4Ghz.

A second, quieter restriction sits behind it. Many adapters can only host an access point on the channel the client is already using, which is where the error Failed to set beacon parameters came from. The hotspot now follows your current connection instead of failing, which means the band you get is a consequence of the network you joined rather than a free choice. Connect to a 2.4GHz network and you get a 2.4GHz hotspot.

There is also a band-width detail that bites: reaching 80MHz under --ieee80211ac needed a new --vht-chwidth option, so an option that existed without working is exactly the failure mode to check for in older scripts you may have copied.

The case no setting can fix: firmware that refuses AP mode with encryption

Some clients see the hotspot, associate, and immediately disconnect. The cause is adapter firmware that does not support AP mode with encryption, create_ap now detects it and warns, and the README is blunt that no create_ap option works around it. Broadcom adapters in T2 Macs are named as known to be affected, with a USB WiFi adapter as the stated fix.

That is the hard boundary of this project. Everything else the maintainer fixed is scriptable: interface preselection, band fallback, following the client's channel, error visibility, virtual interface acceptance on PCIe and USB brcmfmac cards. Firmware capability is outside that reach. If you are shopping for hardware to run this on, ask whether the chipset supports AP mode with WPA before you install anything.

How the VPN hotspot path differs from a plain NAT share

The VPN section anchors a capability that changes the data path rather than the radio settings. With a VPN hotspot the traffic of connected clients is tunnelled through the VPN on the host, which the project describes as useful for devices with no VPN app of their own, such as TVs and consoles. That is a different failure mode from NAT: a client that cannot join your VPN can still join your access point and come out the other side of the tunnel.

The alternative to weigh here is not another hotspot GUI so much as skipping the project. hostapd plus your own dnsmasq and iptables rules does the same work, and it gives you direct control over every hostapd option instead of a GUI that exposes a subset. The trade runs the other way too: doing it by hand means you own the failure modes, and the concrete ones above, the no IR flags and the encryption refusal, do not disappear when you write the config yourself.

What the daemon dependency list commits you to

Beyond the build toolchain the runtime dependencies are a real commitment: bash, util-linux for getopt, procps or procps-ng, hostapd, iproute2, iw, and optional haveged. NATed and None sharing methods also need dnsmasq and iptables. iwconfig is listed only for adapters iw cannot recognise. You are installing a daemon that rewrites interface configuration, so this is not a single-user script with a narrow blast radius.

Continuity risk sits in one place, and it is named: the README carries an explicit note from the maintainer looking for contributors and for trusted collaborators with commit access.

Before you upgrade an existing install, re-read the 5GHz section, because the behaviour around lar_disable and channel following changed in the work listed under What's new.

Editorial conclusion

Adopt it if you need an access point from the same card that holds your uplink and you want a GUI over hostapd rather than your own config. Do not adopt it on Broadcom hardware in T2 Macs, where clients associate and drop regardless of any create_ap option, and do not expect the 5GHz path to work on Intel cards without first reading the lar_disable guide. Verify, before installing anything, whether your chipset can host an AP with encryption and whether the band you want is unflagged: if firmware says no, no setting in this project recovers it.

Frequently asked questions

how to install linux wifi hotspot

The project points to a source build: clone the repository, run make, then sudo make install. On Ubuntu or Debian the build dependencies install with sudo apt install -y libgtk-3-dev build-essential gcc g++ pkg-config make hostapd libqrencode-dev libpng-dev, and on Fedora a COPR repository provides the package.

how to use linux wifi hotspot

Launch the GUI by searching for Wifi Hotspot in the application menu or by running wihotspot in a terminal, check the preselected WiFi and Internet interfaces and pick the frequency band. Full command line help is in src/scripts/README.md, and command line only users run make install-cli-only as root.

linux wifi hotspot alternative

The practical alternative is hostapd configured directly, with dnsmasq and iptables handling DHCP and NAT yourself. That gives access to every hostapd option instead of the subset the GUI exposes, but you take on the adapter failures, such as 5GHz channels flagged no IR on Intel cards.

Can I create a hotspot using Wi-Fi on linux-wifi-hotspot?

Yes, and that is the project's main capability: it shares a connection from one WiFi card while the card stays connected to an existing network, and it can serve 2.4GHz and 5GHz clients from different bands than the uplink. Some adapters only host an access point on the channel their client is already using, so the hotspot follows your current connection.

Official sources

  1. Issues
  2. lakinduakash/linux-wifi-hotspot on GitHub
  3. License: BSD-2-Clause
  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/lakinduakash-linux-wifi-hotspot.svg)](https://hysenlabs.com/projects/lakinduakash-linux-wifi-hotspot)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/lakinduakash-linux-wifi-hotspot.svg)](https://hysenlabs.com/projects/lakinduakash-linux-wifi-hotspot)

Was this useful?