NixOS Networking | 902 Members | |
| Declaratively manage your switching, routing, wireless, tunneling and more. | 269 Servers |
| Sender | Message | Time |
|---|---|---|
| 17 Apr 2026 | ||
| 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 | ||
| 29 Apr 2026 | ||
| 14:44:31 | ||
| 30 Apr 2026 | ||
| hey, I'm slowly going insane trying to configure my router to send certain traffic over a wireguard tunnel. As far as I can tell I have the wireguard connection up (I see handshakes and sent / recieved bytes in wg status). I set a route over the tunnel though and no traffic actually makes it across. I'd really appreciate some pointers in how to debug, I've exhausted my realatively limited networking knowledge. I'm using systemd-networkd, I have a brigde interface (for my lan switch) a wan interface, and a whole bunch of wireguard interfaces and routing across most of the wireguard interfaces work fine, but they are in private subnets. What I'm trying to do with this one is send some traffic to a public IP on the internet over a wireguard interface rather than my default route. | 13:53:52 | |
| Is the machine on the other end configured to actually forward packets? | 13:56:05 | |
| yeah it's mullvad | 14:00:03 | |
| And what is allowedIPs set to on the interface? | 14:00:32 | |
| 0.0.0.0/0 | 14:00:57 | |
| That looks normal then | 14:01:21 | |
| Are you doing NAT on the router? | 14:01:23 | |
| It's possible that Mullvad won't NAT random packets | 14:01:33 | |
| So you have to double NAT | 14:01:35 | |
| I have a very very similar config running on another host but where I've made it my default route | 14:02:17 | |
| and that works | 14:02:19 | |
| That would imply no NAT | 14:02:35 | |
| I've also tried making it the default route on this host and that didn't work either | 14:03:31 | |