All of lore.kernel.org
 help / color / mirror / Atom feed
From: Subin Abid <subinabid@gmail.com>
To: Martin Eskdale Moen <martinmoen@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Google Chromecast
Date: Thu, 3 Jan 2019 12:10:29 +0530	[thread overview]
Message-ID: <CAOAvjy2h_1xHvAUH5BOyCz+Fa_aBkrTDxcsvzgg9XrYnVNHe4Q@mail.gmail.com> (raw)
In-Reply-To: <CAKiCHuOeimfJ3y7k1PWxxN_YXSs8AFA8L7++4C3XFAMLjNM21A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 932 bytes --]

Hi Martin,

Yes, I am.

I came across this message on the thread -  "The network settings for the
peer has a checkbox 'Exclude Private IPs';
You need it enabled so that your phone and Chromecast can talk to
each other on the private network rather than going through the VPN tunnel.
"

Let me try this and i will give a feedback ASAP


On Thu, Jan 3, 2019 at 2:43 AM Martin Eskdale Moen <martinmoen@gmail.com>
wrote:

> Are you routing all your traffic through the VPN?
>
> On Wed, Jan 2, 2019 at 6:47 PM Subin Abid <subinabid@gmail.com> wrote:
>
>> Hello,
>>
>> Android device (using Home app) cannot connect to chromecast while the
>> device is connected to VPN. Is anyone else facing this problem?
>>
>> --
>> Subin Abid
>>
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
>

-- 
Subin Abid
Mob : +91 - 94808 42431

[-- Attachment #1.2: Type: text/html, Size: 2999 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-01-08  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19 14:15 Google Chromecast Subin Abid
2019-01-02 21:13 ` Martin Eskdale Moen
2019-01-03  6:40   ` Subin Abid [this message]
2019-01-02 22:47 ` Jaseem Abid

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=CAOAvjy2h_1xHvAUH5BOyCz+Fa_aBkrTDxcsvzgg9XrYnVNHe4Q@mail.gmail.com \
    --to=subinabid@gmail.com \
    --cc=martinmoen@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.