I'm in a college with wifi available for mobile devices, and I have an Android based G1 type(rooted, of course) on CM-6.0.

Normal process for going online is:
1. Get an IP from dhcp
2. Surf anywhere, and get redirected to their login page.
3. Log in.
I'm able then to surf. At least last year I was. But they upgraded things in the summer.

This year, no login appears. DNS appears to be bouncing between http://data.mobclix.com(?) and the Institute's login page.
data.mobclix.com is redirected to login (expected)
login is directed to data.mobclix.com (Not expected).

Tech Support are positively hostile and agressive, refuse all information, and leave it to me to hack my way in.

OK, I'm no hacker, but I installed 'Shark for root' and had a look. It appears to be a protocol problem - I'm not doing whatever protocol they are. I'm getting redirected from one site to the other.

The other real possibility is that the network packets identify as android, and my paranoid friends in tech may have excluded that somehow. Windows and macOS get on OK.

Any idea what protocol they could be using? Is it out there for Android?

If you think it's a problem because it's Android in the agent-string, you can set your browser to "desktop mode" in the settings for either the default Android browser or Dolphin (only two I've tried). That will change the browser to identify as a desktop client.

Apparently other Androids can get in. I'm currently working on the presumption that it is my own network stack, and looking at a reinstall, or confirming this some way. I've had to restore a nandroid backup more than once because it isn't behaving. I eben have problemas on my own wifi router.

I'll mark this solved, go away and figure myself out. Thanks for the idea though - I may well use it.

mobclix.com may be an apple thing so they think you are using an apple device?

Best way is to monitor another proper logon and decode what is going on.

Well, I bit the bullet yesterday, and reinstalled CM-6.0. It seems to have fixed something fundamental in the network stack I also uploaded a few output files from Shark for Root, and had a look in wireshark I get this massive technicolour display and basically, it appears I wasn't doing the protocol.

We'll see today. I'll kill this if I'm successful.