wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jörg Thalheim" <joerg@higgsboson.tk>
To: wireguard@lists.zx2c4.com
Subject: Re: [wireguard-android] 'roaming' from LTE to WiFi with version 0.0.20180523
Date: Thu, 24 May 2018 14:57:18 +0100	[thread overview]
Message-ID: <f40f4b86-90a6-ff2c-4d17-7d2a278c201b@higgsboson.tk> (raw)
In-Reply-To: <1527135367.1083058.1382934352.4E96D38A@webmail.messagingengine.com>



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.

  reply	other threads:[~2018-05-24 13:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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=f40f4b86-90a6-ff2c-4d17-7d2a278c201b@higgsboson.tk \
    --to=joerg@higgsboson.tk \
    --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).