Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Will Tisdale <will@z3n.uk>
To: Nico Schottelius <nico.schottelius@ungleich.ch>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Request to change IPv4 preference - mobile apps
Date: Tue, 7 May 2019 17:28:41 +0100	[thread overview]
Message-ID: <CAFWLA-WB4hv_Y=0gnnQ=3UeJ1av0GQWg1=DQ+jMZfyuCBnJUbg@mail.gmail.com> (raw)
In-Reply-To: <87pnovti6t.fsf@line.ungleich.ch>


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

Hi Nico,

Not sure how that would work with WireGuard being a stateless protocol.
It also sounds a bit racey given that both v4 and v6 addresses would be
flinging packets at essentially the same endpoint.

I think the ‘proper’ way is to use the address returned in the AAAA record
if one exists. If people’s setup is so broken that it becomes an issue,
they
will likely have worse issues than WG not working. :)

Preferring v4 does weird things like WG using DNS64 addresses over real
v6 addresses too - and using NAT64 instead of native v6 is really broken
behaviour.


Cheers,


-Will

On Mon, 6 May 2019 at 21:57, Nico Schottelius <nico.schottelius@ungleich.ch>
wrote:

>
> Hey Will,
>
> I think the "proper" way to handle this is by using the happy eyeballs
> algorithm: resolve AAAA and A, connect to both, use whatever answers
> first.
>
> Best,
>
> Nico
>
> Will Tisdale <will@z3n.uk> writes:
>
> > Hello,
> >
> > I sent a message to the list about weirdness with IPv4 being preferred
> > over IPv6 in the iOS app a few days ago, but it didn't get there for
> > whatever reason.
> >
> > I've since done a bit of digging through the code and found that
> > preferring IPv4 is intentional, and it's also implemented that way on
> > the Android app too.
> >
> > It seems a shame to hobble native IPv6 support for everyone just to
> > work around some peoples misconfigured setups.
> >
> > My suggestion/request would be to change the apps to prefer IPv6 as
> > default, but add a switch to the apps to disable IPv6 or prefer IPv4
> > for those with broken setups.
> >
> > Does that seem reasonable?
> >
> >
> > Cheers,
> >
> >
> > -Will
> > _______________________________________________
> > 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.
>

[-- Attachment #1.2: Type: text/html, Size: 3155 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-05-11 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-14 17:17 Will Tisdale
2019-05-06 20:57 ` Nico Schottelius
2019-05-07 16:28   ` Will Tisdale [this message]
2019-05-08  9:18     ` Nico Schottelius

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='CAFWLA-WB4hv_Y=0gnnQ=3UeJ1av0GQWg1=DQ+jMZfyuCBnJUbg@mail.gmail.com' \
    --to=will@z3n.uk \
    --cc=nico.schottelius@ungleich.ch \
    --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).