From: "Dan Lüdtke" <mail@danrl.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Demo Server: Dual stack?
Date: Wed, 16 Nov 2016 15:38:05 +0100 [thread overview]
Message-ID: <44DAF4D4-00A8-4903-8003-EB0215635B61@danrl.com> (raw)
In-Reply-To: <CAHmME9r0tdR8=nnC4yPLJoOE8yU_7iJi0qEpx9POyM3OBZ3otQ@mail.gmail.com>
Hi Jason,
> I guess I could provide IPv6 connectivity, but.... why? It's a demo.
Because it is a demo of a brand new protocol, showing how it can be used =
with legacy versions payload and transport protocol. I find that odd, =
but as I understand we have contradicting point of views on IP =
protocols.
> If you're using it as an access point to the Internet with intentions
> beyond simply trying out WireGuard, then you're abusing my service.
I am not using it at all. But it would be useful for howtos and blog =
posts to reference it. I don't use vintage IP in my posts, so I can't =
refer to the official demo server.
Since many potential peers are behind NATs using RFC1918 legacy IP =
addresses AND have global unicast IP addresses (which are easier to =
whitelist in a firewall than maintaining port forwarding in networks =
using a dynamic configuration protocol) I expect WireGuard to be =
especially useful using IPv6 as transport.
BTW, I don't see any reason why the demo server should forward to the =
Internet at all. Connectivity between peers/server and accessing the =
hidden website would be enough for my usecase (howtos/blog posts), which =
may be a different one than what you intended when you setup the server.=20=
> I'm happy to consider this, but I'll need to be convinced that this
> actually matters.
Unfortunately :) I, for one, need to be convinced why I should create =
lasting documentation using an EOL IP protocol. Why does IPv4 matter =
more than IPv6? Usually, latency is better when using IPv6. Latency is =
probably the first thing demo users test (ping through the tunnel).
However, if you like to share some information how to set up one myself, =
I am happy to host a IPv6 demo server. Currently I am wondering how to =
accept *any* public key in the [Peer] config.
Cheers,
Dan
> Jason
>=20
> On Wed, Nov 16, 2016 at 12:39 PM, Dan L=C3=BCdtke <mail@danrl.com> =
wrote:
>> Jason,
>>=20
>> do you plan on adding IPv6 compatibility to the demo server? If not, =
do you mind if I set one up? How difficult is it to run the demo server. =
It just accepts every key, right?
>>=20
>> Cheers,
>>=20
>> Dan
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> http://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2016-11-16 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 11:39 Dan Lüdtke
2016-11-16 14:18 ` Jason A. Donenfeld
2016-11-16 14:38 ` Dan Lüdtke [this message]
2016-11-16 14:45 ` Dan Lüdtke
2016-11-16 14:49 ` Jason A. Donenfeld
2016-11-16 14:54 ` Dan Lüdtke
2016-11-16 15:09 ` Jason A. Donenfeld
2016-12-28 13:19 ` Maykel Moya
2016-12-29 9:22 ` [WireGuard] " Jörg Thalheim
2016-12-31 2:28 ` Jason A. Donenfeld
2016-12-31 2:27 ` [WireGuard] Demo Server: " Jason A. Donenfeld
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=44DAF4D4-00A8-4903-8003-EB0215635B61@danrl.com \
--to=mail@danrl.com \
--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).