My school’s wireless network has two areas:

  • WPA-secured area, with a passkey that I know
  • WEP EAP-MSCHAPv2 secured area, requiring a user name & password (which I have)

The WPA area is fine- I can connect. However, this bug in the Nokia N800 is obviously preventing me reach the second, of course, being the area I’m more likely to use the n800 in.. There are a few solutions: I think the famous wpa_supplicant would fix this problem. The other solution is to use Open1x, which of course looks as if it’d definitely fix this. So that’d be my immediate reaction for a normal Linux computer, however, this is an N800. I’m looking into it..

The other issue sounds a little ridiculous, but proxy user names and passwords are not allowed in the N800. To use the proxy server at school this requires a user name and password, and as there’s no-where to enter these, then this does not work. Looking at the osso-feed-reader (Liferea) source it seems to use the gconf values, but it has been reported that simply adding gconf values is not a fix.

These two things are the most annoying problems with it at the moment! There are some other annoying things but I’ll sum them up later. I’d better satisfy my developer discount somehow though..!

3 Responses to “Roadblocks”

  1. Miguel Says:

    We use PEAP with MSCHAP on our corporate LAN. I am having similar issues with the N800. In looking at the logs on the Radius Server which authenticates our wireless clients, it appears to be an issue in the way the N800 sends the username and password characters. They are sent to the Radius server as gibberish.

  2. Rick Kempf Says:

    Has this ever beeen resolved. Lots of people must have the same problem - I know I do.

  3. jonnylamb Says:

    There are two issues I explained.
    The former I never actually got round to investigating, although I’m not saying I might have got anywhere. I’m not sure how flexible the N800’s wireless can be.
    The latter problem I expect this would be a lot easier to fix, although yet again I haven’t investigated.
    I no longer have these problems because I have moved on to a sane wireless network area.

Leave a Reply