From: "René van Dorst" <opensource@vdorst.com>
To: wireguard@lists.zx2c4.com
Subject: Re: RX Errors from Android Peer
Date: Thu, 26 Apr 2018 08:59:10 +0000 [thread overview]
Message-ID: <20180426085910.Horde.lkBbsqDOKlkg-Ah-LZ5UFW4@www.vdorst.com> (raw)
In-Reply-To: <6e8c6b16-f131-6b45-9eee-f162a4f31099@attglobal.net>
Hi Eddie and Jason,
I seeing this too.
On the server: WireGuard 0.0.20180420-2-g802b85c (Mips32r2)
peer: bHFjNUyfx141TvuNXUyIQ2BDAF57zfcpgdRd09UOlSg=
endpoint: <ipv4>:22649
allowed ips: 10.0.0.8/32, fd00::8/128, <ipv6 prefix/48>:fff8::/64
latest handshake: 17 minutes, 41 seconds ago
transfer: 3.07 MiB received, 18.78 MiB sent
wg0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.0.0.1 P-t-P:10.0.0.1 Mask:255.255.255.0
inet6 addr: fd00::1/64 Scope:Global
inet6 addr: <ipv6 prefix/48>:fff0::/60 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1440 Metric:1
RX packets:23629 errors:215 dropped:0 overruns:0 frame:215
TX packets:23885 errors:6 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3224980 (3.0 MiB) TX bytes:19693516 (18.7 MiB)
Latest Android client 0.4.0 on a Backberry DTEK50 android 6.0.1. So
fallback on userspace implementation.
Address: 10.0.0.8/32, <ipv6 prefix/48>:fff8::1/64
dns: 8.8.8.8
Allowed IPS: ::/0, 0.0.0.0/0
MTU: auto.
Before test
wg0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.0.0.1 P-t-P:10.0.0.1 Mask:255.255.255.0
inet6 addr: fd00::1/64 Scope:Global
inet6 addr: <ipv6 prefix/48>:fff0::/60 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1440 Metric:1
RX packets:23714 errors:215 dropped:0 overruns:0 frame:215
TX packets:23996 errors:6 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3239760 (3.0 MiB) TX bytes:19715932 (18.8 MiB)
dmesg:
wireguard: wg0: Sending handshake initiation to peer 6 (85d26a64)
wireguard: wg0: Receiving handshake initiation from peer 6 (85d26a64)
wireguard: wg0: Sending handshake response to peer 6 (85d26a64)
wireguard: wg0: Keypair 93 created for peer 6
wireguard: wg0: Keypair 91 destroyed for peer 6
wireguard: wg0: Receiving keepalive packet from peer 6 (85d26a64)
wireguard: wg0: Packet has unallowed src IP (8cd8bd50) from peer 6 (85d26a64)
wireguard: wg0: Receiving keepalive packet from peer 6 (85d26a64)
wireguard: wg0: Receiving keepalive packet from peer 6 (85d26a64)
wireguard: wg0: Receiving keepalive packet from peer 6 (85d26a64)
wireguard: wg0: Receiving handshake initiation from peer 6 (85d26a64)
wireguard: wg0: Sending handshake response to peer 6 (85d26a64)
wireguard: wg0: Keypair 94 created for peer 6
wireguard: wg0: Keypair 92 destroyed for peer 6
wireguard: wg0: Receiving keepalive packet from peer 6 (85d26a64)
wireguard: wg0: Retrying handshake with peer 6 (85d26a64) because we
stopped hearing back after 15 seconds
wireguard: wg0: Sending handshake initiation to peer 6 (85d26a64)
wireguard: wg0: Receiving handshake response from peer 6 (85d26a64)
After test:
wg0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.0.0.1 P-t-P:10.0.0.1 Mask:255.255.255.0
inet6 addr: fd00::1/64 Scope:Global
inet6 addr: <ipv6 prefix/48>:fff0::/60 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1440 Metric:1
RX packets:26810 errors:216 dropped:0 overruns:0 frame:216
TX packets:26866 errors:6 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3674552 (3.5 MiB) TX bytes:21719820 (20.7 MiB)
Tunnel is working: test-ipv6.nl shows both my ISP ipv4 and ipv6 address.
Greats,
René van Dorst.
next prev parent reply other threads:[~2018-04-26 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 20:14 Eddie
2018-04-25 21:18 ` Jason A. Donenfeld
2018-04-25 22:28 ` Eddie
2018-04-26 8:59 ` René van Dorst [this message]
2018-04-26 13:04 ` Jason A. Donenfeld
2018-04-26 16:09 ` Eddie
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=20180426085910.Horde.lkBbsqDOKlkg-Ah-LZ5UFW4@www.vdorst.com \
--to=opensource@vdorst.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).