wpa_supplicant hangs scanning

Trying to connect wireless using WPA-PSK with ipw3945 driver on Suse
10.2.

I run wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf.
Something's happening, but prompt does not return.

Running wpa_gui shows status of SCANNING.
Console shows ioctl[SIOCGIFADDR]: Cannot assign requested address
...repeats every few seconds
Disconnect in wpa_gui.
Ctrl-C in console stops wpa_supplicant -- Message =
CTRL-EVENT-TERMINATING - signal 2 received.
wpa_gui agrees indicating signal 2 as the last message.

/etc/wpa_supplicant.conf ................
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="SSIDName"
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
group=TKIP
psk="securesecret"
}

Added scan_ssid=1. The debug says it scans for the specific SSID and
gets no response, then falls back to broadcast SSID and finds the
unsecure AP.

wpa_supplicant v0.4.9

Open wireless works fine, XP works on same SSID.

Ideas appreciated. Thanks.

Lyle

luzuml@nicc.edu wrote:
> Trying to connect wireless using WPA-PSK with ipw3945 driver on Suse
> 10.2.
>
> I run wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf.
> Something's happening, but prompt does not return.
>
> Running wpa_gui shows status of SCANNING.
> Console shows ioctl[SIOCGIFADDR]: Cannot assign requested address
> ...repeats every few seconds
> Disconnect in wpa_gui.
> Ctrl-C in console stops wpa_supplicant -- Message =
> CTRL-EVENT-TERMINATING - signal 2 received.
> wpa_gui agrees indicating signal 2 as the last message.
>
> /etc/wpa_supplicant.conf ................
> ctrl_interface=/var/run/wpa_supplicant
>
> network={
> ssid="SSIDName"
> key_mgmt=WPA-PSK
> proto=WPA
> pairwise=TKIP
> group=TKIP
> psk="securesecret"
> }
>
> Added scan_ssid=1. The debug says it scans for the specific SSID and
> gets no response, then falls back to broadcast SSID and finds the
> unsecure AP.
>
> wpa_supplicant v0.4.9
>
> Open wireless works fine, XP works on same SSID.
>
> Ideas appreciated. Thanks.

The command you gave is to run wpa_supplicant in the foreground. If you want it to run as a daemon,
you need to add a -B switch. To debug it, use the foreground command but add a -dd switch to get
debugging information. You should see the handshaking going on.

Larry

If this appears to be a duplicate answer, I tried one from the HTTP forum
reply and didn't see it show up. This is from KNode reader.

Just after I sent off the original question I rebooted. I logged in as root,
entered the keyring password and connected into the secure wireless right
away. I had an address, but couldn't ping anything, so I changed to the
open network and that worked OK. Changed back to secure and again connected
right in, this time with full working connectivity. I logged out and in as
a regular user and still had the secure connection. Again, I switched to
the open side. OK. Cool.

Restarted the machine. Now, logging is as root or user nothing connects --
either open or secure. Have tried several times. No success.

Don't know how it fixed. Don't know how it broke. Bummer.

I did notice that wpa_supplicant seems to be triggered automatically when
the secure connection is attempted. ps aux | grep wpa returned
wpa_supplicant -g -c/etc/wpa_supplicant-global. (I think that path --
that's from memory a few hours ago) Anyway, that is not at all what I typed
manually trying to start it. What's the "-global", anyway?

Also, here's a basic question. In the Yast network config, there is a place
to configure either open or secure and enter the SSID, WPA-PKA, and
passphrase. Should that be configured or left Open? If it is configured
there does that limit to only using WPA or only that SSID? How does that
setting relate to the NM Configure another network settings?

Thanks.

Lyle

Larry Finger wrote:

> The command you gave is to run wpa_supplicant in the foreground. If you
> want it to run as a daemon, you need to add a -B switch. To debug it, use
> the foreground command but add a -dd switch to get debugging information.
> You should see the handshaking going on.
>
> Larry

Luzum wrote:
> If this appears to be a duplicate answer, I tried one from the HTTP forum
> reply and didn't see it show up. This is from KNode reader.
>
> Just after I sent off the original question I rebooted. I logged in as root,
> entered the keyring password and connected into the secure wireless right
> away. I had an address, but couldn't ping anything, so I changed to the
> open network and that worked OK. Changed back to secure and again connected
> right in, this time with full working connectivity. I logged out and in as
> a regular user and still had the secure connection. Again, I switched to
> the open side. OK. Cool.
>
> Restarted the machine. Now, logging is as root or user nothing connects --
> either open or secure. Have tried several times. No success.
>
> Don't know how it fixed. Don't know how it broke. Bummer.
>
> I did notice that wpa_supplicant seems to be triggered automatically when
> the secure connection is attempted. ps aux | grep wpa returned
> wpa_supplicant -g -c/etc/wpa_supplicant-global. (I think that path --
> that's from memory a few hours ago) Anyway, that is not at all what I typed
> manually trying to start it. What's the "-global", anyway?

That must be the name created by the configuration process. I just started running openSuSE 10.2 and
I'm using a wired connection for the moment while I sort out other stuff - it is a new computer.
>
> Also, here's a basic question. In the Yast network config, there is a place
> to configure either open or secure and enter the SSID, WPA-PKA, and
> passphrase. Should that be configured or left Open? If it is configured
> there does that limit to only using WPA or only that SSID? How does that
> setting relate to the NM Configure another network settings?

You probably want to use open authentication. As I'm new with NM, I can't help you yet.

Larry