WPA problems

OpenSUSE 10.2, Intel 3945 wireless, HP420 AP w/open SSID1 (broadcast)
and WPA SSID2 (not broadcast).

Here's the pattern of the problem.

1) User logs in -- connects automatically to the open SSID.
2) Connect to new wireless network -- enters SSID name, WPA Personal,
enters WPA passphrase, chooses TKIP, Connect
3) Keyring pops up asking for a keyring password -- enters password
4) Connects to SSID2. Works.
5) Re-connects to open SSID1
6) Attempts to re-connect to SSID2 -- sometimes it is listed in NM
memu, sometimes not. If not, has to re-enter info from #2 above.
7) Keyring request does NOT pop up again.
8) Connection fails.

AP logs indicate it is trying to connect back into open SSID1, not use
credentials to connect to SSID2. Cannot re-connect to open side
without restart.

9) Restart and log back in.
10) Open SSID connects.
11) Subsequent attempts to connect to SSID2 fail. Each attempt, have
to enter SSID info from #2 above. Sometimes this is asked twice. SSID2
info sometimes shows up in the NM menu, but not usually after a
failure. Keyring does not ask for password again. Connection attempt
fails. Logs indicate failure connecting to SSID1, but no attempt at 2.

An existing user typically fails. A new user can connect the first
time and then fails after that.

Same pattern seen on SLED 10.

Petty much useless.

Thoughts welcome. Thanks.

Lyle

luzuml@nicc.edu schrieb:
> OpenSUSE 10.2, Intel 3945 wireless, HP420 AP w/open SSID1 (broadcast)
> and WPA SSID2 (not broadcast).

I guess that already explains your problem. Why is SSID broadcast
for SSID2 disabled? Let me have a guess: somebody thought it would
increase security.

Well, it doesn't.

Enable SSID broadcast for all your SSIDs and I bet your problems
will go away.

HTH
Tilman

Wrong guess. HP APs only allow one broadcast SSID.

Lyle

On Fri, 05 Jan 2007 13:15:43 GMT, Tilman Schmidt
<t.schmidt@phoenixsoftware.de> wrote:

>luzuml@nicc.edu schrieb:
>> OpenSUSE 10.2, Intel 3945 wireless, HP420 AP w/open SSID1 (broadcast)
>> and WPA SSID2 (not broadcast).
>
>I guess that already explains your problem. Why is SSID broadcast
>for SSID2 disabled? Let me have a guess: somebody thought it would
>increase security.
>
>Well, it doesn't.
>
>Enable SSID broadcast for all your SSIDs and I bet your problems
>will go away.
>
>HTH
>Tilman

luzuml@nicc.edu schrieb:
> Wrong guess. HP APs only allow one broadcast SSID.

Ouch. Well in that case I'm out of ideas.

Sorry
Tilman

It turns out to be a problem with the shipping ipw3945 driver. Version
1.2.0, according to the bug tracker, addressed just that problem --
not being able to connect to a hidden SSID. We manually replaced 1.1.0
that came with SUSE 10.2 with the beta 1.2.0 version and are testing.
No better so far, but a) we have some other things to check before
passing judgement, and b) having never replaced a wireless driver
before, we can only hope we didn't mess it up. It still connects fine
to the open SSID, so I guess that's a good sign of general driver
replacement success.

Lyle

On Wed, 10 Jan 2007 09:49:09 GMT, Tilman Schmidt
<t.schmidt@phoenixsoftware.de> wrote:

>luzuml@nicc.edu schrieb:
>> Wrong guess. HP APs only allow one broadcast SSID.
>
>Ouch. Well in that case I'm out of ideas.
>
>Sorry
>Tilman