OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network medium common DISPUTE

Start a NetworkManager hotspot or shared ethernet that fails because dnsmasq is missing

omarchyarchendeavouroscachyosmanjaronetworkmanagerlaptopintel
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Cause and fix hold. Confirmed: pacman -Si networkmanager lists dnsmasq: connection sharing as optional, install/omarchy-base.packages on quattro has no dnsmasq (this workstation has it only because it was installed explicitly), PR #7435 is open and adds a migration running omarchy-pkg-add dnsmasq, iw is present on Omarchy through wireless-regdb, and the Arch wiki Software_access_point page states the Intel LAR 5 GHz AP limitation. NetworkManager's nm-dnsmasq-manager.c confirms it launches its own dnsmasq with --conf-file=/dev/null, so the verify step is right. The symptom was wrong in two places. The journal string in current NetworkManager is could not start dnsmasq: Could not find "dnsmasq" binary (nm-device.c plus the helper string Could not find "%s" binary in /usr/bin/NetworkManager 1.58.1), the unquoted form is the old wording from the NixOS issue. Shared connection service failed to start is not raised by current nm-device.c for this path, which fails the IPv4 shared state and surfaces as IP configuration could not be reserved. The cited BBS thread 293307 shows that same nmcli error also comes from a running dnsmasq.service, so the symptom now tells the two apart by the journal line. Not exercised: no hotspot was started on this workstation.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Starting a hotspot on the Wi-Fi interface drops your current Wi-Fi connection. If that is your only uplink, you go offline until you run nmcli connection down Hotspot.

Symptom

Trying to share the laptop's connection fails straight away. nmcli device wifi hotspot ssid MyHotspot password 'longpassword' or a wired profile with ipv4.method shared never activates, and nmcli reports Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.). The NetworkManager journal (journalctl -u NetworkManager -b) shows could not start dnsmasq: Could not find "dnsmasq" binary. Older NetworkManager releases worded it failed to start dnsmasq: Could not find dnsmasq binary. The same nmcli error with no such journal line, on a machine where dnsmasq is installed, usually means dnsmasq.service is running and holding the ports NetworkManager's own instance needs. On an Intel card, a hotspot with band a may also refuse to start even after dnsmasq is installed.

Cause

Any NetworkManager connection with ipv4.method shared (a Wi-Fi hotspot or a shared wired port) runs its own private dnsmasq instance as the DHCP and DNS server for clients. dnsmasq is only an optional dependency of the networkmanager package ("dnsmasq: connection sharing"), and Omarchy 4's base package list does not include it, so a stock install has no binary to start. An open upstream PR (#7435) proposes a migration that installs dnsmasq for exactly this reason. A second, separate cause applies only to 5 GHz: most Intel cards since 2019 run Location-Aware Regulatory firmware that will not start an AP on 5 GHz, so a band a hotspot fails on Intel whatever the software does.

Fix

Install dnsmasq. Do not enable dnsmasq.service, because NetworkManager starts its own instance, and a system dnsmasq bound to port 53 conflicts with it:


sudo pacman -S --needed dnsmasq
systemctl is-enabled dnsmasq.service   # should print disabled

If pacman -S 404s on Omarchy, the sync database is stale. Run omarchy update first, not pacman -Sy.

Check that the card can be an access point, then start the hotspot on 2.4 GHz:


iw list | grep -A10 'Supported interface modes' | grep -w AP
nmcli device                      # find the Wi-Fi interface name, e.g. wlan0 or wlp2s0
nmcli device wifi hotspot ifname wlp2s0 con-name Hotspot ssid MyHotspot band bg password 'at-least-8-chars'

A single radio usually cannot hold a client connection and an AP at once, so the hotspot replaces your Wi-Fi uplink. Share a wired or USB-tethered uplink, not the Wi-Fi you are connected to.

On an Intel card, keep band bg. A band a AP is blocked by the card's LAR firmware, and there is no supported switch to turn that off.

If clients then join but sit at "Obtaining IP address", that is the firewall. See nm-hotspot-clients-no-ip-ufw-blocks-dhcp.

Verify

pacman -Q dnsmasq prints a version. nmcli connection up Hotspot succeeds. nmcli -f GENERAL.STATE device show <iface> reads 100 (connected). pgrep -a dnsmasq shows a dnsmasq started by NetworkManager with --conf-file=/dev/null.

Sources

nm-hotspot-fails-dnsmasq-not-installed