From: David Wibergh <david@ovpn.com>
To: wireguard@lists.zx2c4.com
Subject: Samsung Galaxy S10e can’t reach local devices in network
Date: Fri, 9 Oct 2020 14:18:46 +0200 [thread overview]
Message-ID: <etPan.5f80552b.45639067.8db@ovpn.com> (raw)
Hi everyone,
Sorry for bothering you, but we do have an Android specific question. When using the official WireGuard app on Android (v1.0.20200927), as well as our own, on certain device types we have issues reaching local devices in the network, even if we exclude private IPs. It works entirely fine on other device models though. I have tried on several different wireless networks & different subnets (192.168.0.1/24, 192.168.0.1/16, 10.220.0.1/16), as well as reaching various devices.
So far, we have had issues on OnePlus HD1903 & Samsung Galaxy S10e (model number SM-G970F).
Network
I have three devices in the wireless network (10.220.1.1/16).
1. Samsung Galaxy S10e (10.220.0.2)
2. Macbook (10.220.0.1)
3. Lenovo thinkpad (10.220.1.7)
On the S10e, I can not ping 10.220.0.1 nor 10.220.1.7 when connected.
On the Macbook, I can ping 10.220.1.7 when connected.
Configurations
Macbook uses following config:
[Interface]
PrivateKey = XXX
Address = 172.20.196.X/32, fd00:0:1337:cafe:1111:1111:X:1a60/128
DNS = 46.227.67.134, 192.165.9.158
[Peer]
PublicKey = 0CvxLBss+WQyJqidXRUnd5iO9gMJwMFNPidg09d4Onk=
AllowedIPs = ::/0, 0.0.0.0/5, 8.0.0.0/7, 11.0.0.0/8, 12.0.0.0/6, 16.0.0.0/4, 32.0.0.0/3, 64.0.0.0/2, 128.0.0.0/3, 160.0.0.0/5, 168.0.0.0/6, 172.0.0.0/12, 172.32.0.0/11, 172.64.0.0/10, 172.128.0.0/9, 173.0.0.0/8, 174.0.0.0/7, 176.0.0.0/4, 192.0.0.0/9, 192.128.0.0/11, 192.160.0.0/13, 192.169.0.0/16, 192.170.0.0/15, 192.172.0.0/14, 192.176.0.0/12, 192.192.0.0/10, 193.0.0.0/8, 194.0.0.0/7, 196.0.0.0/6, 200.0.0.0/5, 208.0.0.0/4, 46.227.67.134/32, 192.165.9.158/32
Endpoint = vpn90.prd.erfurt.ovpn.com:9929
Samsung Galaxy S10e uses the following config:
[Interface]
Address = X/32, fd00:0:1337:cafe:1111:1111:e827:X/128
DNS = 46.227.67.134, 192.165.9.158
PrivateKey = XXX
[Peer]
AllowedIPs = 0.0.0.0/5, 8.0.0.0/7, 11.0.0.0/8, 12.0.0.0/6, 16.0.0.0/4, 32.0.0.0/3, 64.0.0.0/2, 128.0.0.0/3, 160.0.0.0/5, 168.0.0.0/6, 172.0.0.0/12, 172.32.0.0/11, 172.64.0.0/10, 172.128.0.0/9, 173.0.0.0/8, 174.0.0.0/7, 176.0.0.0/4, 192.0.0.0/9, 192.128.0.0/11, 192.160.0.0/13, 192.169.0.0/16, 192.170.0.0/15, 192.172.0.0/14, 192.176.0.0/12, 192.192.0.0/10, 193.0.0.0/8, 194.0.0.0/7, 196.0.0.0/6, 200.0.0.0/5, 208.0.0.0/4, ::/0, 46.227.67.134/32, 192.165.9.158/32
Endpoint = vpn11.prd.kista.ovpn.com:9929
PublicKey = p4s2SuFgKgWnV56Uh3yCx6ZWnaVyFXegV9FQqv670So=
Is this an issue you’re aware of? Is there anything else needed from me?
Thanks,
David Wibergh
next reply other threads:[~2020-10-09 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 12:18 David Wibergh [this message]
2020-10-09 12:21 ` Jason A. Donenfeld
2020-10-09 13:44 ` David Wibergh
2020-10-09 14:02 ` Jason A. Donenfeld
2020-10-09 14:52 ` David Wibergh
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=etPan.5f80552b.45639067.8db@ovpn.com \
--to=david@ovpn.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).