wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Rene 'Renne' Bartsch, B.Sc. Informatics" <ml@bartschnet.de>
To: wireguard@lists.zx2c4.com
Subject: Re: IPv6 endpoint AND IPv4 fallback endpoint in roadwarrior scenario?
Date: Sun, 29 Sep 2019 22:46:41 +0200	[thread overview]
Message-ID: <38ff6ee6-a78d-24d7-d338-48bc932ff4d0@bartschnet.de> (raw)
In-Reply-To: <CAOAVeL0e4JP+T6Z1353UPRmEXL84ZX5MSe+pjTO6xzzn9TB83A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1496 bytes --]

What happens if the DNS-lookup fails (e.g broken or manipulated DNS)?
In my opinion it should be possible to work with static IPv6 addresses 
and fall back to static IPv4 addresses.

Regards,

Renne


Am 29.09.19 um 21:31 schrieb Henning Reich:
> 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 <mailto: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 <mailto:WireGuard@lists.zx2c4.com>
>     > https://lists.zx2c4.com/mailman/listinfo/wireguard
>
>
>     _______________________________________________
>     WireGuard mailing list
>     WireGuard@lists.zx2c4.com <mailto: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

[-- Attachment #1.2: Type: text/html, Size: 3445 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-09-29 20:47 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 [this message]
2019-09-30  7:52     ` Nico Schottelius
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=38ff6ee6-a78d-24d7-d338-48bc932ff4d0@bartschnet.de \
    --to=ml@bartschnet.de \
    --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).