From: "Manuel Schölling" <manuel.schoelling@gmx.de>
To: wireguard@lists.zx2c4.com
Subject: WireGuard-p2p: A tool for NAT traversal
Date: Sun, 30 Apr 2017 12:41:47 +0200 [thread overview]
Message-ID: <1493548907.5730.1.camel@gmx.de> (raw)
Hi,
I wrote a python tool for scenarios where both WireGuard peers are
behind a NAT.
It supports public key exchange, NAT traversal using STUN, and IP
address exchange. The exchange of this information is done using a DHT.
You can find it here:
https://github.com/manuels/wireguard-p2p
Any feedback would be appreciated.
Bye,
Manuel
next reply other threads:[~2017-04-30 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 10:41 Manuel Schölling [this message]
2017-04-30 12:08 ` WireGuard-p2p: A tool for NAT traversal Jason A. Donenfeld
2017-09-22 1:11 ` Jason A. Donenfeld
2017-09-25 15:31 ` Manuel Schölling
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=1493548907.5730.1.camel@gmx.de \
--to=manuel.schoelling@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.