Development discussion of WireGuard
 help / color / mirror / Atom feed
* Samsung Galaxy S10e can’t reach local devices in network
@ 2020-10-09 12:18 David Wibergh
  2020-10-09 12:21 ` Jason A. Donenfeld
  0 siblings, 1 reply; 5+ messages in thread
From: David Wibergh @ 2020-10-09 12:18 UTC (permalink / raw)
  To: wireguard

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



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2020-10-14 10:47 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-09 12:18 Samsung Galaxy S10e can’t reach local devices in network David Wibergh
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

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).