From: mikma.wg@lists.m7n.se
To: Nico Schottelius <nico.schottelius@ungleich.ch>,
Henning Reich <henning.reich@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: IPv6 endpoint AND IPv4 fallback endpoint in roadwarrior scenario?
Date: Mon, 30 Sep 2019 13:16:30 +0200 [thread overview]
Message-ID: <079444e4-2d89-92d9-f3b3-245a073bb190@m7n.se> (raw)
In-Reply-To: <87eezyp6f1.fsf@line.ungleich.ch>
On 2019-09-30 09:52, Nico Schottelius wrote:
>
> At lookup time this works already. The problem is, if the underlying
> network topology changes and you need to reconnect via IPv4, when you
> had IPv6 underlying before.
It doesn't work for me at least not with the Android app. I have a DNS
name with both AAAA and A records that I use but the app seems to prefer
IPv4 instead of IPv6. And I also can't detect any fallback to IPv6 if
ICMP unreachable are sent for the IPv4 handshake attempts.
/Mikma
>
> This is the feature that is - afaik- not currently implemented in
> wireguard.
>
>
> Henning Reich <henning.reich@gmail.com> writes:
>
>> Should a DNS entry Wirth one
>> AAAA record and one A record solve thus problem? So the OS decide the best
>> way to connect?
>>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-11-27 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 18:10 IPv6 endpoint AND IPv4 fallback endpoint in roadwarrior scenario? Rene 'Renne' Bartsch, B.Sc. Informatics
2019-09-29 14:27 ` Ulrich Kalloch
2019-09-29 19:31 ` Henning Reich
2019-09-29 20:46 ` Rene 'Renne' Bartsch, B.Sc. Informatics
2019-09-30 7:52 ` Nico Schottelius
2019-09-30 8:44 ` Kalin KOZHUHAROV
2019-09-30 11:16 ` mikma.wg [this message]
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=079444e4-2d89-92d9-f3b3-245a073bb190@m7n.se \
--to=mikma.wg@lists.m7n.se \
--cc=henning.reich@gmail.com \
--cc=nico.schottelius@ungleich.ch \
--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).