Re: NetworkManager Plugin

From: Jordan DeBeer <debee1jp@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: NetworkManager Plugin
Date: Wed, 14 Feb 2018 11:58:39 -0500	[thread overview]
Message-ID: <CAFi5oX6LM+A=jbPmhffc4wT+pKmMg8xi=2ebSMg=s7Qg2AY_sw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qVoBkdu35n4aGdZ8nCH6ONZhcGb=WCGx2LGbyHgJMTSw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2195 bytes --]

Hello Max,

I went ahead and tested this on Fedora 27 w/ NetworkManager 1.8.6-1.fc27
and was able to get it working.  A few things I noticed:

Starting the VPN with SELinux enabled results in a number of alerts.
Mostly for the sysctl source process.  This is to be expected as you
mentioned you were testing on Arch.  If this ever ends up getting packaged
for Fedora the policies can probably be added to the RPM.

The DNS field under Identity does not currently function.  I am not sure
how you want to handle this field as NetworkManager has their own DNS field
under the IPv4 tab in the GUI.

The Endpoint section of the GUI only accepts IP addresses and not FQDNs.

and the last thing I noticed: the Private Key section is required.  This
breaks functionality if you were to have your private key stored in a
password manager.  This is solvable by just pasting a properly formatted
key (I just used my public key) into the field and adding a Post Up script
to grab the private key string.

I am going to keep playing around with this and possibly work on packaging
it into an RPM.

This adds quite a bit of value to Wireguard imo so glad to see you worked
on this.  Thank you!

Cheers,
Jordan DeBeer

On Wed, Feb 14, 2018 at 10:28 AM, Jason A. Donenfeld <Jason@zx2c4.com>
wrote:

> Hey Max,
>
> This is wonderful news. I'm happy to work with you to make sure this
> comes out perfectly, and maybe when it's finished we can submit it
> upstream to NetworkManager, similar to how systemd-networkd now has
> WireGuard support built-in.
>
> The biggest hurdle I currently see is entirely removing the dependency
> on wg-quick and wg, and talking Netlink yourself to the kernel, just
> like systemd-networkd does. It shouldn't be too hard to adopt the
> libmnl-based code in wg(8) to be suitable for your usage; I can assist
> with this. In general, the fwmark/routing logic of wg-quick should
> probably be done in a NetworkManager-centric way, which means not
> using wg-quick.
>
> Looks like things are off to a great start!
>
> Jason
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

[-- Attachment #2: Type: text/html, Size: 2889 bytes --]