It feels awkward to have half the wireguard code in main (kernel), and leave the configuration bits out in favor of our own tools, which probably didn't exist when the wireguard userspace tooling was created. If you go to the wireguard site, it won't teach you how to use systemd- networkd or netplan to configure wireguard: it will talk about wg and wg-quick, which ubuntu users won't have supported in the next LTS release.
If you google for "how to configure wireguard", none of the hits (checked first page only) talk about systemd-networkd or netplan. The netplan documentation mentions wireguard, but does not say how to generate the keys: https://netplan.io/reference/#properties-for-device- type-tunnels%3A This documentation can be improved, as you say, but won't change the fact that we will be the odd ones out by not using upstream's tooling. Doesn't the "duplicated functionality" argument apply to the major bits of wireguard code that are in the kernel in main already? Shall we remove it from the kernel then and go back to having the dkms build only? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950317 Title: [MIR] Wireguard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
