WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: Marc Fawzi <marc.fawzi@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Steven Honson <steven@honson.id.au>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: RFC: wg syncpeers wg0 wireguard.conf
Date: Sun, 16 Jun 2019 12:43:40 -0700
Message-ID: <CACioZitcmZOmEAZox6VoAy-OCvDXoqRqkvosxNNwuv9LLwLnng@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qhuZrj8StZq_7ZbSagp8XGN5Q8U-b1hkcca3AwU2v7mA@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 1444 bytes --]

Hi Jason,

There are a few projects on github that show up under “Wireguard dynamic”
and most have to do with the functionality I believe you guys are
discussing here (please correct me if I’m wrong) which is how to update the
peers on the wg interface (both add and remove) from the configuration.
There is one called Wireguard-dynamic that has to do with configuring a
mesh by using a key-value DHT or a shared kv store.
https://github.com/segator/wireguard-dynamic/issues/2#issuecomment-502478520

There is also P2P-Wireguard in Rust that uses a STUN server to support
nodes behind NAT.

And wg-broker (another project) that is closer to what I’m looking for.

The official wg-dynamic I think has to do with DHCP like functionality
(from what I managed to read so far) so I understand its completely
separate but the confusion around what “dynamic” is refers to is
unfortunate (naming is always a tricky issue)

Btw, may I suggest having two mailing lists: one for users like myself and
another for contributors and core developers? In Tensorflow and other OSS
we have such separation between the platform Developers and the users.




On Fri, Jun 14, 2019 at 11:02 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> On Fri, Jun 14, 2019 at 8:01 PM Marc Fawzi <marc.fawzi@gmail.com> wrote:
> > p.s. does this overlap with similar planned in wg-dynamic?
>
> No, the topics have no similarities.
>

[-- Attachment #1.2: Type: text/html, Size: 2183 bytes --]

<div><div dir="auto">Hi Jason,</div></div><div dir="auto"><br></div><div dir="auto">There are a few projects on github that show up under “Wireguard dynamic” and most have to do with the functionality I believe you guys are discussing here (please correct me if I’m wrong) which is how to update the peers on the wg interface (both add and remove) from the configuration.  There is one called Wireguard-dynamic that has to do with configuring a mesh by using a key-value DHT or a shared kv store. <div><a href="https://github.com/segator/wireguard-dynamic/issues/2#issuecomment-502478520">https://github.com/segator/wireguard-dynamic/issues/2#issuecomment-502478520</a></div></div><div dir="auto"><br></div><div dir="auto">There is also P2P-Wireguard in Rust that uses a STUN server to support nodes behind NAT.</div><div dir="auto"><br></div><div dir="auto">And wg-broker (another project) that is closer to what I’m looking for. </div><div dir="auto"><br></div><div dir="auto">The official wg-dynamic I think has to do with DHCP like functionality (from what I managed to read so far) so I understand its completely separate but the confusion around what “dynamic” is refers to is unfortunate (naming is always a tricky issue) </div><div dir="auto"><br></div><div dir="auto">Btw, may I suggest having two mailing lists: one for users like myself and another for contributors and core developers? In Tensorflow and other OSS we have such separation between the platform Developers and the users. </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 14, 2019 at 11:02 AM Jason A. Donenfeld &lt;<a href="mailto:Jason@zx2c4.com">Jason@zx2c4.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Jun 14, 2019 at 8:01 PM Marc Fawzi &lt;<a href="mailto:marc.fawzi@gmail.com" target="_blank">marc.fawzi@gmail.com</a>&gt; wrote:<br>
&gt; p.s. does this overlap with similar planned in wg-dynamic?<br>
<br>
No, the topics have no similarities.<br>
</blockquote></div></div>

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 19:59 Lonnie Abelbeck
2019-06-10 12:34 ` Rene 'Renne' Bartsch, B.Sc. Informatics
2019-06-11 17:28 ` Jason A. Donenfeld
2019-06-11 21:06   ` Lonnie Abelbeck
2019-06-11 21:41     ` Kalin KOZHUHAROV
2019-06-12  0:22   ` Steven Honson
2019-06-12  0:25     ` Marc Fawzi
2019-06-14 18:01       ` Jason A. Donenfeld
2019-06-16 19:43         ` Marc Fawzi [this message]
2019-06-13 23:15   ` Lonnie Abelbeck
2019-06-14 18:09   ` Jason A. Donenfeld
2019-06-14 20:48     ` Lonnie Abelbeck
2019-06-14 21:14     ` Ivan Labáth

Reply instructions:

You may reply publically 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=CACioZitcmZOmEAZox6VoAy-OCvDXoqRqkvosxNNwuv9LLwLnng@mail.gmail.com \
    --to=marc.fawzi@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=steven@honson.id.au \
    --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

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com zx2c4-wireguard@archiver.kernel.org
	public-inbox-index wireguard


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/ public-inbox