From: "Jérémy Prego" <jeremy@pregonetwork.net>
To: wireguard@lists.zx2c4.com, team@wireguard.com
Subject: Re: wireguard android don't prefer IPV6 endpoint
Date: Sat, 2 Jan 2021 09:27:30 +0100 [thread overview]
Message-ID: <64137c2f-266a-1a06-9130-e8b42ecd4edf@pregonetwork.net> (raw)
In-Reply-To: <ead64d0f-af1e-8d5c-3d87-ed14902c5e1e@pregonetwork.net>
I confirm the same problem in wifi
Le 27/12/2020 à 07:02, Jérémy Prego a écrit :
> hello,
>
> I've always encountered a bug with android wireguard when using an ipv4
> / ipv6 endpoint.
>
> I tested with two phones:
> Huawei p10 lite android 8.0 emui 8
> Xiaomi poco m3 android 10.0 miui 12
>
> When i'm in LTE (not yet been able to test in wifi), wireguard connects
> to the endpoint in ipv4 and not in ipv6, and i don't understand why it
> is doing that.
> However, chrome, for example, does use ipv6 by default and not ipv4.
>
> My phone does recover an ipv6 in 2a01: cb1a ........ / 64 and not an
> ipv6 type fc00 / fd00 / fe80 ...
> I also specify that if I only have an AAAA record, the tunnel works fine
> in ipv6. but suddenly, I can no longer connect to wifi which only have ipv4.
>
> I would like wireguard to favor ipv6 when it is available, and otherwise
> switch to ipv4.
>
> Is it possible ?
>
> Thanks,
>
> Jerem
next parent reply other threads:[~2021-01-02 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ead64d0f-af1e-8d5c-3d87-ed14902c5e1e@pregonetwork.net>
2021-01-02 8:27 ` Jérémy Prego [this message]
2021-01-03 13:48 ` Harsh Shandilya
2021-01-03 15:58 ` Jérémy Prego
2021-01-03 16:44 ` Harsh Shandilya
2021-09-26 11:02 ` Jérémy Prego
2021-09-26 11:50 ` tlhackque
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=64137c2f-266a-1a06-9130-e8b42ecd4edf@pregonetwork.net \
--to=jeremy@pregonetwork.net \
--cc=team@wireguard.com \
--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).