OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
apps-services medium common DISPUTE

Give Waydroid an IP address when ufw blocks DHCP on waydroid0

omarchyarchwaydroidandroidufwdesktoplaptop
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

The four ufw rules match the Arch wiki Waydroid page (raw) word for word. /etc/default/ufw here has DEFAULT_INPUT_POLICY="DROP" and DEFAULT_FORWARD_POLICY="DROP", quattro install/config/firewall.sh sets default deny incoming, and waydroid 1.6.3-1 depends on dnsmasq and nftables. docs.waydro.id networking page (markdown) does give ufw allow 53, ufw allow 67, ufw default allow FORWARD. One claim was false: that default allow FORWARD undoes ufw-docker's protection. /etc/ufw/after.rules here shows ufw-docker's DOCKER-USER chain ending in its own ufw-docker-logging-deny rules for NEW connections to private ranges, which do not depend on ufw's routed policy. The real cost is that every forwarded path (libvirt bridges, other container networks) is accepted, not only waydroid0. Rewrote that paragraph. The #12454 report is a side note in an AI-filed comment on a 7.2.5-4 build, so the cause now says so. ufw's parser accepts forward as a synonym of routed. No rule was added.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.

Symptom

Waydroid's container runs and Android boots, but there is no network. waydroid status shows IP address: UNKNOWN. Inside Android the Wi-Fi tile says connected without internet, the browser cannot load anything and the Play Store says "No connection".

Cause

Waydroid creates a waydroid0 bridge and runs dnsmasq on the host to hand Android its address (the waydroid package depends on dnsmasq and nftables). Android's DHCP request (UDP 67) and DNS queries (port 53) are traffic into the host, and Omarchy runs ufw with default deny incoming and DEFAULT_FORWARD_POLICY="DROP" in /etc/default/ufw. ufw drops DHCP and DNS in INPUT and Android's outbound traffic in FORWARD. A comment on omacom/omarchy#12454 (on a linux-omarchy 7.2.5-4 build) notes this exact IP address: UNKNOWN result with ufw active. Any Arch install with ufw enabled behaves the same.

Fix

Allow DHCP and DNS from the Waydroid bridge only, and route its traffic. These are the Arch wiki's rules:


sudo ufw allow in on waydroid0 to any port 67 proto udp comment 'waydroid dhcp'
sudo ufw allow in on waydroid0 to any port 53 comment 'waydroid dns'
sudo ufw route allow in on waydroid0
sudo ufw route allow out on waydroid0

The Waydroid project's own page suggests sudo ufw allow 53, sudo ufw allow 67 and sudo ufw default allow FORWARD. Do not use those on Omarchy. The first two open DNS and DHCP on every interface, including Wi-Fi. The third makes ufw accept forwarded traffic between every pair of interfaces, so libvirt bridges and other container networks are opened too, not only Waydroid's.

Check IPv4 forwarding, then restart Waydroid so Android asks again:


sysctl net.ipv4.ip_forward          # must print 1
waydroid session stop
sudo systemctl restart waydroid-container.service
waydroid session start

If forwarding prints 0, uncomment net/ipv4/ip_forward=1 in /etc/ufw/sysctl.conf and run sudo ufw reload.

Verify

waydroid status shows an address on the waydroid0 subnet instead of UNKNOWN, and a page loads in Android's browser. sudo ufw status | grep waydroid0 lists the four rules.

Sources

waydroid-no-ip-address-ufw-waydroid0