@ww wrote:
fyi. chromecast has some problems a.t.m.
http://bgr.com/2018/01/15/google-chromecast-home-wifi-problems-router-crashing/
https://www.theregister.co.uk/2018/01/15/router_vendors_update_firmware_to_protect_against_google_ch...
There are, indeed, several problems with Chromecast. Best not to conflate the different issues, although the Vulture always does.
This from information supplied by Google
Which ports does Chromecast use when connecting to external services?
- HTTP: TCP/80
- HTTPS: TCP/443
- DNS: UDP/53
- SNTP: UDP/123
Which ports are used by Chromecast to communicate with computer/phone/tablet in the same network?
- SSDP: UDP/1900/multicast
- mDNS: UDP/5353/multicast
- TCP/8008
- TCP/8009
In my experience, when using a L2 switch (MS220-8P) that has IGMPv3 enabled, and an MR32 WAP, connecting from a smartphone via the WAP to a wired Chromecast capable device on the same VLAN and the same physical switch, there are no issues, it works fine.
However, at present, if the Chromecast devices are on a different VLAN, they do not function, despite explicity granting the required permissions for the VLANs to access devices on the other VLAN. At present the MX devices do not handle multicast packets properly and an IGMP proxy cannot be configured, which may prevent Chromecast packets traversing the MX.
Long term, all "smart" devices should be placed on their own VLAN(s), as their manufacturers are not particularly security aware and they are vulnerable. So we have to find a way of overcoming this particular issue sooner rather than later.