This is after dhcp success. tcpdump shows absolutely zero traffic from the ip address the Chromecast was assigned.
Anyone have ideas why Chromecast somtimes lies that it's connected to wifi but not to the internet?
-
-
-
So somehow Chromecast has decided it has no internet connectivity without trying to send any ip packets...
-
This happens for a long time after boot with AP using hostapd on Linux, not with cheap netgear router.
-
dhcp server is identical either way (netgear config is pure bridge).
-
Are they doing something idiotic with the AP's MAC address and assuming certain MACs are clients not routers?
End of conversation
New conversation -
-
-
They probably do the same thing as Android, where it's assumed there's no internet access until it feels like checking for it.
-
It's probably supposed to check shortly after connecting to a new network though. Maybe there's something blocking that...
-
Android connects to http://clients3.google.com/generate_204 to check for internet access / captive portals. High likelihood it's the same thing.
-
There aren't even any dns lookups. No traffic from the Chromecast's ip when this happens, just repeated successful dhcp reqs.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.