pfSense Gold Subscription

Author Topic: UPnP & Chromecast  (Read 34579 times)

0 Members and 1 Guest are viewing this topic.

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21373
  • Karma: +1431/-26
    • View Profile
Re: UPnP & Chromecast
« Reply #15 on: September 04, 2013, 02:18:08 pm »
Has it occurred to anyone that Chromecast might be a broken POS that isn't quite ready for the world?

I'm sure it has, though it's still rather new/early. Google has been pushing updates for it "improving" it as they go.

So I wouldn't say "broken POS" but more like "in the early adopter stage of its lifetime".

Po-tay-to, po-tah-to... :-)
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline kejianshi

  • Hero Member
  • *****
  • Posts: 4947
  • Karma: +195/-40
  • Debugging...
    • View Profile
Re: UPnP & Chromecast
« Reply #16 on: September 04, 2013, 02:31:33 pm »
Well - So long as they don't start selling ChromcastReady® routers and APs that you MUST use for the service to magically work...

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +956/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: UPnP & Chromecast
« Reply #17 on: September 04, 2013, 02:35:42 pm »
So long as they don't start selling ChromcastReady® routers and switches that you MUST use for the service to magically work...

Not needed. Providing no content outside of U.S. serves this purpose just fine. They even blocked streaming content from Android phones.
Do NOT PM for help!

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21373
  • Karma: +1431/-26
    • View Profile
Re: UPnP & Chromecast
« Reply #18 on: September 04, 2013, 02:37:35 pm »
They didn't block it, they updated the API and the streaming apps needed to catch up to the new API.

Still, it's all beyond the scope of this thread - this is just trying to make it work, not debating its merits.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline stephenw10

  • Administrator
  • Hero Member
  • *****
  • Posts: 11909
  • Karma: +467/-15
    • View Profile
Re: UPnP & Chromecast
« Reply #19 on: September 04, 2013, 02:52:20 pm »
I'll be following this closely. No chance of getting a Chromecast though, yet.
I could believe it's an issue with the AP somehow interfering with broadcast or multicast.
Since most of what the chromecast is meant to do is stream stuff directly, rather than from another wifi device, I could also believe it wants to open firewall holes and be accessible from Google HQ via UPNP.
I could just about believe the setup app. just asks some google server 'is there a chromecast at my address?' and the server looks for it. If UPNP isn't working it won't find one. Seems like asking for a huge number of support calls though.  ;)

Steve

Offline kejianshi

  • Hero Member
  • *****
  • Posts: 4947
  • Karma: +195/-40
  • Debugging...
    • View Profile
Re: UPnP & Chromecast
« Reply #20 on: September 04, 2013, 02:54:04 pm »
Well - With the sheer numbers of us online here with adequate bandwidth and every last one of us running pfsense with openvpn, you would think that with a tiny bit of cooperation we could place-shift our IPs to be wherever we want to be to dodge content filtering.

Maybe I'll try it at my brother's house.  His is giving him issues.
« Last Edit: September 04, 2013, 02:56:02 pm by kejianshi »

Offline jsquyres

  • Newbie
  • *
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Re: UPnP & Chromecast
« Reply #21 on: September 08, 2013, 06:52:27 am »
I figured out my issue.

And to be totally clear: this had nothing to do with pfsense.

It wasn't "client isolation" in my WAP, per se, but the fact that my Cisco Aironet WAP was interfering with multicasting.  I found the solution here: http://forums.androidcentral.com/google-chromecast/301720-issue-chromecast-cisco-aironet-1140-a.html (i.e., disabling igmp snooping).

Thanks for all the suggestions; they were helpful in tracking down the real issue.