From: Roman Mamedov <rm@romanrm.net>
To: "Marco Davids (SIDN)" <marco.davids@sidn.nl>
Cc: wireguard@lists.zx2c4.com
Subject: Re: OSX and Happy Eyeballs
Date: Wed, 18 Nov 2020 12:32:13 +0500 [thread overview]
Message-ID: <20201118123213.227694ac@natsu> (raw)
In-Reply-To: <92cb652f-b818-7224-f004-c324af5e7956@sidn.nl>
On Tue, 17 Nov 2020 13:00:01 +0100
"Marco Davids (SIDN)" <marco.davids@sidn.nl> wrote:
> Hello,
>
> We have a Wireguard VPN and everything is working fine.
>
> There is just one little thing: IPv6 Happy Eyeballs.
>
> Without the VPN enabled, happy eyeballs works fine. The AAAA (IPv6) is
> preferred over A (IPv4). But as soon as we enable the tunnel, it's the
> other way around.
>
> IPv6-only sites are perfectly reachable, but dual-stack sites are always
> reached over IPv4.
>
> It is not a showstopper, but I am just trying to understand why this is.
>
> Anyone with the same experience and more knowledge about the inner
> workings of Wireguard and Apple's happy eyeballs implementation that
> would care to comment?
Do you use ULA IPs (fc00::/7) for the tunnel endpoints? Those are always
depreferred compared to IPv4. See RFC 6724:
https://tools.ietf.org/html/rfc6724#section-2.1
--
With respect,
Roman
next prev parent reply other threads:[~2020-11-18 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 12:00 Marco Davids (SIDN)
2020-11-18 7:32 ` Roman Mamedov [this message]
2020-11-18 9:29 ` Marco Davids (SIDN)
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=20201118123213.227694ac@natsu \
--to=rm@romanrm.net \
--cc=marco.davids@sidn.nl \
--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).