Describe the bug
I could boot the installer ISO (GNOME version) for 21.05 without an issue, and within the live session I have a stable connection with properly assigned IPv4 and IPv6 addresses. Rebooting after the install, NetworkManager will repeatedly notify that the activation of the network has failed. Checking the logs of NetworkManager showed the following repeated lines:
device (eno2): failure to start DHCPv6: failed to start client: Address already in use
device (eno2): Activation: failed for connection 'Wired connection 1'
Checking the logs of dhcpcd also revealed repeated addition and removal of the same IPv4 and IPv6 addresses.
I found #72416 that is somewhat similar as well, except that NetworkManager has dhcp set to internal. By disabling dhcpcd, my network access is fully working without a problem. But enabling it even with NetworkManager's dhcp set to dhcpcd, the same issue occurs.
I first disabled DHCPv6, and the problem persisted. Then I realised that my router advertisements flags are set to M+O+A (Stateful DHCPv6 and SLAAC), whereby A only (SLAAC only) solves the problem entirely. So it is likely the RA flags that triggers the conflict between dhcpcd and NetworkManager.
To Reproduce
Steps to reproduce the behavior:
Install NixOS with minimal changes to the generated configs
Reboot and see network issues on a network with DHCPv6 enabled
Expected behavior
Since NetworkManager is enabled, I don't see a reason for dhcpcd to be running as well, it should default to being disabled especially when NetworkManager uses its internal library for DHCP.
Additional context
My local network is dual stack with working global IPv6 addresses, with both DHCPv6 and SLAAC enabled.
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:
networking.networkmanager
networking.dhcpcd
Describe the bug I could boot the installer ISO (GNOME version) for 21.05 without an issue, and within the live session I have a stable connection with properly assigned IPv4 and IPv6 addresses. Rebooting after the install, NetworkManager will repeatedly notify that the activation of the network has failed. Checking the logs of NetworkManager showed the following repeated lines:
Checking the logs of dhcpcd also revealed repeated addition and removal of the same IPv4 and IPv6 addresses.
I found #72416 that is somewhat similar as well, except that NetworkManager has
dhcp
set tointernal
. By disabling dhcpcd, my network access is fully working without a problem. But enabling it even with NetworkManager'sdhcp
set todhcpcd
, the same issue occurs.I first disabled DHCPv6, and the problem persisted. Then I realised that my router advertisements flags are set to M+O+A (Stateful DHCPv6 and SLAAC), whereby A only (SLAAC only) solves the problem entirely. So it is likely the RA flags that triggers the conflict between dhcpcd and NetworkManager.
To Reproduce Steps to reproduce the behavior:
Expected behavior Since NetworkManager is enabled, I don't see a reason for dhcpcd to be running as well, it should default to being disabled especially when NetworkManager uses its internal library for DHCP.
Additional context My local network is dual stack with working global IPv6 addresses, with both DHCPv6 and SLAAC enabled.
Metadata
Maintainer information: