From: Jannis Pinter <jannis@pinterjann.is>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Compatibiliyt issues between 0.0.20170115 and 0.0.20170517
Date: Fri, 19 May 2017 09:26:54 +0800 [thread overview]
Message-ID: <b17e4f7a-9ecc-f674-26dd-f16f7c7afedc@pinterjann.is> (raw)
In-Reply-To: <CAHmME9osBYxRKFwSCroHcpORdCj8d8x1=WrE=6iR0DRofB=rAg@mail.gmail.com>
Am 19.05.2017 um 02:43 schrieb Jason A. Donenfeld:
> Only use 0.0.20170517.
Thanks! I hoped not up recompile and upgrade my routers firmware, since
I'm currently at the other side of the planet.
Also the new wireguard version is only available for the development
branch of LEDE. The stable branch still runs 0.0.20170115. I'll contact
the LEDE devs regarding that.
> i know we're in early days with wireguard, and there's no guarantee of
> protocol compatibility. but i wonder whether we should signal
> explicitly when there is an update that requires both sides to upgrade
> at the same time.
>From the user perspective, it would be nice if incompatible versions
were clearly signaled.
Regards,
Jannis
prev parent reply other threads:[~2017-05-19 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 4:35 Jannis Pinter
2017-05-18 18:43 ` Jason A. Donenfeld
2017-05-18 19:39 ` Daniel Kahn Gillmor
2017-05-18 20:04 ` Bruno Wolff III
2017-05-19 1:26 ` Jannis Pinter [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=b17e4f7a-9ecc-f674-26dd-f16f7c7afedc@pinterjann.is \
--to=jannis@pinterjann.is \
--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).