Get an IPv4 lease when the router ignores NetworkManager's DHCP client-id
Symptom
After upgrading to Omarchy Quattro the laptop associates to Wi-Fi and gets a global IPv6 address and IPv6 default route, but no IPv4 address and no IPv4 route at all. Other devices on the same network are fine, and the same laptop gets IPv4 from a phone hotspot. NetworkManager's log shows:
ipv4.dhcp-client-id: no explicit client-id configured
client-id: set effective 01:xx:xx:xx:xx:xx:xx
event: send DISCOVER to 255.255.255.255
event: send DISCOVER to 255.255.255.255
with no OFFER ever arriving.
Cause
When no client-id is configured, NetworkManager synthesises RFC 2132 option 61 from the interface MAC (01:<mac>). Some ISP-supplied routers refuse to answer a DISCOVER that carries that option, or key their lease table on a different identifier. Setting the client-id to none makes NetworkManager omit option 61 entirely, which those routers accept.
Fix
nmcli -g NAME,TYPE connection show # find the profile name
sudo nmcli connection modify "<connection-name>" ipv4.dhcp-client-id none
sudo nmcli connection up "<connection-name>"
To watch the exchange while testing:
journalctl -u NetworkManager -f | grep -i dhcp
# healthy: received OFFER of 192.168.0.192 from 192.168.0.1 / received ACK ... / state changed new lease
To apply it to every new profile, drop in a default:
sudo tee /etc/NetworkManager/conf.d/30-dhcp-client-id.conf >/dev/null <<'EOF'
[connection]
ipv4.dhcp-client-id=none
EOF
sudo systemctl reload NetworkManager
Verify
ip -4 addr show shows an address and ip -4 route shows a default route via the router. The setting persists across reconnects (nmcli -f ipv4.dhcp-client-id connection show "<name>").