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

Let hotspot and shared-ethernet clients get an address through Omarchy's default-deny ufw

omarchyarchendeavouroscachyosmanjaronetworkmanagerufwlaptop
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 holds. quattro install/config/firewall.sh sets ufw default deny incoming and enables ufw, /etc/default/ufw on this 4.0.4-1 machine has DEFAULT_FORWARD_POLICY="DROP", and nftables semantics make a drop in ufw's base chain terminal regardless of an accept in NetworkManager's own table. The cited BBS thread shows a CachyOS user fixing exactly this by disabling ufw. Open PR #7435 adds interface-scoped rules for DHCP udp/67, DNS on 53 and a route rule, but it scopes DNS and forwarding to the shared subnet with from <subnet>, which the record did not. The record's danger also overstated the exposure: NetworkManager's dnsmasq runs only while the shared connection is up, so on another network nothing answers on 53 or 67 unless some other service listens there. Fix rewritten to scope DNS and forwarding to 10.42.0.0/24 as the PR does, which narrows the danger to the DHCP rule. Not exercised: no ufw rule was added on this workstation.

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

The DHCP rule accepts udp/67 on that interface on every network it joins, not only while sharing. NetworkManager's dnsmasq runs only while the shared connection is up, so nothing answers on another network, but any service you later run on port 67 would be reachable there. The DNS and forwarding rules are limited to 10.42.0.0/24. Delete the rules when you stop sharing: sudo ufw status numbered, then sudo ufw delete <n>.

Symptom

The hotspot is up and phones see the SSID and accept the password, but they sit on "Obtaining IP address" forever and then drop. Or a laptop plugged into a shared ethernet port gets no lease. If a client is given a static address in 10.42.0.0/24, it can ping the host but reaches nothing beyond it.

Cause

NetworkManager's shared mode runs dnsmasq on the shared interface (10.42.0.1/24 by default) and adds its own NAT rules. Omarchy enables ufw with default deny incoming, and /etc/default/ufw keeps DEFAULT_FORWARD_POLICY="DROP". Client DHCP requests (udp/67) and DNS queries (53) to 10.42.0.1 hit the host's INPUT chain and are dropped. Forwarded client traffic hits ufw's FORWARD drop. An accept in NetworkManager's own nftables table does not override a drop in ufw's chains on the same hook, so the clients never get a lease. libvirt's virbr0 fails the same way on Omarchy. An open upstream PR (#7435) adds interface-scoped ufw rules for this reason.

Fix

Find the interface clients connect to (the hotspot's Wi-Fi interface, or the shared ethernet port) and your uplink interface:


nmcli device          # e.g. wlp2s0 = hotspot, enp3s0 = uplink

NetworkManager's shared mode uses 10.42.0.0/24 unless the profile sets another address. Check with:


nmcli -g ipv4.addresses connection show Hotspot    # empty means the 10.42.0.1/24 default

Open DHCP on the shared interface, and DNS and forwarding only for the shared subnet:


sudo ufw allow in on wlp2s0 to any port 67 proto udp comment 'hotspot dhcp'
sudo ufw allow in on wlp2s0 from 10.42.0.0/24 to any port 53 comment 'hotspot dns'
sudo ufw route allow in on wlp2s0 out on enp3s0 from 10.42.0.0/24 comment 'hotspot egress'
sudo ufw status verbose

The DHCP rule cannot be limited by source, because a client asking for a lease has no address yet.

Reconnect the client (forget and rejoin on the phone).

For a shared ethernet port the roles swap. The client side is the ethernet interface, and the uplink is usually the Wi-Fi interface.

Do not "fix" this with sudo ufw disable. That removes the firewall on every interface, including the uplink.

Plain Arch: this applies only if ufw (or another default-deny firewall) is enabled. Stock Arch has no firewall, so dnsmasq being missing is the more likely cause there.

Verify

The client gets a 10.42.0.x address and can browse. On the host, journalctl -u NetworkManager -b | grep -i dnsmasq shows DHCPACK lines for the client. sudo ufw status verbose lists the three rules.

Sources

nm-hotspot-clients-no-ip-ufw-blocks-dhcp