Hi Matthias,
Thanks for the explanation.
I did some more testing on Windows. If the peer FQDN resolves to both and
A, WireGuard seems to check for an interface with an IPv4 address (other than
link-local or loopback). If there is one, it uses IPv4, otherwise IPv6. The
issue is that it doesn'
On 17.02.20 16:44, Maurice Walker wrote:
> The Android (v0.0.20200206) and Windows (v0.0.38) clients have the same bug.
It's not a ("simple") bug, but a general problem with peers with
multiple addresses – wireguard only stores one in the kernel, it doesn't
do multipath, by design.
Thus the front
Hello,
On Thu, Jan 2, 2020 at 09:40:53 CET, Siyuan Ren wrote:
> I am using WireGuard on my iPhone, and the endpoint is specified by a
> domain name that has both and A record. When I turn on WireGuard
> in a network with dual IPv6 and IPv4, I find out that WireGuard
> chooses IPv4 by executi
On Thu, Jan 2, 2020 at 09:40:53 CET, Siyuan Ren wrote:
> I am using WireGuard on my iPhone, and the endpoint is specified by a
> domain name that has both 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"
I am using WireGuard on my iPhone, and the endpoint is specified by a
domain name that has both 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,
