[wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523

nnet nnet at fastmail.fm
Thu May 24 06:16:07 CEST 2018


> It never recovers... I turn the tunnel off and back on to get a tunnel again. 

So this is how it ends:

05-23 20:33:45.323  9600  9619 D WireGuard/GoBackend/wireguard: peer(AsMM…SeWg) - Sending handshake initiation                                    
05-23 20:33:45.326  9600  9619 E WireGuard/GoBackend/wireguard: peer(AsMM…SeWg) - Failed to send handshake initiation write udp6 [::]:46719->[]:41414: sendto: network is unreachable                                                                                      
05-23 20:33:45.326  9600  9619 D WireGuard/GoBackend/wireguard: peer(AsMM…SeWg) - Awaiting keypair                                                
05-23 20:33:50.367  9600  9678 D WireGuard/GoBackend/wireguard: peer(AsMM…SeWg) - Sending handshake initiation                                    
05-23 20:33:50.376  9600  9678 E WireGuard/GoBackend/wireguard: peer(AsMM…SeWg) - Failed to send handshake initiation write udp6 [::]:46719->[snip]:41414: sendto: network is unreachable
05-23 20:36:10.188  9600 11291 D WireGuard/GoBackend/wireguard: peer(AsMM…SeWg): Handshake did not complete after 20 attempts, giving up
05-23 20:39:12.258  9600  9677 D WireGuard/GoBackend/wireguard: :peer(AsMM…SeWg) Removing all keys, since we haven't received a new one in 540 seconds

Interestingly it's trying to send out to an IPv6 address. The peer endpoint IP is IPv4 only (the LTE is IPv4-in-6).

On Wed, May 23, 2018, at 4:57 PM, nnet wrote:
> Hi Jason,
> 
> Following up from IRC. 
> 
> I've been looking for the WireGuard tunnel to move back to over WiFi 
> from LTE 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 
> [WIFI () - 115] EVENT_NETWORK_INFO_CHANGED, going from null to 
> CONNECTING
> 05-23 14:30:51.378  3081  3209 D ConnectivityService: NetworkAgentInfo 
> [WIFI () - 115] EVENT_NETWORK_INFO_CHANGED, going from CONNECTING to 
> CONNECTED
> 05-23 14:30:51.649  3081  3209 D ConnectivityService: Switching to new 
> default network: NetworkAgentInfo{ ni{[type: WIFI[], ...
> 05-23 14:30:51.667  3081  3209 D ConnectivityService: Lingering 
> NetworkAgentInfo [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=true
> 05-23 14:30:51.669  3081  3209 D ConnectivityService: Sending CONNECTED 
> broadcast for type 1 NetworkAgentInfo [WIFI () - 115] 
> isDefaultNetwork=true
> 05-23 14:30:51.777  8674  9978 D WireGuard/GoBackend/wireguard: Failed 
> to send authenticated packet to peer peer(AsMM…SeWg)
> 05-23 14:30:51.778  8674  9978 I chatty  : 
> uid=10104(com.wireguard.android) identical 1 line
> 05-23 14:30:51.778  8674  9978 D WireGuard/GoBackend/wireguard: Failed 
> to send authenticated packet to peer peer(AsMM…SeWg)
> ...
> 
> It never recovers... I turn the tunnel off and back on to get a tunnel again. 
> 
> 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 flows 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 
> [WIFI () - 103] EVENT_NETWORK_INFO_CHANGED, going from null to 
> CONNECTING
> 05-23 15:51:54.382  1088  1254 D ConnectivityService: NetworkAgentInfo 
> [WIFI () - 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 
> [WIFI () - 103] validation passed
> 05-23 15:51:54.629  1088  1254 D ConnectivityService: Switching to new 
> default network: NetworkAgentInfo{ ni{[type: WIFI[] ...
> 05-23 15:51:54.663  1088  1254 D ConnectivityService: Lingering 
> NetworkAgentInfo [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=true
> 05-23 15:51:54.672  1088  1254 D ConnectivityService: Sending CONNECTED 
> broadcast for type 1 NetworkAgentInfo [WIFI () - 103] 
> isDefaultNetwork=true
> 05-23 15:52:08.924  2520  2595 D WireGuard/GoBackend/wireguard: 
> peer(dJuC…1/Ws) - Sending handshake initiation
> 05-23 15:52:09.173  1088  2592 D ConnectivityService: 
> ConnectivityService NetworkRequestInfo binderDied(NetworkRequest 
> [ LISTEN id=29, [ Capabilities: 
> INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND] ], 
> android.os.BinderProxy at bae392b)
> 05-23 15:52:13.459  1088  1561 D ConnectivityService: 
> ConnectivityService NetworkRequestInfo binderDied(NetworkRequest 
> [ LISTEN id=28, [ Capabilities: 
> INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND] ], 
> android.os.BinderProxy at 5ec2cc4)
> 05-23 15:52:13.946  2520  5094 D WireGuard/GoBackend/wireguard: 
> peer(dJuC…1/Ws) - Sending handshake initiation
> 05-23 15:52:19.248  2520  4976 D WireGuard/GoBackend/wireguard: 
> peer(dJuC…1/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…1/Ws) - Sending handshake initiation
> 05-23 15:52:19.289  2520  4972 D WireGuard/GoBackend/wireguard: 
> peer(dJuC…1/Ws) - Received handshake response
> 05-23 15:52:19.289  2520  4972 D WireGuard/GoBackend/wireguard: 
> peer(dJuC…1/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 
> [MOBILE (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 with the latest 0.0.20180523 on going from LTE to WiFi.
> 
> Thanks!
> 
> _______________________________________________
> WireGuard mailing list
> WireGuard at lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard


More information about the WireGuard mailing list