WireGuard Archive on lore.kernel.org
 help / color / 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
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 --]

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    What happens if the DNS-lookup fails (e.g broken or manipulated
    DNS)?<br>
    In my opinion it should be possible to work with static IPv6
    addresses and fall back to static IPv4 addresses.<br>
    <br>
    Regards,<br>
    <br>
    Renne
    <p><br>
    </p>
    <div class="moz-cite-prefix">Am 29.09.19 um 21:31 schrieb Henning
      Reich:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOAVeL0e4JP+T6Z1353UPRmEXL84ZX5MSe+pjTO6xzzn9TB83A@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">Should a DNS entry Wirth one
        <div dir="auto">AAAA record and one A record solve thus problem?
          So the OS decide the best way to connect?</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">Ulrich Kalloch &lt;<a
            href="mailto:ulli@noc23.de" moz-do-not-send="true">ulli@noc23.de</a>&gt;
          schrieb am So., 29. Sep. 2019, 16:29:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello @ all<br>
          <br>
          i am interested in this too.<br>
          <br>
          Regards<br>
          <br>
          Ulli<br>
          <br>
          Am 27.05.19 um 20:10 schrieb Rene 'Renne' Bartsch, B.Sc.
          Informatics:<br>
          &gt; Hi,<br>
          &gt;<br>
          &gt; is it meanwhile possible to define an IPv6 endpoint AND
          and an IPv4<br>
          &gt; endpoint as fallback<br>
          &gt; in case a road warrior does not get IPv6 connectivity
          when switching<br>
          &gt; internet sockets?<br>
          &gt;<br>
          &gt; Regards,<br>
          &gt;<br>
          &gt; Renne<br>
          &gt; _______________________________________________<br>
          &gt; WireGuard mailing list<br>
          &gt; <a href="mailto:WireGuard@lists.zx2c4.com"
            target="_blank" rel="noreferrer" moz-do-not-send="true">WireGuard@lists.zx2c4.com</a><br>
          &gt; <a
            href="https://lists.zx2c4.com/mailman/listinfo/wireguard"
            rel="noreferrer noreferrer" target="_blank"
            moz-do-not-send="true">https://lists.zx2c4.com/mailman/listinfo/wireguard</a><br>
          <br>
          <br>
          _______________________________________________<br>
          WireGuard mailing list<br>
          <a href="mailto:WireGuard@lists.zx2c4.com" target="_blank"
            rel="noreferrer" moz-do-not-send="true">WireGuard@lists.zx2c4.com</a><br>
          <a href="https://lists.zx2c4.com/mailman/listinfo/wireguard"
            rel="noreferrer noreferrer" target="_blank"
            moz-do-not-send="true">https://lists.zx2c4.com/mailman/listinfo/wireguard</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
WireGuard mailing list
<a class="moz-txt-link-abbreviated" href="mailto:WireGuard@lists.zx2c4.com">WireGuard@lists.zx2c4.com</a>
<a class="moz-txt-link-freetext" href="https://lists.zx2c4.com/mailman/listinfo/wireguard">https://lists.zx2c4.com/mailman/listinfo/wireguard</a>
</pre>
    </blockquote>
  </body>
</html>

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

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

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 18:10 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

Reply instructions:

You may reply publically 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

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com zx2c4-wireguard@archiver.kernel.org
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/ public-inbox