From: Riccardo Berto <riccardo@rcrdbrt.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Troubleshooting WireGuard connections
Date: Fri, 20 Apr 2018 15:57:02 +0200 [thread overview]
Message-ID: <f541248bfc8b47975b34acbc1c7bfa9b@rcrdbrt.com> (raw)
In-Reply-To: <9896807f0c6cbee1c7c99647a3c289cc@rcrdbrt.com>
Sorry for the late answer, I've been busy with exams this week.
I updated WireGuard to the latest snapshot 20180420 on both server and
peers.
I use unique key pairs for every host and I'm using the right
privkey/pubkey combo, I just checked manually via the `wg pubkey`
command.
I also tried removing all the peers but one Raspberry Pi, I'm still
getting this weird output on the server from `tcpdump -vv -ni ens3 'port
51820'`:
15:45:49.138470 IP (tos 0x0, ttl 52, id 27235, offset 0, flags [none],
proto UDP (17), length 176)
raspberry-ip.51820 > server-ip.51820: [udp sum ok] UDP, length 148
15:45:49.138883 IP (tos 0x88, ttl 64, id 2728, offset 0, flags [none],
proto UDP (17), length 120)
server-ip.51820 > raspberry-ip.51820: [bad udp cksum 0x92e3 ->
0x0eae!] UDP, length 92
15:46:05.778398 IP (tos 0x0, ttl 52, id 27850, offset 0, flags [none],
proto UDP (17), length 176)
raspberry-ip.51820 > server-ip.51820: [udp sum ok] UDP, length 148
15:46:05.778890 IP (tos 0x88, ttl 64, id 5807, offset 0, flags [none],
proto UDP (17), length 120)
server-ip.51820 > raspberry-ip.51820: [bad udp cksum 0x92e3 ->
0x85d0!] UDP, length 92
15:46:22.419043 IP (tos 0x0, ttl 52, id 28761, offset 0, flags [none],
proto UDP (17), length 176)
raspberry-ip.51820 > server-ip.51820: [udp sum ok] UDP, length 148
15:46:22.419748 IP (tos 0x88, ttl 64, id 8596, offset 0, flags [none],
proto UDP (17), length 120)
server-ip.51820 > raspberry-ip.51820: [bad udp cksum 0x92e3 ->
0x6d8c!] UDP, length 92
Removing everything and simply adding the "always working" peer (my
laptop) in the server config makes it working perfectly fine.
next prev parent reply other threads:[~2018-04-20 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 9:23 Riccardo Berto
2018-04-13 21:54 ` Jason A. Donenfeld
[not found] ` <33d0fd1f4c60919b98b50e2b9d04fe78@rcrdbrt.com>
2018-04-13 22:36 ` Riccardo Berto
2018-04-14 1:26 ` Jason A. Donenfeld
2018-04-14 7:56 ` Riccardo Berto
2018-04-14 23:19 ` Jason A. Donenfeld
2018-04-20 13:57 ` Riccardo Berto [this message]
2018-04-20 19:37 ` Jason A. Donenfeld
2018-04-20 19:39 ` Jason A. Donenfeld
2018-04-20 19:51 ` Jason A. Donenfeld
2018-04-20 20:31 ` Riccardo Berto
2018-04-25 11:46 ` Riccardo Berto
2018-04-25 11:51 ` Jason A. Donenfeld
2018-04-25 12:40 ` logcabin
2018-04-25 22:56 ` Riccardo Berto
2018-04-26 9:52 ` Riccardo Berto
-- strict thread matches above, loose matches on Subject: below --
2018-04-12 9:09 Riccardo Berto
2018-04-12 20:57 ` Eric Light
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=f541248bfc8b47975b34acbc1c7bfa9b@rcrdbrt.com \
--to=riccardo@rcrdbrt.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).