cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Routing Chromecast across VLANs

Conversationalist

Routing Chromecast across VLANs

Has anyone been able to figure out how to route Chromecast broadcasts from one VLAN to a maobile device on another VLAN? I'm working with an MX64.

3 REPLIES 3
Kind of a big deal

Re: Routing Chromecast across VLANs

From this reddit post I read mDNS is the culprit keeping it from working across subnets:

https://www.reddit.com/r/Chromecast/comments/454fsi/chromecast_across_subnetsvlans_pfsense/

 

I have no Chromecast myself so I can't test it but you might be able to leverage the Bonjour Forwarding feature in the MX to make it work:

https://documentation.meraki.com/MX/Other_Topics/Configuring_Bonjour_forwarding_for_the_MX_Security_...

 

Don't forget to also open up TCP 5556 and TCP 5558 from your Chromecast segment to your source device segment as mentioned in the Reddit.

 

Hope that helps.

Kind of a big deal

Re: Routing Chromecast across VLANs


@EricNathan wrote:

Has anyone been able to figure out how to route Chromecast broadcasts from one VLAN to a maobile device on another VLAN? I'm working with an MX64.


Rather than "kick against the pricks", because I've been there with an otherwise nice Juniper SRX, I am not going to even attempt routing Chromecast broadcasts on an MX, because the MX is deficient as far as Multicast and IGMP Proxies/Reflectors are concerned.

 

In fact there is no way to get an MX to handle the flavour of multicast used by content providers to distribute programs (subscription TV).This is commonplace in Britain, Europe and much of East Asia. It is not commonly encountered in the US, although I'm aware of some services that use IP4 Multicast that requires the use of an IGMP proxy on the router in the subscriber's premises.

 

Chromecast also uses Multicast. Routing multicast requires feature enablement on the MX which has not occurred despite repeated requests. Strangely, the switches do handle multicast traffic properly (IGMP snooping).

 

The good news is that there is a solution.

 

We installed a security appliance, switch and WiFi access points and VLANned the heck out of the new network, as it is designed to handle all the goats and bad boys - smart appliances, smart TVs, security kit, Chromecast, Bonjour, guest WiFi etc.

 

Instead of connecting to the VDSL modem, the MX now connects to a LAN port on the third party security appliance, which passes the MX traffic through to the Internet. Rather than allow devices (typically phones) connected to a MX VLAN access to the third party network, I grabbed some smartphones that are now used as if they were remote controllers for Chromecast. I'll admit it is an affluent solution to an affluent problem. They can be switched off once the Chromecast device has started casting.

 

This works, security is improved, We have not had a repeat of the power company's smart meter trying to get to the Internet (which is what kicked off the redesign in the first place).

 

Interestingly, I have a neighbour who turns off his computer system at night, including the router/modem. This causes his smart TV to try and get to the internet via our guest WiFi network, all night. This turned up on an exception report and it has been permanently blocked, although it keeps trying. Smart TVs do the weirdest stuff.

Robin St.Clair | Principal, Caithness Analytics | @uberseehandel
Getting noticed

Re: Routing Chromecast across VLANs

I was looking at doing this too. Did you every figure it out, Eric?

There are some interesting responses in this reddit post.

 

https://www.reddit.com/r/meraki/comments/bkd949/one_device_available_on_multiple_ssids/

Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.