From: "Manuel Schölling" <manuel.schoelling@gmx.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard-p2p: A tool for NAT traversal
Date: Mon, 25 Sep 2017 17:31:04 +0200 [thread overview]
Message-ID: <1506353464.15832.1.camel@gmx.de> (raw)
In-Reply-To: <CAHmME9qcEe4jKZbJ4qspULxk3VDmrPe4_B=mT-76pzz6j+m0FQ@mail.gmail.com>
Hi Jason,
On Fri, 2017-09-22 at 03:11 +0200, Jason A. Donenfeld wrote:
> Looks like you rewrote this project from python into rust. Cool!
Yes, it was about time. It took quite a while but I think it was worth
while.
> I'd be interested to learn what's new, what's changed, and what's up
> in general. I always thought this was a pretty neat idea.
>From the functional point of view there is not a lot of change.
You can
A) exchange your public keys using wireguard-p2p (publish & search
modes)
B) setup a wireguard peer-to-peer connection
A) Exchange public keys
-----------------------
You can simply choose a name for your computer (e.g. alice_laptop) and
then bob can search for it:
on Alice's computer: $ cargo run publish wg0 alice_laptop
on Bob's computer: $ cargo run search alice_laptop
=> lists Alice's public key on Bob's console
B) peer-to-peer connection
--------------------------
Just setup your wireguard connections (/etc/wireguard/*.conf files) as
usual but you can leave out the Endpoint.
Add the device and the public keys of the corresponding peers to
/etc/wireguard-p2p.conf like this:
[wg0]
Peer1=<bobs_public_key>
Now start wireguard-p2p using
$ cargo run daemon
wireguard-p2p will try to determine your IP/port using STUN, publish it
in a distributed-hash-table (bulletinboard-dht) and will try to lookup
Bob's IP/port in the distributed-hash-table, too.
If it finds Bob's IP/port, it will proxy data between Alice and Bob.
It's not perfect, yet, but if you guys find some issues, let me know!
Bye,
Manuel
prev parent reply other threads:[~2017-09-25 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 10:41 Manuel Schölling
2017-04-30 12:08 ` Jason A. Donenfeld
2017-09-22 1:11 ` Jason A. Donenfeld
2017-09-25 15:31 ` Manuel Schölling [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=1506353464.15832.1.camel@gmx.de \
--to=manuel.schoelling@gmx.de \
--cc=Jason@zx2c4.com \
--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).