![]() ![]() ![]() |
|
GregM: I'm having issues still with the chrome casts not being able to be connected to and from what I can tell, its to do with 5ghz, seems no issue on 2.4ghz so far.
GregM: Just the one ssid, but have changed to prefer 2.4ghz. I can see on the clients tab when they were on 5ghz I was having issues, but worked fine when on 2.4ghz. I also read about issues with the higher 5ghz channels with chromecasts, so removed the higher channels. Still testing, but I feel I'm making progress.
I would try creating another SSID with a 2.4ghz channel only and connect your Chromecasts to that, then see if you can see them while connected to the original SSID. I would also try disabling Broadcast filtering on both SSIDs, since you are probably not worried about rogue devices at home.
This person found they had to disable both Broadcast filtering AND the AirGroup settings before they would work for them, so you could try that as well.
Also enable Multicast transmission optimization and Dynamic multicast optimization as well
ShinyChrome:GregM: Just the one ssid, but have changed to prefer 2.4ghz. I can see on the clients tab when they were on 5ghz I was having issues, but worked fine when on 2.4ghz. I also read about issues with the higher 5ghz channels with chromecasts, so removed the higher channels. Still testing, but I feel I'm making progress.I would try creating another SSID with a 2.4ghz channel only and connect your Chromecasts to that, then see if you can see them while connected to the original SSID. I would also try disabling Broadcast filtering on both SSIDs, since you are probably not worried about rogue devices at home.
This person found they had to disable both Broadcast filtering AND the AirGroup settings before they would work for them, so you could try that as well.
Also enable Multicast transmission optimization and Dynamic multicast optimization as well
I actually re-read that link I shared before and realised I had it wrong; they were changing the Broadcast filtering from All to ARP (which is the current default setting) AND disabling the AirGroup settings, so I'm not sure what they accomplished there...
I did a bit of experimenting myself last night with a first gen Chromecast and I managed to get it reliably working across VLANs. I connected it to my 2.4ghz band only IoT SSID, which is in it's own VLAN, and I am able to cast to it via my phone from both the same SSID and another SSID in a different VLAN. I only have 'Enable Bonjour' enabled under AirGroups and the 'airplay', 'googlecast', 'DIAL' services ticked, as well as a custom group for Spotify Connect.
I also fixed a sort-of related issue where I couldn't connect to my Harmony hub (also on the IoT SSID) from the Android app, even from a device on the same SSID! When I tried setting Broadcast Filtering to 'Disabled' for that SSID only, it reappeared and now can be accessed from any VLAN, so I'm happy. It seems to use UDP for broadcasting, so I guess the Broadcast Filtering is quite aggressive it seems.
GregM: I've tried your suggestions and still issues with the tvnz app. It just won't cast, even though the app says it is eventually. No issues with my old unifi's.
Strange... I even downloaded the TVNZ app and tested this, as well as every other casting app I had on my phone, but all have been working perfectly for me.
What does the Aruba controller show the signal strength to the CC is like? Also, what settings do you have enabled on your SSIDs/AirGroup?
ShinyChrome:
GregM: I've tried your suggestions and still issues with the tvnz app. It just won't cast, even though the app says it is eventually. No issues with my old unifi's.
Strange... I even downloaded the TVNZ app and tested this, as well as every other casting app I had on my phone, but all have been working perfectly for me.
What does the Aruba controller show the signal strength to the CC is like? Also, what settings do you have enabled on your SSIDs/AirGroup?
Got it working for now, I didn't have all the services turned off.
And now this morning its not working. I'm about ready to give up.............
I have come to the conclusion that casting is just fundamentally broken since it has never worked right for me. Things are seen ok but sometimes control drops out, and then the app will just start playing on the PC even tho the chromecast is still playing. It only seems to work right for me with youtube to the gameconsoles. Everything else is unreliable and lags and often stops.
Would you #@$*&#$ believe it?!
Home sick yesterday so it was a good chance to try to sort this.
Switched off everything in AirGroup and rebooted the APs; following this, and unlike all previous times, all casting devices were visible from my phone (eg, could see and select all in Spotify etc). What was even stranger is that all casting devices - including the previously missing CC Audios and CC Ultra - were visible from the Nest Max, and could be selected. Playback to any of the devices was fairly choppy, and control/viewing on the Hub Max was a bit hit-and-miss, but they were there!
Following this, I re-enabled what I understand to be the bare necessity for Google casting (AirGroup: DLNA; Settings: googlecast; DIAL; DLNA Media), following which playback across all devices is now fine and Hub Max media control of Spotify (selecting devices; viewing what's playing on other devices) is fairly stable. Also, the list of castable devices no longer ebbs and flows (one device at a time would show up but then they'd disappear and then reappear, making it difficult to select specific devices.)
Bloody awesome! (touch wood...)
Am I likely to run into any problems having disabled all other services (eg, wireless printing)? I haven't re-enabled the Spotify service as most of my devices aren't using Spotify Connect (seems like a real dog to get CCs to use this vs Googlecast).
Thanks for all the advice and tips; as usual, really appreciated.
Until I got these Aruba's it's not a brand I've done a lot with in recent years. I've been more of a Ruckus fanboi in recent years when it came to enterprise hardware.
The reality is that in a typical enterprise or large scale WiFi deployment there is a lot more thought that needs to go into a network than a 1-2 AP install at home. Broadcast and multicast traffic on a network can be a huge problem because it simply can kill the performance of a network, hence the reasons companies include such granular filtering capabilities.
One of the single biggest issues is that broadcast and multicast traffic along with all management frames (beacon requests etc) are sent at the minimum supported rate - so if you have a scenario where you have say 100 devices on a network with zero filtering and have basic rate configured at (the near default for most vendors) 1Mbps you're instantly draining all your airtime resources as every management frame and broadcast/multicast packet is sent at 1Mbps even if your devices are connected at much higher PHY rate.
The solutions are to manage this traffic by filtering, but also to increase this rate but then you have to ensure coverage is perfect.
|
![]() ![]() ![]() |