From 3c8150a5aaa19f11ea83c34f3e6c55a5c53ada60 Mon Sep 17 00:00:00 2001 From: Chandler Swift Date: Fri, 1 Nov 2024 01:30:48 -0500 Subject: [PATCH] Fix stage2 IPv6 networking When `ip=dhcp` is passed as a kernel param (which I assume, but don't know for sure, just gets passed to systemd and probably then to systemd-networkd or NetworkManager or whatever does the networking in the initrd?), IPv6 doesn't come up. With the param, bad IPv6: ```text 2: eno1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 3c:52:82:00:46:d6 brd ff:ff:ff:ff:ff:ff altname enp0s31f6 inet 192.168.1.20/24 brd 192.168.1.255 scope global eno1 valid_lft forever preferred_lft forever inet6 2601:441:8301:8af7:94e1:4d4c:73c2:ac31/64 scope global temporary dynamic valid_lft 322763sec preferred_lft 86330sec inet6 fd0a:8f9f:6f83:0:3e52:82ff:fe00:46d6/64 scope global dynamic mngtmpaddr proto kernel_ra valid_lft forever preferred_lft forever inet6 2601:441:8301:8af7:3e52:82ff:fe00:46d6/64 scope global dynamic mngtmpaddr proto kernel_ra valid_lft 322763sec preferred_lft 322763sec inet6 fe80::3e52:82ff:fe00:46d6/64 scope link proto kernel_ll valid_lft forever preferred_lft forever ``` whereas without the param I get good (whatever that means) addresses: ```text 2: eno1: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 3c:52:82:00:46:d6 brd ff:ff:ff:ff:ff:ff altname enp0s31f6 inet 192.168.1.20/24 brd 192.168.1.255 scope global dynamic noprefixroute eno1 valid_lft 43188sec preferred_lft 43188sec inet6 fd0a:8f9f:6f83::33b/128 scope global dynamic noprefixroute valid_lft 43190sec preferred_lft 43190sec inet6 2601:441:8301:8af7::33b/128 scope global dynamic noprefixroute valid_lft 43190sec preferred_lft 43190sec inet6 2601:441:8301:8af7:b572:fc6c:ba27:dcdb/64 scope global temporary dynamic valid_lft 322965sec preferred_lft 86235sec inet6 2601:441:8301:8af7:f3f0:df23:a6bb:7d25/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 322965sec preferred_lft 322965sec inet6 fd0a:8f9f:6f83:0:485e:f55d:fa1d:cef4/64 scope global temporary dynamic valid_lft 604790sec preferred_lft 86235sec inet6 fd0a:8f9f:6f83:0:7851:1417:807:f017/64 scope global mngtmpaddr noprefixroute valid_lft forever preferred_lft forever inet6 fe80::eb0c:1983:24a5:3e42/64 scope link noprefixroute valid_lft forever preferred_lft forever ``` I'm honestly not entirely sure what this _should_ look like, but what I _do_ know is that in the "bad" configuration, SSH takes an extra ~10s to connect as it has to wait for two ~5s `No route to host` timeouts: ```console [chandler@oscar:~]$ ssh -v root@bert OpenSSH_9.8p1, OpenSSL 3.0.14 4 Jun 2024 debug1: Reading configuration data /home/chandler/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 5: Applying options for * debug1: Connecting to bert [fd0a:8f9f:6f83::33b] port 22. debug1: connect to address fd0a:8f9f:6f83::33b port 22: No route to host debug1: Connecting to bert [2601:441:8301:8af7::33b] port 22. debug1: connect to address 2601:441:8301:8af7::33b port 22: No route to host debug1: Connecting to bert [192.168.1.20] port 22. debug1: Connection established. ``` Future work: What _should_ my IPv6 config look like? Is there any way I can keep network config stable between the initrd and the booted system? Why is this recommended against? > The default is false when systemd is enabled in initrd, because the > systemd-networkd documentation suggests it. --- bert/configuration.nix | 1 + 1 file changed, 1 insertion(+) diff --git a/bert/configuration.nix b/bert/configuration.nix index 5f46d8b..d3d4d92 100644 --- a/bert/configuration.nix +++ b/bert/configuration.nix @@ -19,6 +19,7 @@ availableKernelModules = [ "e1000e" ]; network = { enable = true; + flushBeforeStage2 = true; # Without this, stage2 IPv6 config is messed up? ssh = { enable = true; port = 22;