Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Maurice Walker <maurice@walker.earth>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: Bug report: WireGuard iOS prioritizes IPv4 over IPv6
Date: Mon, 17 Feb 2020 15:44:59 +0000	[thread overview]
Message-ID: <AM0PR03MB4354F7720F30995B3615664DDC160@AM0PR03MB4354.eurprd03.prod.outlook.com> (raw)

On Thu, Jan 2, 2020 at 09:40:53 CET, Siyuan Ren <netheril96@gmail.com> wrote:
> I am using WireGuard on my iPhone, and the endpoint is specified by a
> domain name that has both AAAA and A record. When I turn on WireGuard
> in a network with dual IPv6 and IPv4, I find out that WireGuard
> chooses IPv4 by executing "wg" on my server. If I explicitly set the
> endpoint as IPv6 address, WireGuard works just fine, so it is not a
> misconfiguration on my server.

The Android (v0.0.20200206) and Windows (v0.0.38) clients have the same bug.
This might be considered just bad behavior in dual-stack networks, but it
causes real issues in IPv6-only networks:
On Android, WireGuard uses IPv4 via 464XLAT (if available). This works, but
can result in decreased performance.
Windows doesn't have a CLAT [1], but WireGuard tries to use IPv4 anyway. This
results in the tunnel not working at all.

Cheers,
Maurice

[1] Well, it does, but only on mobile data, not on WiFi or Ethernet.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2020-02-23 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 15:44 Maurice Walker [this message]
2020-02-23 10:41 ` Matthias Urlichs
  -- strict thread matches above, loose matches on Subject: below --
2020-02-23 16:25 Maurice Walker
2020-02-20 21:24 Maurice Walker
2020-01-02  8:40 Siyuan Ren

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=AM0PR03MB4354F7720F30995B3615664DDC160@AM0PR03MB4354.eurprd03.prod.outlook.com \
    --to=maurice@walker.earth \
    --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).