From: Maykel Moya <mmoya@mmoya.org>
To: wireguard@lists.zx2c4.com
Subject: Re: [WireGuard] Demo Server: Dual stack?
Date: Wed, 28 Dec 2016 14:19:57 +0100 [thread overview]
Message-ID: <7973130b-159b-a7c9-c2d8-24ca7afa8914@mmoya.org> (raw)
In-Reply-To: <CAHmME9qTLVPVrCnrusb3W32EtGYvLuKyyiGz+TWrXTxneVSrCA@mail.gmail.com>
On 16/11/16 15:49, Jason A. Donenfeld wrote:
> On Wed, Nov 16, 2016 at 3:38 PM, Dan Lüdtke <mail@danrl.com> wrote:
>> 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.
>
> I see what you mean. That's a fair point. We might as well give people
> an opportunity for trying things out, indeed.
Chiming in just to tell that my ip6 experience is a breeze since
wireguard appeared.
Right now I found myself advocating WG more as a simple-to-configure and
reliable-roaming ip6 tunnelling technology than a VPN itself.
I've previously used HE (with a handcrafted mechanism to update my
public ip4 endpoint whenever it changed) or SiXXs with a new daemon
running in my system.
With WG it's just setup and forget. Roaming is *reliable*, subjective
performance is impressive (you've done the measures, I just browse and
use services from the v6 internet without hassle).
IMHO ip6 tunnelling is a(nother) good selling point of WG.
Cheers,
maykel
next prev parent reply other threads:[~2016-12-28 13:11 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
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 [this message]
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=7973130b-159b-a7c9-c2d8-24ca7afa8914@mmoya.org \
--to=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).