Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Max Moser <e1326252@student.tuwien.ac.at>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: NetworkManager Plugin
Date: Wed, 14 Feb 2018 14:47:20 -0500	[thread overview]
Message-ID: <87zi4bpd4n.fsf@fifthhorseman.net> (raw)
In-Reply-To: <CAHmME9qVoBkdu35n4aGdZ8nCH6ONZhcGb=WCGx2LGbyHgJMTSw@mail.gmail.com>

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

On Wed 2018-02-14 16:28:59 +0100, Jason A. Donenfeld wrote:

> 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.

last time i looked, network-manager included a local copy of a big chunk
of systemd code.  so it's possible that a newer version of
network-manager will already have the systemd-networkd code available to
it, and you just need to hook into it correctly from the nm internals.

        --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      parent reply	other threads:[~2018-02-14 20:57 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
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 [this message]

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=87zi4bpd4n.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=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).