* [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
@ 2018-05-23 23:57 nnet
2018-05-24 4:16 ` nnet
2018-05-24 18:00 ` Jason A. Donenfeld
0 siblings, 2 replies; 9+ messages in thread
From: nnet @ 2018-05-23 23:57 UTC (permalink / raw)
To: Jason Donenfeld; +Cc: wireguard
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!
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
2018-05-23 23:57 [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523 nnet
@ 2018-05-24 4:16 ` nnet
2018-05-24 13:57 ` Jörg Thalheim
2018-05-24 14:01 ` Jason A. Donenfeld
2018-05-24 18:00 ` Jason A. Donenfeld
1 sibling, 2 replies; 9+ messages in thread
From: nnet @ 2018-05-24 4:16 UTC (permalink / raw)
To: wireguard
> It never recovers... I turn the tunnel off and back on to get a tunnel ag=
ain.=20
So this is how it ends:
05-23 20:33:45.323 9600 9619 D WireGuard/GoBackend/wireguard: peer(AsMM=
=E2=80=A6SeWg) - Sending handshake initiation=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
05-23 20:33:45.326 9600 9619 E WireGuard/GoBackend/wireguard: peer(AsMM=
=E2=80=A6SeWg) - Failed to send handshake initiation write udp6 [::]:46719-=
>[]:41414: sendto: network is unreachable=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
05-23 20:33:45.326 9600 9619 D WireGuard/GoBackend/wireguard: peer(AsMM=
=E2=80=A6SeWg) - Awaiting keypair=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20
05-23 20:33:50.367 9600 9678 D WireGuard/GoBackend/wireguard: peer(AsMM=
=E2=80=A6SeWg) - Sending handshake initiation=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
05-23 20:33:50.376 9600 9678 E WireGuard/GoBackend/wireguard: peer(AsMM=
=E2=80=A6SeWg) - 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=
=E2=80=A6SeWg): Handshake did not complete after 20 attempts, giving up
05-23 20:39:12.258 9600 9677 D WireGuard/GoBackend/wireguard: :peer(AsMM=
=E2=80=A6SeWg) Removing all keys, since we haven't received a new one in 54=
0 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,
>=20
> Following up from IRC.=20
>=20
> I've been looking for the WireGuard tunnel to move back to over WiFi=20
> from LTE with wireguard-android Play version 0.0.20180523 and Android=20
> 8.1 May 5th Android Security Patch level. Here's a log extract from what=
=20
> I see with it:
>=20
> 05-23 14:30:50.215 3081 3209 D ConnectivityService: NetworkAgentInfo=20
> [WIFI () - 115] EVENT_NETWORK_INFO_CHANGED, going from null to=20
> CONNECTING
> 05-23 14:30:51.378 3081 3209 D ConnectivityService: NetworkAgentInfo=20
> [WIFI () - 115] EVENT_NETWORK_INFO_CHANGED, going from CONNECTING to=20
> CONNECTED
> 05-23 14:30:51.649 3081 3209 D ConnectivityService: Switching to new=20
> default network: NetworkAgentInfo{ ni{[type: WIFI[], ...
> 05-23 14:30:51.667 3081 3209 D ConnectivityService: Lingering=20
> NetworkAgentInfo [MOBILE (LTE) - 114] for 30000ms
> 05-23 14:30:51.668 3081 3209 D ConnectivityService: Sending=20
> DISCONNECTED broadcast for type 0 NetworkAgentInfo [MOBILE (LTE) - 114]=20
> isDefaultNetwork=3Dtrue
> 05-23 14:30:51.669 3081 3209 D ConnectivityService: Sending CONNECTED=20
> broadcast for type 1 NetworkAgentInfo [WIFI () - 115]=20
> isDefaultNetwork=3Dtrue
> 05-23 14:30:51.777 8674 9978 D WireGuard/GoBackend/wireguard: Failed=20
> to send authenticated packet to peer peer(AsMM=E2=80=A6SeWg)
> 05-23 14:30:51.778 8674 9978 I chatty :=20
> uid=3D10104(com.wireguard.android) identical 1 line
> 05-23 14:30:51.778 8674 9978 D WireGuard/GoBackend/wireguard: Failed=20
> to send authenticated packet to peer peer(AsMM=E2=80=A6SeWg)
> ...
>=20
> It never recovers... I turn the tunnel off and back on to get a tunnel ag=
ain.=20
>=20
> I'm not having the same problem with (my own build) from tag=20
> 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=20
> 'turned off' after a bit:
>=20
> 05-23 15:51:53.189 1088 1246 D ConnectivityService:=20
> registerNetworkAgent NetworkAgentInfo{ ni{[type: WIFI[], ...
> 05-23 15:51:53.189 1088 1254 D ConnectivityService: NetworkAgentInfo=20
> [WIFI () - 103] EVENT_NETWORK_INFO_CHANGED, going from null to=20
> CONNECTING
> 05-23 15:51:54.382 1088 1254 D ConnectivityService: NetworkAgentInfo=20
> [WIFI () - 103] EVENT_NETWORK_INFO_CHANGED, going from CONNECTING to=20
> CONNECTED
> 05-23 15:51:54.384 1088 1254 D ConnectivityService: Adding iface wlan0=
=20
> to network 103
> 05-23 15:51:54.623 1088 1254 D ConnectivityService: NetworkAgentInfo=20
> [WIFI () - 103] validation passed
> 05-23 15:51:54.629 1088 1254 D ConnectivityService: Switching to new=20
> default network: NetworkAgentInfo{ ni{[type: WIFI[] ...
> 05-23 15:51:54.663 1088 1254 D ConnectivityService: Lingering=20
> NetworkAgentInfo [MOBILE (LTE) - 102] for 30000ms
> 05-23 15:51:54.670 1088 1254 D ConnectivityService: Sending=20
> DISCONNECTED broadcast for type 0 NetworkAgentInfo [MOBILE (LTE) - 102]=20
> isDefaultNetwork=3Dtrue
> 05-23 15:51:54.672 1088 1254 D ConnectivityService: Sending CONNECTED=20
> broadcast for type 1 NetworkAgentInfo [WIFI () - 103]=20
> isDefaultNetwork=3Dtrue
> 05-23 15:52:08.924 2520 2595 D WireGuard/GoBackend/wireguard:=20
> peer(dJuC=E2=80=A61/Ws) - Sending handshake initiation
> 05-23 15:52:09.173 1088 2592 D ConnectivityService:=20
> ConnectivityService NetworkRequestInfo binderDied(NetworkRequest=20
> [ LISTEN id=3D29, [ Capabilities:=20
> INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND] ],=20
> android.os.BinderProxy@bae392b)
> 05-23 15:52:13.459 1088 1561 D ConnectivityService:=20
> ConnectivityService NetworkRequestInfo binderDied(NetworkRequest=20
> [ LISTEN id=3D28, [ Capabilities:=20
> INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND] ],=20
> android.os.BinderProxy@5ec2cc4)
> 05-23 15:52:13.946 2520 5094 D WireGuard/GoBackend/wireguard:=20
> peer(dJuC=E2=80=A61/Ws) - Sending handshake initiation
> 05-23 15:52:19.248 2520 4976 D WireGuard/GoBackend/wireguard:=20
> peer(dJuC=E2=80=A61/Ws): Handshake did not complete after 5 seconds, retr=
ying=20
> (try 2)
> 05-23 15:52:19.249 2520 4976 D WireGuard/GoBackend/wireguard:=20
> peer(dJuC=E2=80=A61/Ws) - Sending handshake initiation
> 05-23 15:52:19.289 2520 4972 D WireGuard/GoBackend/wireguard:=20
> peer(dJuC=E2=80=A61/Ws) - Received handshake response
> 05-23 15:52:19.289 2520 4972 D WireGuard/GoBackend/wireguard:=20
> peer(dJuC=E2=80=A61/Ws) - Sending keepalive packet
> 05-23 15:52:24.623 1088 1254 D ConnectivityService:=20
> handleLingerComplete for NetworkAgentInfo [MOBILE (LTE) - 102]
> 05-23 15:52:24.624 1088 1254 D ConnectivityService: NetworkAgentInfo=20
> [MOBILE (LTE) - 102] got DISCONNECTED, was satisfying 11
>=20
> Thoughts on what's holding things up on the first non-sticky socket=20
> version 0.0.20180523? Perhaps the issue lies elsewhere?
>=20
> I'd be curious to see someone your or someone else's logs of what=20
> happens with the latest 0.0.20180523 on going from LTE to WiFi.
>=20
> Thanks!
>=20
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
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
1 sibling, 1 reply; 9+ messages in thread
From: Jörg Thalheim @ 2018-05-24 13:57 UTC (permalink / raw)
To: wireguard
On 2018-05-24 05:16, nnet wrote:
> 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).
In the wg command it resolves the domain once and picks the preferred protocol family of the system (which is ipv6 when its available).
Since this is only done once it will stick to ipv6 for ever until the VPN is reconfigured by wg.
This is an unsolved known problem.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
2018-05-24 13:57 ` Jörg Thalheim
@ 2018-05-24 13:59 ` Jason A. Donenfeld
0 siblings, 0 replies; 9+ messages in thread
From: Jason A. Donenfeld @ 2018-05-24 13:59 UTC (permalink / raw)
To: Jörg Thalheim; +Cc: WireGuard mailing list
On Thu, May 24, 2018 at 3:57 PM, J=C3=B6rg Thalheim <joerg@higgsboson.tk> w=
rote:
>
>
> On 2018-05-24 05:16, nnet wrote:
>> So this is how it ends:
>>
>> 05-23 20:33:45.323 9600 9619 D WireGuard/GoBackend/wireguard: peer(AsM=
M=E2=80=A6SeWg) - Sending handshake initiation
>> 05-23 20:33:45.326 9600 9619 E WireGuard/GoBackend/wireguard: peer(AsM=
M=E2=80=A6SeWg) - 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(AsM=
M=E2=80=A6SeWg) - Awaiting keypair
>> 05-23 20:33:50.367 9600 9678 D WireGuard/GoBackend/wireguard: peer(AsM=
M=E2=80=A6SeWg) - Sending handshake initiation
>> 05-23 20:33:50.376 9600 9678 E WireGuard/GoBackend/wireguard: peer(AsM=
M=E2=80=A6SeWg) - 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(AsM=
M=E2=80=A6SeWg): Handshake did not complete after 20 attempts, giving up
>> 05-23 20:39:12.258 9600 9677 D WireGuard/GoBackend/wireguard: :peer(As=
MM=E2=80=A6SeWg) 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 endpo=
int IP is IPv4 only (the LTE is IPv4-in-6).
>
> In the wg command it resolves the domain once and picks the preferred pro=
tocol family of the system (which is ipv6 when its available).
> Since this is only done once it will stick to ipv6 for ever until the VPN=
is reconfigured by wg.
> This is an unsolved known problem.
That's *not* what's going on here. This is an issue with how Go
sockets handle IP addresses and their preference for v4-mapped-v6.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
2018-05-24 4:16 ` nnet
2018-05-24 13:57 ` Jörg Thalheim
@ 2018-05-24 14:01 ` Jason A. Donenfeld
2018-05-24 15:04 ` Jason A. Donenfeld
1 sibling, 1 reply; 9+ messages in thread
From: Jason A. Donenfeld @ 2018-05-24 14:01 UTC (permalink / raw)
To: nnet; +Cc: WireGuard mailing list
Hey Nnet,
On Thu, May 24, 2018 at 6:16 AM, nnet <nnet@fastmail.fm> wrote:
> Interestingly it's trying to send out to an IPv6 address. The peer endpoint IP is IPv4 only (the LTE is IPv4-in-6).
Great observation. I thought I had tried to squash those bugs, but
there may in fact be work still to do. You snipped the IP from the
log, so that makes it harder for me to be confident in this hunch, but
could you confirm something for me? Did those IPs begin with
"::ffff:[somethingelse]"?
Thanks,
Jason
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
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
0 siblings, 2 replies; 9+ messages in thread
From: Jason A. Donenfeld @ 2018-05-24 15:04 UTC (permalink / raw)
To: nnet; +Cc: WireGuard mailing list
It would appear that T-Mobile is using 464XLAT and Android runs
https://github.com/toreanderson/clatd
Can you confirm this suspicion by sending the output of `ip addr show`
and `ps|grep clat`?
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
2018-05-24 15:04 ` Jason A. Donenfeld
@ 2018-05-24 15:10 ` Jason A. Donenfeld
2018-05-24 15:18 ` nnet
1 sibling, 0 replies; 9+ messages in thread
From: Jason A. Donenfeld @ 2018-05-24 15:10 UTC (permalink / raw)
To: nnet; +Cc: WireGuard mailing list
On Thu, May 24, 2018 at 5:04 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> It would appear that T-Mobile is using 464XLAT and Android runs
> https://github.com/toreanderson/clatd
Rather, this: https://android.googlesource.com/platform/external/android-clat/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
2018-05-24 15:04 ` Jason A. Donenfeld
2018-05-24 15:10 ` Jason A. Donenfeld
@ 2018-05-24 15:18 ` nnet
1 sibling, 0 replies; 9+ messages in thread
From: nnet @ 2018-05-24 15:18 UTC (permalink / raw)
To: wireguard
> It would appear that T-Mobile is using 464XLAT ...
Yes, from what I've seen and read.
> ... and Android runs
> https://github.com/toreanderson/clatd
...
> Can you confirm this suspicion by sending the output of `ip addr show`
> and `ps|grep clat`?
Below follows. Although DHCP is giving IPv4 only on WiFi there is a link local IPv6 address.
$ ps|grep clat
1
$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
link/ether snipmac brd ff:ff:ff:ff:ff:ff
inet6 snipinet6 scope link
valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN group default
link/sit 0.0.0.0 brd 0.0.0.0
4: rmnet_ipa0: <UP,LOWER_UP> mtu 2000 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/[530]
5: rmnet_data0: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
6: rmnet_data1: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
7: rmnet_data2: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
8: rmnet_data3: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
9: rmnet_data4: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
10: rmnet_data5: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
11: rmnet_data6: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
12: rmnet_data7: <UP,LOWER_UP> mtu 1500 qdisc htb state UNKNOWN group default qlen 1000
link/[530]
inet6 snipinet6/64 scope global dynamic
valid_lft forever preferred_lft forever
inet6 snipinet6/64 scope link
valid_lft forever preferred_lft forever
13: r_rmnet_data0: <UP,LOWER_UP> mtu 3000 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/[530]
inet6 snipinet6/64 scope link
valid_lft forever preferred_lft forever
14: r_rmnet_data1: <> mtu 3000 qdisc noop state DOWN group default qlen 1000
link/[530]
15: r_rmnet_data2: <> mtu 3000 qdisc noop state DOWN group default qlen 1000
link/[530]
16: r_rmnet_data3: <> mtu 3000 qdisc noop state DOWN group default qlen 1000
link/[530]
17: r_rmnet_data4: <> mtu 3000 qdisc noop state DOWN group default qlen 1000
link/[530]
18: r_rmnet_data5: <> mtu 3000 qdisc noop state DOWN group default qlen 1000
link/[530]
19: r_rmnet_data6: <> mtu 3000 qdisc noop state DOWN group default qlen 1000
link/[530]
20: r_rmnet_data7: <> mtu 3000 qdisc noop state DOWN group default qlen 1000
link/[530]
21: r_rmnet_data8: <> mtu 3000 qdisc noop state DOWN group default qlen 1000
link/[530]
25: tun0: <POINTOPOINT,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500
link/none
inet snipinet/32 scope global tun0
valid_lft forever preferred_lft forever
32: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 3000
link/ether snipmac brd ff:ff:ff:ff:ff:ff
inet snipinet/24 brd snipinet scope global wlan0
valid_lft forever preferred_lft forever
inet6 snipinet6/64 scope link
valid_lft forever preferred_lft forever
33: p2p0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 3000
link/ether snipmac brd ff:ff:ff:ff:ff:ff
On Thu, May 24, 2018, at 8:04 AM, Jason A. Donenfeld wrote:
> It would appear that T-Mobile is using 464XLAT and Android runs
> https://github.com/toreanderson/clatd
>
> Can you confirm this suspicion by sending the output of `ip addr show`
> and `ps|grep clat`?
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
2018-05-23 23:57 [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523 nnet
2018-05-24 4:16 ` nnet
@ 2018-05-24 18:00 ` Jason A. Donenfeld
1 sibling, 0 replies; 9+ messages in thread
From: Jason A. Donenfeld @ 2018-05-24 18:00 UTC (permalink / raw)
To: nnet; +Cc: WireGuard mailing list
Looks like we've resolved this with 0.0.20180524. Thanks for your
useful logs and debugging.
Jason
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2018-05-24 17:59 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-23 23:57 [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523 nnet
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
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).