Compatibiliyt issues between 0.0.20170115 and 0.0.20170517

Compatibiliyt issues between 0.0.20170115 and 0.0.20170517

[Jannis Pinter]

Hi list,

I use wireguard to connect to my remote LEDE routers which works great
and is really fast. This morning I've upgraded my Arch Linux laptop to
the latest wireguard version and noticed that I can no longer connect to
my routers.

It looks like the handshake between the two devices does not complete. I
can see that my laptop sends UDP packets every 5 seconds to the router,
but the router never sends a packet back.

Downgrading wireguard on my laptop to the previous version 0.0.20170421
solves the issue.

Software versions on LEDE router:
OS: 		LEDE 17.01
Kernel: 	4.4.59
Wireguard:	0.0.20170115

Software versions on my Arch Linux laptop:
OS:		Arch Linux
Kernel:		4.10.13
Wireguard:	0.0.20170517

Now this description is not very detailed, is there anything I could do
to provice more useful debugging output?

Regards,
Jannis

Re: Compatibiliyt issues between 0.0.20170115 and 0.0.20170517

[Jason A. Donenfeld]

Hello Jannis,

Only use 0.0.20170517.

Regards,
Jason

Re: Compatibiliyt issues between 0.0.20170115 and 0.0.20170517

[Daniel Kahn Gillmor]

On Thu 2017-05-18 20:43:11 +0200, Jason A. Donenfeld wrote:

> Only use 0.0.20170517.

i think this was the first incompatible revision that has been released.
is that correct?

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.  Should i have put it in the NEWS file in the debian
package, for example?  Or are there other forms of signalling that we
should use to communicate this better?

         --dkg

Re: Compatibiliyt issues between 0.0.20170115 and 0.0.20170517

[Bruno Wolff III]

On Thu, May 18, 2017 at 15:39:48 -0400,
  Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
>On Thu 2017-05-18 20:43:11 +0200, Jason A. Donenfeld wrote:
>
>> Only use 0.0.20170517.
>
>i think this was the first incompatible revision that has been released.
>is that correct?

No. There have been a few incompatible upgrades. I usually upgrade both 
ends at the same time, but I want to start using the LEDE version and 
once I do, I'll need to be more careful.

Re: Compatibiliyt issues between 0.0.20170115 and 0.0.20170517

[Jannis Pinter]

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