NixOS Networking | 878 Members | |
| Declaratively manage your switching, routing, wireless, tunneling and more. | Don't rely on `networking.*` for interface and routing setup, use systemd-networkd, ifstate or NetworkManager instead. | Set `SYSTEMD_LOG_LEVEL=debug` to debug networking issues with networkd | No bad nft puns, please. | Room recommendations: #sysops:nixos.org | 255 Servers |
| Sender | Message | Time |
|---|---|---|
| 16 Apr 2026 | ||
| 12:22:16 | ||
| 17:35:35 | ||
so, hm, I have not rebooted this host in a while (47 days since last boot on nixos-unstable, using systemd.networkd.enable=true) but now that I have rebooted it, it is refusing to set up its hostbr0 bridge, networkctl reports that hostbr0 is in "no-carrier configuring" state, ip -br l shows that interface as DOWN in NO-CARRIER state; it's backed by an ethernet device that also shows no carrier (but ... has a lit link LED)? I'm really at a loss how to debug this, all signs say this should work but it doesn't come up. | 18:58:21 | |
| (deleting the bridge and setting the ethernet interface up shows traffic if I tcpdump it, I should add) | 18:59:20 | |
| oh, that's right, there should be VLAN netdevs that aren't created | 19:06:55 | |
yeuuuup, looks like [Match] block semantics changed: previously in a .network file I had to match the "old" name (enp*) when now I have to match the renamed name that a preceding .link file effects | 19:09:41 | |
| How wonderful | 20:28:33 | |
In reply to @antifuchs:asf.computerI always had the least amount of pain when I matched hardware interfaces by MACAddress | 20:44:22 | |
| 23:14:12 | ||
| 17 Apr 2026 | ||
In reply to @oddlama:matrix.orgWell, I did that in addition but since there are bridges with inherited Mac’s in the mix, the config also has to match on device names | 02:59:52 | |
| It’s supremely annoying and makes me want to redo the whole thing but also … not | 03:00:11 | |
| that breaks with vlans though | 03:06:55 | |
| Redacted or Malformed Event | 03:07:07 | |
| 08:36:58 | ||
| 08:41:50 | ||
| 16:58:37 | ||
| Kind= might be a bit less painful tbh, but ughhh testing this means a reboot each time | 17:47:45 | |
| you can check networkctl for the correct kind | 18:08:16 | |
| 22 Apr 2026 | ||
| 19:19:00 | ||
| 24 Apr 2026 | ||
| 20:52:21 | ||
| 25 Apr 2026 | ||
| I just tried to swap a wireguard client from wg-quick to systemd.network, and did not have a good time | 00:11:34 | |
| how so | 00:12:28 | |
| Well, I made an attempt to go from this:
to this:
and it kinda worked. | 04:54:13 | |
| But I have major gripes | 04:54:57 | |
| First, systemd.network does not behave like you expect from a deterministic sense - I had to manually tear down wg interfaces multiple times because I screwed something up. | 04:55:50 | |
| Second, for some reason this broke docker container to container networking when using the host network, and I have no idea why, other than that there must be something I have massively misconfigured | 04:56:45 | |
| I ended up swapping back to wg-quick for now since it's been such a pain | 04:57:23 | |
| I guess my routing table there was sending docker's traffic to the remote as well? I don't know, it's just a frustrating swap to try to make | 04:59:28 | |
| 26 Apr 2026 | ||
| 03:44:06 | ||
| 23:25:18 | ||