Chromecast issues

gistfile1.txt

The Chromecast has some challenges when compared to a simple RasberryPI/Cubieboard setup. 

With the army of developer resources Google has at it's disposal, it's clear Google didn't allocate any effort into some simple security measures.  Any wireless configuration beyond perhaps "default" router settings simply won't work with this device.

Here are things I found to be a bit frustrating, lacking, or outright insecure:

1. Requires publicly broadcasting SSID
2. Doesn't allow for SSID pinning to preferred AP-mac addresses
3. Requires AP isolation turned off
4. Broadcasts it's own non-secured configuration network when it cannot reach the intended AP
5. Only works with 2.4GHz spectrum
6. Android client app forces your client over to the same SSID network, even if you have two APs on the same vlan (instead of prompting)
7. Firmware updates are controlled entirely by Google. You will get your OTA update when Google says you will get your update.


I wish there was a way to at least control some of these configurations.  In the case of AP isolation, this would appear to be intentional design.