From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: 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 09:52:34 +0200 [thread overview]
Message-ID: <87eezyp6f1.fsf@line.ungleich.ch> (raw)
In-Reply-To: <CAOAVeL0e4JP+T6Z1353UPRmEXL84ZX5MSe+pjTO6xzzn9TB83A@mail.gmail.com>
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.
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?
>
> Ulrich Kalloch <ulli@noc23.de> schrieb am So., 29. Sep. 2019, 16:29:
>
>> Hello @ all
>>
>> i am interested in this too.
>>
>> Regards
>>
>> Ulli
>>
>> Am 27.05.19 um 20:10 schrieb Rene 'Renne' Bartsch, B.Sc. Informatics:
>> > Hi,
>> >
>> > is it meanwhile possible to define an IPv6 endpoint AND and an IPv4
>> > endpoint as fallback
>> > in case a road warrior does not get IPv6 connectivity when switching
>> > internet sockets?
>> >
>> > Regards,
>> >
>> > Renne
>> > _______________________________________________
>> > WireGuard mailing list
>> > WireGuard@lists.zx2c4.com
>> > https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
>>
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
--
Your Swiss, Open Source and IPv6 Virtual Machine. Now on www.datacenterlight.ch.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-09-30 7:52 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 [this message]
2019-09-30 8:44 ` Kalin KOZHUHAROV
2019-09-30 11:16 ` mikma.wg
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=87eezyp6f1.fsf@line.ungleich.ch \
--to=nico.schottelius@ungleich.ch \
--cc=henning.reich@gmail.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).