[Google Chromecast] nigelhealy:
So I know a little, but I don't have 100% solution yet, about this in that you must go to your router and make it forward everything for 212.58.240.0/20 to a UK http proxy. You can make that proxy via things like privoxy which uses TOR. This does not forward everything to the proxy (which would be terrible performance) but just the geoIP checking which is 17 bytes every 56 secs or so. This can then get stuff like HD streaming.

Issue is... iplayer just seems broke today full stop. Away from Chromecast things which worked don't. I thought it was Chromecast and wasted hours to only find iplayer in general broke.

Once iplayer is working for me from "good 'ole fashioned" means I can then probe what is needed for Chromecast.

FYI helps if you're running DD-WRT or some other smart router so you can do stuff like run VPN off router and make it only do it for the Chromecast and turn that on/off or do seamless proxying via IPTABLES. If not... you're going to find this even harder to make work.

A much more near-100% perfect fallback which in my experience is better is to ditch the iplayer app and just move to get-iplayer, it downloads to mp4 files, make that visible via Apache as http or DLNA or one of the many alternatives then use a Chromecast app to stream that. The advantage is you don't suffer streaming stutter and get HD video and vids never expire, etc, etc. The device which is running get-iplayer still needs the proxy support but its easier to do away from Chromecast than within Chromecast. Tangential but in some ways better.

---------- Post added at 09:35 PM ---------- Previous post was at 09:29 PM ----------

Like what Apple does? The iplayer app on Apple does some kind of background check to find where you REALLY are and blocks, something Android hasn't done. I can see though something has happened major in the back-end servers inside BBC, they are sending quite different traffic patterns than they done for the last years. Much more use of Akamai than before. Wonder if they done that to "scale up" for more streaming demand such as likes of Chromecast will be adding? The traffic now looks more like ITVplayer. ITV sends its geoIP checking to 4 different services.

I'm routing all traffic through a router running traffic analyser so I can see inside all the bytes flowing. This one could involve two cups of coffee.

---------- Post added at 10:30 PM ---------- Previous post was at 09:35 PM ----------

They've inserted a few more checks recently, to Amazon (which is usual) and someone called wavecable, I think what's happening is these other services are not in the UK and so they are basically triangulating your whereabouts. I'm getting it to work a little better each time. This looks near-identical to how ITVplayer has been for a year+. This is fixable but just takes time.

212.58.244.79	bbc-vip124.telhc.bbc.co.uk	00:24:17:aa:42:c8	2,292	17,158	19,450	50 secs

54.243.165.170	ec2-54-243-165-170.compute-1.amazonaws.com	00:24:17:aa:42:c8	776	347	1,123	51 secs

212.58.244.68	bbc-vip113.telhc.bbc.co.uk	00:24:17:aa:42:c8	3,669	8,039	11,708	53 secs

204.195.95.73	static-204-195-95-73.wavecable.com	00:24:17:aa:42:c8	1,632	38,941	40,573	1 min, 3 secs

212.58.246.122	bbc-vip036.cwwtf.bbc.co.uk