From: Jannis Pinter <jannis@pinterjann.is>
To: wireguard@lists.zx2c4.com
Subject: Compatibiliyt issues between 0.0.20170115 and 0.0.20170517
Date: Thu, 18 May 2017 12:35:20 +0800 [thread overview]
Message-ID: <16c492cb-af24-e864-cd49-c8c2c5457ee4@pinterjann.is> (raw)
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
next reply other threads:[~2017-05-18 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 4:35 Jannis Pinter [this message]
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
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=16c492cb-af24-e864-cd49-c8c2c5457ee4@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).