| 6 Jun 2023 |
 @elvishjerricco:matrix.org | I wonder what creates the incoming traffic | 14:30:28 |
 oddlama | Probably mdns | 14:30:33 |
| oddlama | The working server is in my home network | 14:30:46 |
| oddlama | The non working one is a hetzner server with a public ipv4 and no other machines on the network | 14:31:04 |
| @elvishjerricco:matrix.org | Hm, something tells me that the reference to man:rtnetlink(7) in the docs section of that unit is relevant | 14:32:43 |
| @elvishjerricco:matrix.org | hmm: ListenNetlink=route 1361 | 14:36:25 |
| @elvishjerricco:matrix.org | oddlama: Maybe you're missing a kernel module relating to this? | 14:36:38 |
| @elvishjerricco:matrix.org | but that's weird because in nixos we have a wants relationship from multi-user.target on systemd-networkd.service | 14:37:27 |
| oddlama | In reply to @elvishjerricco:matrix.org
oddlama: Maybe you're missing a kernel module relating to this? Since this is stage2 I don't see how that could be a problem.. Which module would you have in mind? | 14:39:34 |
| oddlama | Hard to find any information about route 1361 | 14:39:42 |
| @elvishjerricco:matrix.org | no clue :P | 14:39:45 |
| oddlama | occurrs exactly once in systemd's source, in networkd.socket :/ | 14:39:59 |
| oddlama | * occurs exactly once in systemd's source, in networkd.socket :/ | 14:40:05 |
| oddlama | In reply to @elvishjerricco:matrix.org
but that's weird because in nixos we have a wants relationship from multi-user.target on systemd-networkd.service where is that relationship defined? | 14:42:13 |
| @elvishjerricco:matrix.org | https://github.com/NixOS/nixpkgs/blob/5c31944c1d468476f7827943dd636b34478db22b/nixos/modules/system/boot/networkd.nix#L3129 | 14:42:43 |
| @elvishjerricco:matrix.org | oddlama: Something else kinda weird is that on my system that has networkd enabled in both stage 1 and stage 2, I don't see the same messages from the socket unit about "Incoming traffic" | 14:44:21 |
| @elvishjerricco:matrix.org | your default.target is multi-user.target, right? :P | 14:45:03 |
| oddlama | In reply to @elvishjerricco:matrix.org
oddlama: Something else kinda weird is that on my system that has networkd enabled in both stage 1 and stage 2, I don't see the same messages from the socket unit about "Incoming traffic" Maybe it's also a red herring and just coincidence | 14:45:15 |
| @elvishjerricco:matrix.org | possibly | 14:45:22 |
| oddlama | In reply to @elvishjerricco:matrix.org
your default.target is multi-user.target, right? :P I didn't change anything in that regard, so I hope so :D | 14:45:31 |
| @elvishjerricco:matrix.org | (please double check, because it is possible to change) | 14:45:59 |
| @elvishjerricco:matrix.org | (like, it shouldn't, but systemctl status default.target is easy enough :P) | 14:46:34 |
| oddlama | Already on it | 14:46:46 |
| oddlama | Yep, multi-user.target on both systems. | 14:46:59 |
| @elvishjerricco:matrix.org | oddlama: As a sanity check, what's systemctl show -p WantedBy systemd-networkd.service say? | 14:48:24 |
| oddlama | Just did a sanity check on the systemd issues | 14:49:39 |
| oddlama | https://github.com/systemd/systemd/issues/27718 | 14:49:40 |
| oddlama | In reply to @elvishjerricco:matrix.org
oddlama: As a sanity check, what's systemctl show -p WantedBy systemd-networkd.service say? WantedBy=multi-user.target on both | 14:50:32 |
| @elvishjerricco:matrix.org | Interesting tidbit from that issue that I'd like to revisit later:
networkd.service removes some (not all) IP addresses, routes, and friends on stop. Hence, restarting networkd during switching root may disconnect network. So, if the rootfs is backed by a network filesystem, system may fail to boot.
It was my understanding that this is explicitly not the case
| 14:53:49 |
| @elvishjerricco:matrix.org | huh, ok apparently that's only true because we're not actually stopping systemd-networkd.service correctly before switch-root | 14:56:00 |
