Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Maemo: Users

N800 won't connect via WPA2...says "network does not support"

 

 

Maemo users RSS feed   Index | Next | Previous | View Threaded


mklein at vxappliance

Oct 27, 2007, 6:12 PM

Post #1 of 7 (4273 views)
Permalink
N800 won't connect via WPA2...says "network does not support"

But this is bunk as my WM5 8525 connects via WPA2/AES! This totally
blows me away...WM?!?

I notice my ST5111 atheros client has only "WPA/WPA2" option (no manual
select) and it seems to fallback to WPA/AES.

I have googled on exact network error and found ZIP.

I am one release back from current firmware (the sdhc fix).

Anybody else seen this error? I may attempt to flash new firmware...but
will check buglist first.


thx in advance...

mike
_______________________________________________
maemo-users mailing list
maemo-users [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-users


mklein at vxappliance

Oct 27, 2007, 6:17 PM

Post #2 of 7 (4159 views)
Permalink
Re: N800 won't connect via WPA2...says "network does not support" [In reply to]

Addnly I am using WRT54GL w/DD-WRT firmware (v24-RC1). I can certainly
try an update of dd-wrt firmware as well....unfortunately earlier today
I bricked my primary 54gl and am now on backup unit....thk goodness I
had a spare. So the router firmware update may have to wait until get
another backup unit...only $60 so no biggie.

Unless my 8525 is lying (certainly possible...perhaps hidden fallback to
WPA?)...my network DOES support wpa2.


mike

Mike Klein wrote:
> But this is bunk as my WM5 8525 connects via WPA2/AES! This totally
> blows me away...WM?!?
>
> I notice my ST5111 atheros client has only "WPA/WPA2" option (no manual
> select) and it seems to fallback to WPA/AES.
>
> I have googled on exact network error and found ZIP.
>
> I am one release back from current firmware (the sdhc fix).
>
> Anybody else seen this error? I may attempt to flash new firmware...but
> will check buglist first.
>
>
> thx in advance...
>
> mike
> _______________________________________________
> maemo-users mailing list
> maemo-users [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-users
>
_______________________________________________
maemo-users mailing list
maemo-users [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-users


peter at silmaril

Oct 28, 2007, 6:00 AM

Post #3 of 7 (4145 views)
Permalink
Re: N800 won't connect via WPA2...says "network does not support" [In reply to]

Mike Klein wrote:
> Addnly I am using WRT54GL w/DD-WRT firmware (v24-RC1). I can certainly
> try an update of dd-wrt firmware as well....unfortunately earlier today
> I bricked my primary 54gl and am now on backup unit....thk goodness I
> had a spare. So the router firmware update may have to wait until get
> another backup unit...only $60 so no biggie.
>
> Unless my 8525 is lying (certainly possible...perhaps hidden fallback to
> WPA?)...my network DOES support wpa2.

I believe it *is* a fallback. I had reports from a Mac user that getting
into the campus network (which *is* WPA) involved switching to WPA2. On
investigation this turned out to be that the WPA driver in Vista was
buggy, so everything was set up using the WPA2 drivers, and all users
were configured for this, *including* Mac users (!) even though the
connection didn't actually use any WPA2 features. On the same network,
my Gutsy connects with N-M using plain WPA. I'm not any kind of expert
in this, so I'm just reproducing what the networking gureaux have told
me. YMMV. The N800 absolutely will *not* connect to the WPA network in
the current circumstances (I have yet to try it with certificates).

I wish there was some kind of step-by-step trace mode for connections
that would show the exchange of information between AP and client.

///Peter
_______________________________________________
maemo-users mailing list
maemo-users [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-users


zkolic at sbb

Oct 28, 2007, 7:22 AM

Post #4 of 7 (4148 views)
Permalink
Re: N800 won't connect via WPA2...says "network does not support" [In reply to]

> But this is bunk as my WM5 8525 connects via WPA2/AES! This totally
> blows me away...WM?!?
> I notice my ST5111 atheros client has only "WPA/WPA2" option (no manual
> select) and it seems to fallback to WPA/AES.
> I am one release back from current firmware (the sdhc fix).

I could confirm that wrt54gl supports wpa2 with aes encryption.
Knowing that, you have to calmly find the way around. First, let
the channel be 6 or 11. Then, go to just "g" mode emission. Let
your mac address pass the firewall on the device. Set the appropriate
password, at least 65 long. Set ssid to hidden. Then... Let wizard
on n800 help you. Include hidden ssid as very important. On 770
I made the connection from the very first attempt.
Atheros chip is known as good for open source drivers. I have
5212 on freebsd box and it works just flowlessly. Linux drivers
are similar, with no time outs or alike funs.

Zoran

_______________________________________________
maemo-users mailing list
maemo-users [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-users


mklein at vxappliance

Oct 28, 2007, 10:09 AM

Post #5 of 7 (4156 views)
Permalink
Re: N800 won't connect via WPA2...says "network does not support" [In reply to]

Thanks for help all.

I managed to unbrick my wrt54gl (tftp via orig. linksys firmware at
reboot of unit...whew!) and got onto v24RC4 (was on rc1). This and a
reboot after configuring for "WPA2Mixed/TKIP+AES" yields the following
results:

8525 (WM5): Connect via WPA2/AES (at least it says so)
N800: Connect only via WPA (wpa2 still yields network msg)...not sure
whether tkip or aes.
ST5111 (WinXP): Now (After router reboot) uses WPA/AES and not
tkip...but still no wpa2.
Tried Msoft and Athereos...only atheros had wpa2 option...but it
falls back to wpa.
Inspiron (WinXP): WPA-PSK/AES (not even option for wpa2)

So firmware upgrade only yielded ability to use AES whereas before all
clients were tkip. The router reboot after making settings changes may
have done this actually. dd-wrt seems to get a little confused when
you're in the ui going and forth between ssid hidden/visible and making
security changes.

I will start looking for dd-wrt bug/changelist (they don't bundle with
firmware downloads?!?) and am of belief now that (perhaps) WM5 is
"falling back" to WPA...although I do have it explicitly set to WPA2 and
not WPA. I wouldn't think fallback would NOT occur in this case as there
is specific selection for wpa2. Oddly enough my tablet pc (st5111) only
has WPA2/WPA option...wpa2 cannot be forced.

[side note]
dd-wrt is so flexible now. I could setup virtual ssid (all are hidden)
for my wife's old WEP-only laptop and further restrict access by macid.
I am even restricting by macid on wpa2 ssid as well. N800 is in these
lists although it's hostname doesn't show up in wifi list.

What was I thinking reflashing my primary AP first and not my backup
unit...that's what it's there for...doh!
[/side note]


mike

Zoran Kolic wrote:
>> But this is bunk as my WM5 8525 connects via WPA2/AES! This totally
>> blows me away...WM?!?
>> I notice my ST5111 atheros client has only "WPA/WPA2" option (no manual
>> select) and it seems to fallback to WPA/AES.
>> I am one release back from current firmware (the sdhc fix).
>>
>
> I could confirm that wrt54gl supports wpa2 with aes encryption.
> Knowing that, you have to calmly find the way around. First, let
> the channel be 6 or 11. Then, go to just "g" mode emission. Let
> your mac address pass the firewall on the device. Set the appropriate
> password, at least 65 long. Set ssid to hidden. Then... Let wizard
> on n800 help you. Include hidden ssid as very important. On 770
> I made the connection from the very first attempt.
> Atheros chip is known as good for open source drivers. I have
> 5212 on freebsd box and it works just flowlessly. Linux drivers
> are similar, with no time outs or alike funs.
>
> Zoran
>
> _______________________________________________
> maemo-users mailing list
> maemo-users [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-users
>


mklein at vxappliance

Oct 28, 2007, 11:44 AM

Post #6 of 7 (4157 views)
Permalink
Re: N800 won't connect via WPA2...says "network does not support" [In reply to]

I now have WPA2 (aes?) forced on N800 and it works.

Apparently dd-wrt in "wpa2 mixed" mode wasn't compatible with N800 scheme.

I've been working with Winbloze for 20 years? now and didn't know there
were updates outside of Windows Update?

I had no ability for wpa2 on my xp tabletpc or wifey's xp laptop...only
wpa. Atheros provided wpa2 but I preferred using std windows. After some
googling I found various hotfixes for XP SP2 that are outside of Windows
Update mechanism....why? How the heck do you find out about these other
than knowing you need them and googling?

After applying hotfix dd-wrt is now set for "wpa2/aes only"....and all
clients are on strongest except for wife's "legacy" (ahem) laptop.

My last option to try was shortening the wpa2 passphrase....it is fairly
large and I heard there were issues with this.


thanks all for help/suggestions...all is well again.

mike
_______________________________________________
maemo-users mailing list
maemo-users [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-users


james at linuxrebel

Oct 28, 2007, 8:43 PM

Post #7 of 7 (4137 views)
Permalink
Re: N800 won't connect via WPA2...says "network does not support" [In reply to]

On Sunday 28 October 2007 10:09:24 Mike Klein wrote:
> Thanks for help all.
>
> I managed to unbrick my wrt54gl (tftp via orig. linksys firmware at
> reboot of unit...whew!) and got onto v24RC4 (was on rc1). This and a
> reboot after configuring for "WPA2Mixed/TKIP+AES" yields the following
> results:
>
> 8525 (WM5): Connect via WPA2/AES (at least it says so)
> N800: Connect only via WPA (wpa2 still yields network msg)...not sure
> whether tkip or aes.
> ST5111 (WinXP): Now (After router reboot) uses WPA/AES and not
> tkip...but still no wpa2.
> Tried Msoft and Athereos...only atheros had wpa2 option...but it
> falls back to wpa.
> Inspiron (WinXP): WPA-PSK/AES (not even option for wpa2)
>
> So firmware upgrade only yielded ability to use AES whereas before all
> clients were tkip. The router reboot after making settings changes may
> have done this actually. dd-wrt seems to get a little confused when
> you're in the ui going and forth between ssid hidden/visible and making
> security changes.
>
> I will start looking for dd-wrt bug/changelist (they don't bundle with
> firmware downloads?!?) and am of belief now that (perhaps) WM5 is
> "falling back" to WPA...although I do have it explicitly set to WPA2 and
> not WPA. I wouldn't think fallback would NOT occur in this case as there
> is specific selection for wpa2. Oddly enough my tablet pc (st5111) only
> has WPA2/WPA option...wpa2 cannot be forced.
>
> [side note]
> dd-wrt is so flexible now. I could setup virtual ssid (all are hidden)
> for my wife's old WEP-only laptop and further restrict access by macid.
> I am even restricting by macid on wpa2 ssid as well. N800 is in these
> lists although it's hostname doesn't show up in wifi list.
>
> What was I thinking reflashing my primary AP first and not my backup
> unit...that's what it's there for...doh!
> [/side note]
>
>
> mike

Mike I like to think of doing this kind of thing as a desire to live
dagerously and an inward urge to really chew my own a$$ out. *grin*

James
_______________________________________________
maemo-users mailing list
maemo-users [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-users

Maemo users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.