Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Ryuichiro Nagasaka <r.ngsk.todo@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Problem with connection from android phone to IPv6 endpoint
Date: Thu, 6 Aug 2020 17:02:10 +0900	[thread overview]
Message-ID: <CAODy9c4WjuE2dJrXaJQeVn_WZXrk5ewpnqcsj1R024GT78ERGw@mail.gmail.com> (raw)

Hello,

After upgrading Wireguard Android app to v1.0.20200724 by Google Play Store,
The wireguard connections with multiple hosts via IPv6 network failed
to establish.
Using IPv4, the connections had no problem. Also, the ones from iPad including
IPv6 were good.

Before the upgrade, the app version was V1.0.20200407, which could establish
connections successfully.
# reconfirmed by manually installing the old version of the app.
# The IPv6 internet connection from my phone is always quite good.

On my router, I used tcpdump to check whether packets emitting from my phone
were observed. But, no packet was found.

Android Phone's configuration (Zenfone 6):
=============
[Interface]
Address = 10.xxx.y.z/24, xxxx:xx:xxx:xxxx:yyyy:y::z/96
PrivateKey = (hidden)
DNS = 10.xxx.y.1

[Peer]
PublicKey = (hidden)
PresharedKey = (hidden)
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = [xxxx:xx:xxx:xxxx:yyyy:yyy:yy:y]:1194
==============

Router's configuration on /etc/wireguard/wg0.conf:
==============
[Interface]
Address = 10.xxx.y.1/24, xxxx:xx:xxx:xxxx:yyyy:y::1/96
ListenPort = 1194
MTU = 1372
PrivateKey = (hidden)

[Peer]
PublicKey = (hidden)
PresharedKey = (hidden)
AllowedIPs = 10.xxx.y.z/32, xxxx:xx:xxx:xxxx:yyyy:y::z/128
==============

Is anyone else having the same problem?

Sincerely,
Ryuichiro

                 reply	other threads:[~2020-08-06 14:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAODy9c4WjuE2dJrXaJQeVn_WZXrk5ewpnqcsj1R024GT78ERGw@mail.gmail.com \
    --to=r.ngsk.todo@gmail.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).