From: "Hendrik Friedel" <hendrik@friedels.name>
To: "Kilian Schauer" <kilian@schauer.tech>
Cc: wireguard@lists.zx2c4.com
Subject: Re[2]: ipv6 vs. ipv4
Date: Mon, 18 Apr 2022 08:43:34 +0000 [thread overview]
Message-ID: <ema52cc7e0-e1ab-4564-a4a6-fbb65abb12c4@envy> (raw)
In-Reply-To: <9ff861ea-6d25-4e63-ba43-615afe1b655b@schauer.tech>
Hello Kilian,
thanks for your reply.
>the WireGuard mobile apps prefer IPv4 for connecting to the peer, since this helps roaming between networks (where many are still IPv4-only).
understood. Is that documented somewhere? For the Windows-Client, I did
read somewhere that ipv6 is preferred.
I find it inconsistent, that the clients behave differently.
>If you want to force an IPv6 transport, you either need to put a raw IPv6 address into Endpoint, or use an AAAA-only domain
Intuitively, I tried [my.domain.com]:51280 in order to enforce ipv6
(just like ipv6 adresses are enclosed in [].
Would that not be an enhancement to the app?
Best regards,
Hendrik
>
prev parent reply other threads:[~2022-04-18 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 8:14 Hendrik Friedel
2022-04-17 9:26 ` Kilian Schauer
2022-04-18 8:43 ` Hendrik Friedel [this message]
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=ema52cc7e0-e1ab-4564-a4a6-fbb65abb12c4@envy \
--to=hendrik@friedels.name \
--cc=kilian@schauer.tech \
--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).