Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: David Wibergh <david@ovpn.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:02:47 +0200	[thread overview]
Message-ID: <CAHmME9riJ2Mi6FEw5+kftUFqBOmm+i7dZH-jrwPOg-hZ1VQ0PA@mail.gmail.com> (raw)
In-Reply-To: <etPan.5f806950.26ad9721.107c@ovpn.com>

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.

  reply	other threads:[~2020-10-09 14:03 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 [this message]
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=CAHmME9riJ2Mi6FEw5+kftUFqBOmm+i7dZH-jrwPOg-hZ1VQ0PA@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=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).