Bugzilla – Bug 128618
[wpa_supplicant] unable to assosiate with AP
Last modified: 2006-02-27 15:31:24 UTC
My config: 1. D-Link DI-614+ router with AP (802.11b) 2. Fujitsu-Siemens Amilo M3438G laptop with ipw2200 3. static IP addresses 4. static WEP key Configuring wireless NIC using YaST goes well. But after configuration done interface does not work. Modules/firmware are loaded, interface is up and IP configured properly, but iwconfig shows that no assosiation made. Here's what happens: barracuda:~ # iwconfig eth1 eth1 unassociated ESSID:"Stealth.Net" Mode:Managed Channel=0 Access Point: 00:0D:88:9B:56:14 Bit Rate=0 kb/s Tx-Power=20 dBm Retry limit:7 RTS thr:off Fragment thr:off Encryption key:0934-3432-9324-2323-4232-3212-12 Security mode:restricted Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:26 Missed beacon:0 and just few seconds later: barracuda:~ # iwconfig eth1 eth1 unassociated ESSID:"Stealth.Net" Mode:Managed Channel=0 Access Point: 00:0D:88:9B:56:14 Bit Rate=0 kb/s Tx-Power=20 dBm Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:26 Missed beacon:0 barracuda:~ # wpa_supplicant process runs infinitely, trying to authentificate with no success. BTW, it uses wireless-extensions driver (-Dwext) but should use ipw with ipw2100/2200 cards (-Dipw). After I change wext to ipw in /etc/sysconfig/network/scripts/ifup-wireless (639 line, WPA_DRIVER) network restart outputs the following: barracuda:~ # rcnetwork restart eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05) eth1 configuration: wlan-bus-pci-0000:01:03.0 eth1 is controlled by ifplugd ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported done Setting up service network . . . . . . . . . . . . . . done barracuda:~ #
SL 10.0 (and later) already uses Wireless Extensions version 18, so -Dwext is correct. Does it help when you add PREFER_WPA_SUPPLICANT="no" to your /etc/sysconfig/network/ifcfg-wlan-* file?
I don't even have this option in /etc/sysconfig/network/ifcfg-wlan*. I've added it manually and restarted network (rcnetwork restart). Now wpa_supplicant process does not run but there's no luck either. Here's how NIC behaves now: barracuda:~ # iwconfig eth1 eth1 unassociated ESSID:"Stealth.Net" Nickname:"barracuda" Mode:Managed Frequency=2.437 GHz Access Point: 00:0D:88:9B:56:14 Bit Rate=0 kb/s Tx-Power=20 dBm Retry limit:7 RTS thr:off Fragment thr:off Encryption key:0934-3432-9324-2323-4232-3212-12 Security mode:restricted Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 barracuda:~ # iwconfig eth1 eth1 unassociated ESSID:"Stealth.Net" Nickname:"barracuda" Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00 Bit Rate=0 kb/s Tx-Power=20 dBm Retry limit:7 RTS thr:off Fragment thr:off Encryption key:0934-3432-9324-2323-4232-3212-12 Security mode:restricted Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 barracuda:~ # Also power management is not configurable - it's alsays off until manual iwconfig'ing it.
I had this exact problem. By changing the ipw2200 module according to this bug: https://bugzilla.novell.com/show_bug.cgi?id=113634 the cycling stopped, but it is still unassociated... My setup worked perfectly in SuSE 9.3 (Toshiba laptop M200) Any ideas?
Okay, seems that it works in alpha2. I installed ipw-firmware-5-7.noarch.rpm and swithed NIC to "on boot" mode.
*** Bug 153687 has been marked as a duplicate of this bug. ***