libvopono VS network-manager-wireguard

But I wanted to switch to communicating with rtnetlink directly first (instead of shelling out to ip etc.) - and did a little bit of work on that here. This would allow you to write programs that can use vopono as a library - creating network namespaces for functions/closures, e.g. for web scraping, etc.

I made some progress with libvopono but still need to add in the wgquick and Openvpn3 functionality.

I'm also (slowly) working on making vopono a library too, so you could run spawn a network namespace and Wireguard connection to run a specific closure (i.e. reqwest requests, etc.) - https://github.com/jamesmcm/libvopono

git clone https://github.com/max-moser/network-manager-wireguard

I used to use a neat little plugin - network-manager-wireguard to make my wireguard connections using the GUI under VPN connections. It's dead simple - create the profile and it shows up in the tool bar as a toggle switch. Unfortunately it breaks in network-manager v1.36 and above, so I've locked it to v1.34 . I make different wireguard connections daily so it's inconvenient to have to go into nmtui to make the connection if I go that route...

NetworkManager supports WireGuard natively. I wouldn't use the networkmanager-wireguard package, which is the VPN plugin (from https://github.com/max-moser/network-manager-wireguard). I would uninstall that.

For network manager: https://github.com/max-moser/network-manager-wireguard and if you use gnome, VPN status will be shown in the top bar.

git clone https://github.com/max-moser/network-manager-wireguard

On Arch I installed this package to get a GUI for WireGuard in the Gnome Control Panel. It doesn't look like anyone has packaged it for Ubuntu, but you could install it from source.