From eeeb2bf8035b309a636d596de6a3b1d52ca427b1 Mon Sep 17 00:00:00 2001 From: Justin Humm Date: Wed, 11 Mar 2020 00:32:44 +0100 Subject: [PATCH] nixos/release-notes: mention that dhcpcd stopped giving IPv4 addresses to bridges by default This is an backward incompatible change from upstream dhcpcd [0], as this could have easily locked me out of my box. As dhcpcd doesn't allow to use only a blacklist (denyinterfaces in dhcpcd.conf) of devices and use all remaining devices, while explicitly allowing some interfaces like bridges, I think the best option would be to not change anything about it and just educate the users here about that edge case and how to solve it. [0] https://roy.marples.name/archives/dhcpcd-discuss/0002621.html --- nixos/doc/manual/release-notes/rl-2003.xml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/nixos/doc/manual/release-notes/rl-2003.xml b/nixos/doc/manual/release-notes/rl-2003.xml index 3aa06c3bb2bd..9147ee49eee7 100644 --- a/nixos/doc/manual/release-notes/rl-2003.xml +++ b/nixos/doc/manual/release-notes/rl-2003.xml @@ -377,6 +377,17 @@ services.xserver.displayManager.defaultSession = "xfce+icewm"; + + + The dhcpcd package + does not request IPv4 addresses for tap and bridge interfaces anymore by default. + In order to still get an address on a bridge interface, one has to disable + networking.useDHCP and explicitly enable + networking.interfaces.<name>.useDHCP on + every interface, that should get an address via DHCP. This way, dhcpcd + is configured in an explicit way about which interface to run on. + + GnuPG is now built without support for a graphical passphrase entry