Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Max Moser <e1326252@student.tuwien.ac.at>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: NetworkManager Plugin
Date: Wed, 14 Feb 2018 16:28:59 +0100	[thread overview]
Message-ID: <CAHmME9qVoBkdu35n4aGdZ8nCH6ONZhcGb=WCGx2LGbyHgJMTSw@mail.gmail.com> (raw)
In-Reply-To: <7d5325a3-fa07-f67f-a31e-aadd44458d41@student.tuwien.ac.at>

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

  reply	other threads:[~2018-02-14 15:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 15:05 Max Moser
2018-02-14 15:28 ` Jason A. Donenfeld [this message]
2018-02-14 16:58   ` Jordan DeBeer
2018-02-15  0:34     ` Maximilian Moser
2018-02-15 14:07       ` Jason A. Donenfeld
2018-02-15 14:35         ` Maximilian Moser
2018-02-15 14:46           ` Jason A. Donenfeld
2018-02-15 14:57             ` Maximilian Moser
2018-02-15 20:15               ` Maykel Moya
2018-02-16  5:33                 ` Jason A. Donenfeld
2018-02-16 10:43                   ` Max Moser
2018-02-16 15:07                   ` Manuel Schölling
2018-02-16 21:00                     ` Javier Arteaga
2018-02-14 19:47   ` Daniel Kahn Gillmor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHmME9qVoBkdu35n4aGdZ8nCH6ONZhcGb=WCGx2LGbyHgJMTSw@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=e1326252@student.tuwien.ac.at \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).