From: Yeri Tiete <yeri@google.com>
To: wireguard@lists.zx2c4.com
Subject: WireGuard as gateway; excluding private IPs
Date: Sat, 8 Jun 2019 16:02:02 +0800 [thread overview]
Message-ID: <CAKDvA6JSXfjSUF3iwxorKWW9ogkf-MZtX-A+btTyqEE1++M+ow@mail.gmail.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1488 bytes --]
This is a personal project after hitting a wall for the Nth time with the
GFW. Where oVPN gets RST or otherwise blocked, it seems WG is still able to
by-pass the firewall.
I was playing around with a couple of devices; routing everything through
WG except for LAN, plus have my devices auto connect no matter where I am.
I can select to exclude private IPs and it'll update 0.0.0.0/0 to include
only public IPs. This seems to be working fine on Android: WG connects,
there's a handshake, traffic gets routed through WG gateway, and I am still
able to connect to my local network devices.
On OSX and iOS on the other hand, once I select *exclude private IPs* the
handshake fails and WG doesn't connect. No traffic gets routed and my
devices can't connect until I turn off WG.
On the other hand -- if I don't select *exclude private IPs,* on iOS and
OSX I can still access LAN IPs just fine -- but on Android that doesn't
work.
In all cases the official app is used.
Any clue why there's a difference? The server address is a public IP.
That being said I seem to be able to make it work -- it's just that the
behaviour is different.
One more thing:
Android doesn't have a feature to connect on-demand the same way iOS and
OSX do. Is this a limitation of Android? Ie I can select it to be
always-on, but the options are not as granular as iOS where I can define to
be on for Cell, WiFi and define the SSIDs.
Thanks,
Yeri Tiete | Corp Ops Engineer | yeri@google.com | +65 9225 0750
[-- Attachment #1.1.2: Type: text/html, Size: 3791 bytes --]
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4839 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-06-08 8:02 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=CAKDvA6JSXfjSUF3iwxorKWW9ogkf-MZtX-A+btTyqEE1++M+ow@mail.gmail.com \
--to=yeri@google.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).