35
Anyone using WireGuard through plain systemd-networkd?
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jul 2024
35 points (100.0% liked)
Selfhosted
40406 readers
369 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Yes I use wireguard only with systemd-networkd (as server and as client).
I followed the arch wiki and you need to ensure that the file permissions are correct, otherwise systemd will ignore them.
Copied from the wiki:
Do you notice anything wrong with my config? https://github.com/systemd/systemd/issues/30495
Have you tried to reduce your config to a minimum (like in the wiki) and add additional parts step by step? F.e. the link and route parts? So you can maybe identify the block/line which breaks your config.
Edit: I have never seen ActivationPolicy before. Is it NixOS specific? An additional idea how are your files named? systemd-networkd uses the name of the file as indicator for the initialization order (alphanumeric order is applied here). Which means that wireguard.network will be used xx.network. I mean the lower w is near the end of the ascii table, but the devil is in the details and maybe your ethernet or wifi connection will be established after wireguard and therefore wireguard will not be able to connect. F.e. wlan.network for example will come up after wireguard.network. (As I remember that would not be the case using wg-quick, because its unit file depends network-online.target.)
The
ActivationPolicyI added in an attempt to replicate whatwg-quickproduces, as I recall.Do you have a link where it is documented in systemd-networkd content?