Development discussion of WireGuard
 help / color / mirror / Atom feed
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:54:49 +0100	[thread overview]
Message-ID: <7FCCB728-BB7E-4A4F-ABAC-7D16FA6A1382@danrl.com> (raw)
In-Reply-To: <CAHmME9qTLVPVrCnrusb3W32EtGYvLuKyyiGz+TWrXTxneVSrCA@mail.gmail.com>

Thanks Jason!

No hurry, though.

Is the script open source as well? Maybe I can tinker with it, so you =
don't waste your precious development time on supporting infrastructure.

> On 16 Nov 2016, at 15:49, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>=20
> Hey Dan,
>=20
> On Wed, Nov 16, 2016 at 3:38 PM, Dan L=C3=BCdtke <mail@danrl.com> =
wrote:
>> Hi Jason,
>>=20
>>> I guess I could provide IPv6 connectivity, but.... why? It's a demo.
>>=20
>> 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.
>=20
> I see what you mean. That's a fair point. We might as well give people
> an opportunity for trying things out, indeed.
>=20
> Currently the scripts on the server don't support that, so I'll have
> to write a small bit of code, but it shouldn't be too bad. I'll circle
> back in a few weeks.
>=20
> Jason

  reply	other threads:[~2016-11-16 14:49 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 [this message]
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=7FCCB728-BB7E-4A4F-ABAC-7D16FA6A1382@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).