From: Le Sandie <lesandie@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Handshake problem
Date: Mon, 8 May 2017 15:36:54 +0200 [thread overview]
Message-ID: <CAKgwHq_tXi16AyAt-_30WtD6pOuR4gTHVxJ-zBFLJMX8CDCEGg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
Hi all,
I'm new to the list and also the wireguard community. I like a lot the
simplicity and power of the kmod. Coming from OpenVPN and the performance
difference is great.
Just to report some issues i've been having with the last
commit 5f25c6520d75dac1163c8353b80ebe5fde648d70 (merge).
The handshake between my LEDE router with kmod-wireguard and my Rpi3 with
latest commit just broke. If i fall back to the latest snapshot 20170421
the handshake starts to work again and the peers can see each other. Also
i've tested the handshake with two peers with the last commit and they can
see each other perfectly.
I don't use a pre-shared key, so i gues the redesign in the las commit has
nothing to do. If i have some time i'll go deep into the code and test some
scenarios to feel where the problem is.
Best regards and thanks for your contribution!
Le,
[-- Attachment #2: Type: text/html, Size: 1097 bytes --]
next reply other threads:[~2017-05-08 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 13:36 Le Sandie [this message]
2017-05-08 14:00 ` 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=CAKgwHq_tXi16AyAt-_30WtD6pOuR4gTHVxJ-zBFLJMX8CDCEGg@mail.gmail.com \
--to=lesandie@gmail.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).