From: nnet <nnet@fastmail.fm>
To: Jason Donenfeld <Jason@zx2c4.com>
Cc: wireguard@lists.zx2c4.com
Subject: [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
Date: Wed, 23 May 2018 16:57:05 -0700 [thread overview]
Message-ID: <1527119825.1012882.1382673952.168165E8@webmail.messagingengine.com> (raw)
Hi Jason,
Following up from IRC.=20
I've been looking for the WireGuard tunnel to move back to over WiFi from L=
TE with wireguard-android Play version 0.0.20180523 and Android 8.1 May 5th=
Android Security Patch level. Here's a log extract from what I see with it:
05-23 14:30:50.215 3081 3209 D ConnectivityService: NetworkAgentInfo [WIF=
I () - 115] EVENT_NETWORK_INFO_CHANGED, going from null to CONNECTING
05-23 14:30:51.378 3081 3209 D ConnectivityService: NetworkAgentInfo [WIF=
I () - 115] EVENT_NETWORK_INFO_CHANGED, going from CONNECTING to CONNECTED
05-23 14:30:51.649 3081 3209 D ConnectivityService: Switching to new defa=
ult network: NetworkAgentInfo{ ni{[type: WIFI[], ...
05-23 14:30:51.667 3081 3209 D ConnectivityService: Lingering NetworkAgen=
tInfo [MOBILE (LTE) - 114] for 30000ms
05-23 14:30:51.668 3081 3209 D ConnectivityService: Sending DISCONNECTED =
broadcast for type 0 NetworkAgentInfo [MOBILE (LTE) - 114] isDefaultNetwork=
=3Dtrue
05-23 14:30:51.669 3081 3209 D ConnectivityService: Sending CONNECTED bro=
adcast for type 1 NetworkAgentInfo [WIFI () - 115] isDefaultNetwork=3Dtrue
05-23 14:30:51.777 8674 9978 D WireGuard/GoBackend/wireguard: Failed to s=
end authenticated packet to peer peer(AsMM=E2=80=A6SeWg)
05-23 14:30:51.778 8674 9978 I chatty : uid=3D10104(com.wireguard.androi=
d) identical 1 line
05-23 14:30:51.778 8674 9978 D WireGuard/GoBackend/wireguard: Failed to s=
end authenticated packet to peer peer(AsMM=E2=80=A6SeWg)
...
It never recovers... I turn the tunnel off and back on to get a tunnel agai=
n.=20
I'm not having the same problem with (my own build) from tag 0.0.20180521. =
It doesn't 'roam' immediately as is expected with non-sticky sockets, it fl=
ows over WiFi it seems when the LTE interface is 'turned off' after a bit:
05-23 15:51:53.189 1088 1246 D ConnectivityService: registerNetworkAgent =
NetworkAgentInfo{ ni{[type: WIFI[], ...
05-23 15:51:53.189 1088 1254 D ConnectivityService: NetworkAgentInfo [WIF=
I () - 103] EVENT_NETWORK_INFO_CHANGED, going from null to CONNECTING
05-23 15:51:54.382 1088 1254 D ConnectivityService: NetworkAgentInfo [WIF=
I () - 103] EVENT_NETWORK_INFO_CHANGED, going from CONNECTING to CONNECTED
05-23 15:51:54.384 1088 1254 D ConnectivityService: Adding iface wlan0 to=
network 103
05-23 15:51:54.623 1088 1254 D ConnectivityService: NetworkAgentInfo [WIF=
I () - 103] validation passed
05-23 15:51:54.629 1088 1254 D ConnectivityService: Switching to new defa=
ult network: NetworkAgentInfo{ ni{[type: WIFI[] ...
05-23 15:51:54.663 1088 1254 D ConnectivityService: Lingering NetworkAgen=
tInfo [MOBILE (LTE) - 102] for 30000ms
05-23 15:51:54.670 1088 1254 D ConnectivityService: Sending DISCONNECTED =
broadcast for type 0 NetworkAgentInfo [MOBILE (LTE) - 102] isDefaultNetwork=
=3Dtrue
05-23 15:51:54.672 1088 1254 D ConnectivityService: Sending CONNECTED bro=
adcast for type 1 NetworkAgentInfo [WIFI () - 103] isDefaultNetwork=3Dtrue
05-23 15:52:08.924 2520 2595 D WireGuard/GoBackend/wireguard: peer(dJuC=
=E2=80=A61/Ws) - Sending handshake initiation
05-23 15:52:09.173 1088 2592 D ConnectivityService: ConnectivityService N=
etworkRequestInfo binderDied(NetworkRequest [ LISTEN id=3D29, [ Capabilitie=
s: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND] ], android.os.BinderProxy@ba=
e392b)
05-23 15:52:13.459 1088 1561 D ConnectivityService: ConnectivityService N=
etworkRequestInfo binderDied(NetworkRequest [ LISTEN id=3D28, [ Capabilitie=
s: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND] ], android.os.BinderProxy@5e=
c2cc4)
05-23 15:52:13.946 2520 5094 D WireGuard/GoBackend/wireguard: peer(dJuC=
=E2=80=A61/Ws) - Sending handshake initiation
05-23 15:52:19.248 2520 4976 D WireGuard/GoBackend/wireguard: peer(dJuC=
=E2=80=A61/Ws): Handshake did not complete after 5 seconds, retrying (try 2)
05-23 15:52:19.249 2520 4976 D WireGuard/GoBackend/wireguard: peer(dJuC=
=E2=80=A61/Ws) - Sending handshake initiation
05-23 15:52:19.289 2520 4972 D WireGuard/GoBackend/wireguard: peer(dJuC=
=E2=80=A61/Ws) - Received handshake response
05-23 15:52:19.289 2520 4972 D WireGuard/GoBackend/wireguard: peer(dJuC=
=E2=80=A61/Ws) - Sending keepalive packet
05-23 15:52:24.623 1088 1254 D ConnectivityService: handleLingerComplete =
for NetworkAgentInfo [MOBILE (LTE) - 102]
05-23 15:52:24.624 1088 1254 D ConnectivityService: NetworkAgentInfo [MOB=
ILE (LTE) - 102] got DISCONNECTED, was satisfying 11
Thoughts on what's holding things up on the first non-sticky socket version=
0.0.20180523? Perhaps the issue lies elsewhere?
I'd be curious to see someone your or someone else's logs of what happens w=
ith the latest 0.0.20180523 on going from LTE to WiFi.
Thanks!
next reply other threads:[~2018-05-23 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 23:57 nnet [this message]
2018-05-24 4:16 ` nnet
2018-05-24 13:57 ` Jörg Thalheim
2018-05-24 13:59 ` Jason A. Donenfeld
2018-05-24 14:01 ` Jason A. Donenfeld
2018-05-24 15:04 ` Jason A. Donenfeld
2018-05-24 15:10 ` Jason A. Donenfeld
2018-05-24 15:18 ` nnet
2018-05-24 18: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=1527119825.1012882.1382673952.168165E8@webmail.messagingengine.com \
--to=nnet@fastmail.fm \
--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).