From: David Wibergh <david@ovpn.com>
To: "Jason A. Donenfeld" <jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Samsung Galaxy S10e can’t reach local devices in network
Date: Fri, 9 Oct 2020 16:52:23 +0200 [thread overview]
Message-ID: <etPan.5f80792c.2de5c3e3.107c@ovpn.com> (raw)
In-Reply-To: <CAHmME9riJ2Mi6FEw5+kftUFqBOmm+i7dZH-jrwPOg-hZ1VQ0PA@mail.gmail.com>
The command output is the same:
Sony
$ ip route get 10.220.0.4
10.220.0.4 dev wlan0 table 1026 src 10.220.0.6 uid 10356
cache
Galaxy S10e
$ ip route get 10.220.0.4
10.220.0.4 dev wlan0 table 1017 src 10.220.0.5 uid 10294
cache
We’ll try to get some of our users to run similar tests. We do have an S7 that we can dig up and do some testing on. If you want to go down the rabbit hole, but don’t have access to a galaxy device, I could ship the S10e to you.
Thanks,
David
På 9 oktober 2020 kl. 16:03:02, Jason A. Donenfeld (jason@zx2c4.com) skrev:
> Hmm, from that command output, I'm still not quite sure. The most
> significant difference I can see from casual inspection is:
>
> Sony:
> 19000: from all fwmark 0xcd/0x1ffff iif lo lookup 1026
> 21000: from all fwmark 0xce/0x1ffff lookup 1026
>
> Galaxy:
> 19000: from all fwmark 0x2ad/0x1ffff iif lo lookup 1017
> 21000: from all fwmark 0x2ab/0xffff lookup 1017
>
> Is the galaxy missing a leading 0x1 in the mask of that second rule there?
>
> What do you get on each when you run `ip route get 10.220.0.4`? Same
> thing or is it different?
>
> I also noticed that on the Galaxy, there's a direct route to some
> telco server -- `90.132.128.59 via 10.220.0.1 dev wlan0 table 99 proto
> static`. I didn't see this direct route on the Sony. I doubt it's
> related to the above, but I've also never seen this before and wonder
> if it's some VoLTE/VoWIFI hand-over trick in recent Android networking
> stacks.
>
prev parent reply other threads:[~2020-10-09 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 12:18 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 message]
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.5f80792c.2de5c3e3.107c@ovpn.com \
--to=david@ovpn.com \
--cc=jason@zx2c4.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).