mirror of
https://github.com/NixOS/nixpkgs.git
synced 2025-02-23 04:25:14 +00:00
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
This commit is contained in:
parent
e89b1063fb
commit
eeeb2bf803
@ -377,6 +377,17 @@ services.xserver.displayManager.defaultSession = "xfce+icewm";
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
The <package>dhcpcd</package> package <link xlink:href="https://roy.marples.name/archives/dhcpcd-discuss/0002621.html">
|
||||
does not request IPv4 addresses for tap and bridge interfaces anymore by default</link>.
|
||||
In order to still get an address on a bridge interface, one has to disable
|
||||
<literal>networking.useDHCP</literal> and explicitly enable
|
||||
<literal>networking.interfaces.<name>.useDHCP</literal> 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.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
GnuPG is now built without support for a graphical passphrase entry
|
||||
|
Loading…
Reference in New Issue
Block a user