DHCPv4 received no offer until ipv4.dhcp-client-id was set to none

[pjgeutjens]

System details

• Omarchy upgrade: 3.8.5 at commit f4378f0d to 4.0.0-1
• NetworkManager: 1.58.0-1
• Kernel: 7.1.8-arch1-3
• Laptop: HP with Intel Wireless 8265 / 8275 using iwlwifi
• Router: ISP-provided Telenet modem/router, model unknown
• Both the 2.4 GHz and 5 GHz Wi-Fi connections showed the same problem

What happened

After upgrading to Quattro, the laptop connected to Wi-Fi and received a global IPv6 address and an IPv6 default route. It received no IPv4 address or IPv4 route.

The same laptop receives IPv4 from an iPhone hotspot. Other devices on the home network also receive IPv4. Changing Omarchy's DNS provider did not fix the missing lease.

The connection profile used automatic IPv4 configuration:

ipv4.method:          auto
ipv4.addresses:       --
ipv4.gateway:         --
ipv4.dhcp-client-id:  --

NetworkManager chose a client ID based on the Wi-Fi MAC address. It repeatedly sent DHCP DISCOVER messages, but received no OFFER:

ipv4.dhcp-client-id: no explicit client-id configured
client-id: set effective 01:[MAC REDACTED]
event: send DISCOVER to 255.255.255.255
event: send DISCOVER to 255.255.255.255
event: send DISCOVER to 255.255.255.255

I then disabled the client ID for the connection:

sudo nmcli connection modify "<connection-name>" ipv4.dhcp-client-id none
sudo nmcli connection up "<connection-name>"

The next DHCP request received a lease:

ipv4.dhcp-client-id: set to "none"
event: send DISCOVER to 255.255.255.255
event: received OFFER of 192.168.0.192 from 192.168.0.1
event: send REQUEST of 192.168.0.192 to 255.255.255.255
event: received ACK of 192.168.0.192 from 192.168.0.1
state changed new lease, address=192.168.0.192

The setting remains active after reconnecting. The laptop currently has 192.168.0.192/24 and an IPv4 default route through 192.168.0.1.

Expected result

NetworkManager obtains an IPv4 lease with the default connection profile.

Actual result

NetworkManager received no DHCP OFFER with its automatically selected client ID. It received a lease on the next activation after ipv4.dhcp-client-id was set to none.

Additional context

I saw the same IPv6-only symptom on another Omarchy laptop on this network, although I did not repeat the client ID test on that machine.

This may depend on the router's DHCP implementation. I am reporting it to Omarchy because it appeared after the Quattro networking migration to NetworkManager. I do not know whether Omarchy should change a migration default or document the workaround. The reproducible result is that the DHCP lease arrived as soon as I disabled the client ID.