All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kilian Schauer <kilian@schauer.tech>
To: Hendrik Friedel <hendrik@friedels.name>
Cc: wireguard@lists.zx2c4.com
Subject: Re: ipv6 vs. ipv4
Date: Sun, 17 Apr 2022 09:26:57 +0000 (UTC)	[thread overview]
Message-ID: <9ff861ea-6d25-4e63-ba43-615afe1b655b@schauer.tech> (raw)
In-Reply-To: <emdff71c03-470a-45f8-ade7-0343b0b698ab@envy>


17.04.2022 10:20:03 Hendrik Friedel <hendrik@friedels.name>:

> Hello,
> 
> I understood that wireguard prefers ipv6 over ipv4 by default.
> Nevertheless, on both Windows and Android I do not get a connection (only sent bytes no received bytes) when using my domain (friedel.dynv6.net). If I use the IP (2a00:6020:1bfb:c700:ba27:ebff:fe3e:6c55), I get a normal connection.
> I can imagine that WG uses ipv4 (the A-record is set, I cannot change that, but it points to an invalid ip)
> 
> How can I -when using the domain- enforce that ipv6 is really used?
> 
> Apart from that, my suspicion is that ipv4 is in fact used here... How can I really find out, why I get no bytes on the received counter?
> 
> Best regards,
> Hendrik

Hi Hendrik,

the WireGuard mobile apps prefer IPv4 for connecting to the peer, since this helps roaming between networks (where many are still IPv4-only). If the A record of the Endpoint domain is broken, it won't work.
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.

Hope this helps,
Kilian

  reply	other threads:[~2022-04-22  0:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17  8:14 ipv6 vs. ipv4 Hendrik Friedel
2022-04-17  9:26 ` Kilian Schauer [this message]
2022-04-18  8:43   ` Re[2]: " Hendrik Friedel

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=9ff861ea-6d25-4e63-ba43-615afe1b655b@schauer.tech \
    --to=kilian@schauer.tech \
    --cc=hendrik@friedels.name \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.