Historic archive of defunct list cerowrt-users@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: cerowrt-users <cerowrt-users@lists.bufferbloat.net>
Subject: Re: [Cerowrt-users] [Cerowrt-devel] Chromecast on cerowrt
Date: Fri, 30 Aug 2013 16:15:51 -0700	[thread overview]
Message-ID: <CAA93jw5K_qxzyn3tVGOxt4wtT6st2Y0YT8rckUq-hQfcbpag1g@mail.gmail.com> (raw)
In-Reply-To: <20130830110822.61814f88@nehalam.linuxnetplumber.net>

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

In my all too brief test of chromecast

I had to set it up on the same 2.4ghz interface.

After it was setup I could get to it via 5 or 2 or wired interfaces.
On Aug 30, 2013 11:08 AM, "Stephen Hemminger" <stephen@networkplumber.org>
wrote:

> On Fri, 30 Aug 2013 12:29:30 -0400
> Christopher Robin <pheoni@gmail.com> wrote:
>
> > Ah, let me explain the problem better.
> >
> > The chromecast connects just fine via 2.4 ghz. It's unable to connect via
> > 5ghz or ethernet. But to stream to the chromecast you have to be
> connected
> > to the router via 2.4ghz as well. If you're connected via ethernet or
> 5ghz
> > you can't see the chromecast to stream to it.
> >
> > I've tried several devices (ipad, android phone, desktop) and they all
> come
> > back with the same result. If you connect to the network via 2.4ghz the
> > chromecast works fine. If you connect any other way, you can't talk to
> the
> > chromecast.
> >
> > I've verified that the networks I'm connecting to are all on the same
> vlan.
> >
>
> On Cerowrt the 2.4 and 5 Ghz are separate IP networks (not bridged).
> Chromecast uses some form of network local communication (Multicast?)
> that is not forwarded. For normal users this is a security feature.
> _______________________________________________
> Cerowrt-users mailing list
> Cerowrt-users@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-users
>

[-- Attachment #2: Type: text/html, Size: 2009 bytes --]

  reply	other threads:[~2013-08-30 23:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 15:30 [Cerowrt-users] " Christopher Robin
     [not found] ` <67D417E9-ED85-40BC-A7A8-FFCAFD2FBAC9@imap.cc>
2013-08-30 16:29   ` [Cerowrt-users] [Cerowrt-devel] " Christopher Robin
2013-08-30 18:08     ` Stephen Hemminger
2013-08-30 23:15       ` Dave Taht [this message]
2013-09-01 13:40         ` Christopher Robin
2013-09-01 16:39           ` Dave Taht
2013-09-03 16:06             ` Stephen Hemminger

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=CAA93jw5K_qxzyn3tVGOxt4wtT6st2Y0YT8rckUq-hQfcbpag1g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-users@lists.bufferbloat.net \
    --cc=stephen@networkplumber.org \
    /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