From: Christophe-Marie Duquesne <chmd@chmd.fr>
To: wireguard <wireguard@lists.zx2c4.com>
Subject: Re: [Android app] Can't connect to a chromecast when wireguard is running
Date: Sun, 30 Dec 2018 20:10:20 +0100 [thread overview]
Message-ID: <CAHLp1YmoZV-T+d_U_GDhSpgbK1099x+xVEUX=T24q5u=SKCnJA@mail.gmail.com> (raw)
In-Reply-To: <CAHLp1YkibRSvohY9FJ5G+FXaEw4tFU52rLsbWLSP8oiL0K=rhQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 858 bytes --]
Hi again,
Thinking about my former setup with Openvpn, I realized it had a setting
"bypass VPN for local networks" (under "routing"). Is there such a thing in
the Wireguard app? (In the peer config, there is a checkbox "Exclude
private IPs". In doubt, I tried to enable it, but then the wireguard
interface stopped working with the message "Error bringing up tunnel: Bad
address")
Generally, the app which I believe would solve my chromecast problem is
probably "Google play services" (com.google.android.gms). It is
unfortunately not part of the list of applications one can exclude from the
UI. Is there a way to do one of these two things?
- Implement a feature similar to "bypass VPN for local networks"
- Make it possible to exclude an application by string input (directly
typing "com.google.android.gms" in some text area)
Thanks,
Christophe-Marie
[-- Attachment #1.2: Type: text/html, Size: 1134 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-12-30 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 10:27 Christophe-Marie Duquesne
2018-12-30 19:10 ` Christophe-Marie Duquesne [this message]
2018-12-30 20:09 ` Samuel Holland
2019-01-03 2:48 ` Samuel Holland
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='CAHLp1YmoZV-T+d_U_GDhSpgbK1099x+xVEUX=T24q5u=SKCnJA@mail.gmail.com' \
--to=chmd@chmd.fr \
--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).