From: "Manuel Schölling" <manuel.schoelling@gmx.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, Maykel Moya <mmoya@mmoya.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: NetworkManager Plugin
Date: Fri, 16 Feb 2018 16:07:14 +0100 [thread overview]
Message-ID: <1518793634.23818.33.camel@gmx.de> (raw)
In-Reply-To: <CAHmME9oy2uhNfG4vXYHLK2eq36qZA_QWfrTnMrQJWis6sqDTag@mail.gmail.com>
Hi,
On Fri, 2018-02-16 at 06:33 +0100, Jason A. Donenfeld wrote:
> I think he's working on some wilder plugin that incorporates his DHT
> stuff, which is a separate effort from Max's. My personal preference
> is getting a lightweight but functional NetworkManager plugin out
> there for users, that doesn't come with the baggage or bells&whistles
> of the DHT. But for people using the DHT work, having the plugin for
> that is undoubtedly useful.
Yeah, I gave that presentation. The plugin I wrote is suppose to work
for both: raw wireguard and my wireguard-p2p solution, that lets you
circumvent the NAT and dyndns problems. I wrote it in Rust because I
really did not go through all the pain with GTK that Max went through
;)
My plugin comes independent of the DHT client (it just communicates
with it via dbus if the DHT client is installed). However, it's written
in Rust, so I don't think that it would be easy to get it accepted
upstream.
next prev parent reply other threads:[~2018-02-16 15:00 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 [this message]
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=1518793634.23818.33.camel@gmx.de \
--to=manuel.schoelling@gmx.de \
--cc=Jason@zx2c4.com \
--cc=mmoya@mmoya.org \
--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).