summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
diff options
context:
space:
mode:
authorMajiir Paktu <majiir@nabaal.net>2023-10-07 12:40:42 -0400
committerMajiir Paktu <majiir@nabaal.net>2023-10-14 13:57:32 -0400
commitc4228b6c8f662a3e3022c187ec40f4debafbd454 (patch)
treeec83c231adf2236220aa88a7d526b838e9a5d3e0 /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
parentaf4598273b3ed2be66cc1d52ce8a98ef2c43090d (diff)
nixos/network-interfaces-systemd: fix DHCP setting
The networkd backend logic for setting DHCP= on an interface is bugged and inconsistent with the scripted logic. Consider this simple NixOS configuration: { networking.useNetworkd = true; networking.interfaces.eth0.wakeOnLan.enable = true; } The default value of networking.useDHCP is true, so we expect our eth0 interface to have DHCP enabled. With the scripted backend, this works. But the networkd backend generates the following 40-eth0.network file: [Match] Name=eth0 [Network] DHCP=no IPv6PrivacyExtensions=kernel This is happening because the wakeOnLan configuration creates a key in networking.interfaces, and the networkd backend erroneously checks that instead of for explicitly configured IP addresses as in the scripted backend. The documentation is also inconsistent across various options. This change aligns the networkd backend and option documentation to the actual behavior of the scripted backend, and updates a test to account for this behavior for both backends.
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions