### System details

Framework Laptop 13 (AMD Ryzen AI 300 Series), Mediatek MT7925 Wi-Fi 7, Omarchy version 3.1.4

### What's wrong?

> Note: Investigation & drafting of this issue was aided by AI but the solution works now.

WiFi fails to establish network connectivity on normal boots, with the interface
stuck in dormant state. The issue does not occur when booting from Limine
snapshots, only on regular boots.

## Symptoms

- WiFi shows as "connected" in impala
- Interface state is dormant instead of routable
- No actual network traffic possible (cannot send queries)
- networkctl status wlan0 shows State: dormant
- Booting from a Limine snapshot works perfectly with identical network
configuration

## (Possible) Root Cause

I'm pretty sure this is a race condition introduced by commit 1c5a17f ("Disable systemd-networkd-wait-online #645"), which masked systemd-networkd-wait-online.service to prevent boot timeouts.

The issue occurs because:

1. UFW starts very early in boot (Before=sysinit.target,
After=systemd-sysctl.service)
2. Network services start later (iwd and systemd-networkd both start
After=network-pre.target)
3. With systemd-networkd-wait-online masked, network-online.target no longer
actually waits for any network interface
4. UFW applies firewall rules before the WiFi interface completes DHCP negotiation
5. This leaves the interface in dormant state without an IP address

Evidence from dmesg

```dmesg
[   27.266512] wlan0: send auth to 26:2e:dd:d8:33:71 (try 1/3)
[   27.271962] wlan0: authenticated
[   27.276383] wlan0: associate with 26:2e:dd:d8:33:71 (try 1/3)
[   27.291917] wlan0: RX AssocResp from 26:2e:dd:d8:33:71 (capab=0x11 status=0
aid=1)
[   27.328204] wlan0: associated
[   27.331366] wlan0: Limiting TX power to 0 (-128 - 0) dBm as advertised by 26:2e:dd:d8:33:71
[   27.829575] [UFW BLOCK] IN=br-009d91a19628 OUT= MAC= SRC=172.19.0.1 DST=224.0.0.252 LEN=60 TOS=0x00 PREC=0x00 TTL=255 ID=7039 PROTO=UDP SPT=5355 DPT=5355 LEN=40 
```
Authentication and association succeed, but DHCP never completes, leaving the
interface dormant.

## My current workaround

Create a systemd override for UFW to ensure it waits for the network:

```bash
sudo mkdir -p /etc/systemd/system/ufw.service.d
sudo tee /etc/systemd/system/ufw.service.d/override.conf << 'EOF'
[Unit]
After=network-online.target
Wants=network-online.target
EOF
sudo systemctl daemon-reload
```
## Possibly after 3.1.4??
This started to happen yesterday morning. I noticed that when I booted from a Limine snapshot things were working, possibly because of different boot timings or how snapshots are restored compared to normal boot

I am very confident it is a race conditions as if I did subsequent restarts, sometimes wifi would be stable