Need 802.1x support

[GoogleCodeExporter]

   Can ChromeCast please support 802.1x?

This is necessary for use in corporate and academic settings.

I can't find a true feature request section for ChromeCast so I'll post this 
here. I figure if we get enough stars here we may find planned support for 
802.1x.

Thanks.

Original issue reported on code.google.com by rgs...@gmail.com on 9 Sep 2013 at 3:31

[GoogleCodeExporter]

Damn.  That's really too bad, Apple figured it out, and it'd be nice to have a 
PC equivalent in the Enterprise.  

Original comment by matthew....@gmail.com on 14 Jan 2015 at 11:21

[GoogleCodeExporter]

That is too bad. I'm guessing it's a licensing issue with Hollywood? It looks 
like Google had to go out of the way to disable the 802.1x functionality. 

Original comment by jamesb2147@gmail.com on 14 Jan 2015 at 11:53

[GoogleCodeExporter]

I don't understand why they cannot support this?!  One my work-study students 
hacked his own Chromecast and added code that worked just fine.  I guess we'll 
have to change our 100+ orders to Apple for our conference rooms, as will the 
other 4800 colleges and universities in the US.  Too bad.

Original comment by philspi...@gmail.com on 15 Jan 2015 at 2:45

[GoogleCodeExporter]

How are you guys getting the (presumably) Apple TV devices to work? On our 
campus, we keep running headlong into a bug where the Apple TV sets its clock 
to January 1, 1969 (pre-Unix epoch) and thus all of our wireless certs are 
invalid and it won't join the wireless. The workaround is to have an ethernet 
cable jacked in, which gives it NTP, so it can join the wireless, but that 
workaround doesn't work for a lot of the areas we want to put these in. Are you 
bridging Bonjour traffic across the wired and wireless VLAN's?

Original comment by jamesb2147@gmail.com on 15 Jan 2015 at 2:50

[GoogleCodeExporter]

@jamesb2...@gmail.com - I honestly don't know.  It was all setup and working 
before I got here, but I know that a handful of our conf. rooms and classrooms 
have AppleTVs in them for use.  I can try and find out.

Original comment by philspi...@gmail.com on 15 Jan 2015 at 2:55

[GoogleCodeExporter]

That would be great! 

I'm also curious about how your student hacked it onto the wireless, but I'm 
not sure this is the wisest place to talk about that. Feel free to email me 
directly. My Gmail username is jamesb2147.

Original comment by jamesb2147@gmail.com on 15 Jan 2015 at 3:02

[GoogleCodeExporter]

I think the issue with the current chromecast is the chipset inside does not 
officially support 802.1x... that is unfortunate, but the new Android TV boxes 
do chromecast as well and work with 802.1x as far as I know (when they come 
out...).

Original comment by dba...@ursulinestl.org on 15 Jan 2015 at 3:32

[GoogleCodeExporter]

Hi James,

Regarding support for AppleTV on enterprise networks:

* You will need to provision a special .config for the AppleTV using the
Configurator (yes, that's the name).  This config will include NTP address,
certs, and configuration.  I beleive you either need to sign up for Apple's
Enterprise Cloud Configurator or use a Mac with the program to do this.

* Bonjour will only work across subnets with a bonjour gateway (a server
that will broadcast subnet-specific broadcasts across other
'bonjour-enables' networks.  There's open source ones if you need to roll
your own or appliances from many network vendors.

Good Luck!

Matthew

Original comment by matthew....@gmail.com on 15 Jan 2015 at 6:07

[GoogleCodeExporter]

Right, our whole problem was that we would create those configuration
files, load them, and the AppleTV still wouldn't join the network after a
power loss because it defaults to 1969 when it boots up and therefore
wouldn't trust our wireless cert. The only way we could get around this was
giving it a wired network connection, thus providing it NTP, so it could
update its clock and trust the wireless cert. At that point, it was fine,
but we never got it to where we could reboot the thing and just have it
join the network completely wirelessly. (Unless, of course, someone went in
and manually set the clock.)

Original comment by jamesb2147@gmail.com on 15 Jan 2015 at 6:15

[GoogleCodeExporter]

Gotcha.  Yeah, other than wiring and using a bonjour gateway to share out
to wireless, I don't know any other way to solve that issue.   Thanks for
replying back!

Original comment by matthew....@gmail.com on 15 Jan 2015 at 6:22

[GoogleCodeExporter]

I too would like to have 802.1x working on the chromecast. 
I have that setup at home, and was sad when it wasnt working with my existing 
802.1x configured network. Luckily, only thing i had to do, was to enable a 
virtual interface on my router, and set it to WPA2 PSK... which worked.

but... common, it's 2015, devices should all be 802.1n and 802.1x compatible...

Original comment by blade86sam on 10 Jun 2015 at 2:08

[GoogleCodeExporter]

Seriously art it out Google!

Original comment by tcoc...@gmail.com on 20 Aug 2015 at 10:03

[GoogleCodeExporter]

Seriously art it out Google!

Original comment by tcoc...@gmail.com on 20 Aug 2015 at 10:03

[GoogleCodeExporter]

Just come across this problem trying to connect the chromecast to a University 
television. One of the main areas of use for these devices would be in this 
situation -- can it please be sorted out? 

Original comment by david.ed...@gmail.com on 30 Oct 2015 at 1:51

[GoogleCodeExporter]

Please fix, does not work at university

Original comment by johnsonk...@gmail.com on 11 Nov 2015 at 1:38

[GoogleCodeExporter]

I work for a K-12 District with 25k Kids and we would love to have this 
feature. 

Original comment by dgcoya...@sps.org on 15 Jan 2016 at 10:14