OK, this post is really meant to catch some flies. Looking at my site logs, I know that people sometimes stumble upon my blog looking for solutions to things that I haven't really got solutions for. Here's another such thing, but hopefully we can work something out.
In a previous post I sang the praises of my new Nokia E71 running Symbian S60 3rd ed. It's a great little unit and has the full complement of connectivity options, including 802.11g Wifi supporing WPA/WPA2/802.1x authentication.
In case you also weren't aware, I go to the University of New South Wales, who recently provisioned their campus with a free wireless network for students and staff.
The Uniwide network, as it is known, uses WPA2/EAP-PEAP/MSCHAPv2 to authenticate students, all of which are supported by the E71. The ITS setup page lists these details but rather unhelpfully only provides an actual guide, or support, for the iPhone and its bretheren. (I'll have a rant about trading one monopoly-type technology organisation for another in a separate, future post. Go FLOSS!)
So here is a run down of what I tried, in order:
- The "I'm an iPhone user" approach. That is, I went to uni, scanned for networks, found the "uniwide" network, and told it to connect. Result: Authentication failed. No network, no way.
- The "OK, I was just pretending. I actually do like fiddling with settings" approach. That is, taking the automatically created Access Point as a starting point, I delved into the settings to see what was wrong. It had correctly set the network up as a WPA2, EAP-based network, but was attempting to use EAP-SIM or EAP-AKA to authenticate. "Aha!" I cried, deftly enabling EAP-PEAP and disabling the other EAP protocols. In so doing I also then found that the settings for EAP-PEAP allowed you to set up another layer of EAPs, which were also defaulting to EAP-SIM and EAP-AKA. This time I enabled EAP-MSCHAPv2 and set my username and password for MSCHAPv2 accordingly. Feeling rather pleased with my own powers of reasoning, I tried connecting. Result: No network, no way. "EAP-PEAP Authentication failed"
- The "This is starting to get a little ridiculous" approach. I happen to know, from setting up my laptop with this network, and from the iPhone setup guide, that you have to accept UNSW's security certificate to connect to the network. I also happen to know that the Authority certificate that the uni is using is called UTN-USERFirst-Hardware, and is issued by a company called Comodo. It is available for download here. I cleverly determined that this CA isn't installed on the E71, so maybe the poor phone can't authenticate the certificate it's being presented with. Not knowing a huge amount about certificate chains and all that, I installed those certificates onto the phone from the comodo website. This in itself didn't change anything. So I went one step further and in the EAP-PEAP settings, I set the Authority Certificate to be the UTN-USERFirst-Hardware certificate that I had just installed. Result: The phone takes a really long time thinking about connecting before finally failing in exactly the same way as before. Not happy.
- The "Somebody out there must have worked this out already" approach. I wrote a blog post about my troubles and will wait for some kind soul who finds this through Google to comment on the post with their experiences, be they positive or the same as mine.
Seriously. Any Symbian S60 users out there who have worked out the voodoo that makes these little suckers want to play nice with Uniwide? I'm a little bit perplexed by it all.
And while you're here, you might as well comment on this too: does anybody else have issues connecting to some wireless networks with a "No Gateway Reply" error? This is unrelated to the Uniwide network, as it seems to happen consistently at my parents home network, which is just a regular WPA-PSK network, with MAC restriction, and it also occassionaly happens at my own home (oh the shame...)
So although I am pleased with my E71 and it does what it's told most of the time, I am also looking forward to the next firmware update, which will hopefully be not to far away, thankyou, Nokia.