Bugzilla – Bug 128957
WLAN with WEP connect only after ejecting PCMCIA card several times
Last modified: 2007-06-05 10:05:12 UTC
My hardware: Asus L3500D notebook with Netgear WG511v1 I've problems to connect to my home accespoint (AVM Fritz Box SL WLAN) with a 128bit WEP connection. I downloaded the firmware, and the LEDs in the WLAN card are blinking. I gave Yast the SSID and the WEP key but the card does not connect. It only works, when I eject the card of the PCMCIA slot several times; then the green LED turns permanently on (which is the normal signal for a connection), then I have to start KInternet, choose my hotspot, enter the WEP key and it connects. With Suse 9.2 it worked perfect, the login was proceeded during system start without any user interference. Before connecting iwconfig gives the following: ------------------------------- linux:/home/daniel # iwconfig lo no wireless extensions. sit0 no wireless extensions. eth0 no wireless extensions. eth1 IEEE 802.11b/g Mode:Managed Frequency:2.427 GHz Access Point: 00:00:00:00:00:00 Bit Rate:0 kb/s Tx-Power=31 dBm Sensitivity=20/200 Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B Encryption key:off Link Quality:2 Signal level:0 Noise level:27 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ---------------- With a succesfull connection it shows (the WEP key is anonymized): ---------------------------- linux:/home/daniel # iwconfig lo no wireless extensions. sit0 no wireless extensions. eth0 no wireless extensions. eth1 IEEE 802.11b/g ESSID:"FRITZ" Mode:Managed Frequency:2.417 GHz Access Point: 00:04:0E:2D:E3:95 Bit Rate:24 Mb/s Tx-Power=31 dBm Sensitivity=20/200 Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Security mode:restricted Link Quality=139/0 Signal level=-69 dBm Noise level=-193 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ---------------------------- I've no idea why it doesn't save the key ... In Yast it's saved
I've had the same problem. There is a problem with wpa_supplicant. If you uninstall the wpa_supplicant package using yast and then reconfigure your eth1 using yast (perhaps you have to remove it first, than restart yast and than configure it) your connection should function. good luck...
There is no need to uninstall wpa_supplicant. Just add PREFER_WPA_SUPPLICANT="no" to /etc/sysconfig/network/ifcfg-wlan-* . But before you do so, could you run 'rcnetwork status' and attach the output?
I ran rcnetwork status two times. The first was shown while it's disconnected and searching for a hotspot - the second when it's connected in "my" way: -------------------- Checking optional network interfaces: eth0 device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90) eth0 configuration: eth-id-00:0e:a6:28:b2:23 eth0 dhcpcd is still waiting for data waiting eth1 device: Intersil Corporation Intersil ISL3890 [Prism GT/Prism Duette] (rev 01) eth1 configuration: wlan-id-00:09:5b:94:d2:bc eth1 dhcpcd is still waiting for data wpa_state=ASSOCIATING Supplicant PAE state=DISCONNECTED suppPortStatus=Unauthorized EAP state=DISABLED waiting Checking mandatory network interfaces: lo IP address: 127.0.0.1/8 running Checking service network . . . . . . . . . . . . . . . running ---------------------------- after I connected in the above described manual way rcnetwork shows: ---------------------------- Checking optional network interfaces: eth0 device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90) eth0 configuration: eth-id-00:0e:a6:28:b2:23 eth0 dhcpcd is still waiting for data waiting eth1 device: Intersil Corporation Intersil ISL3890 [Prism GT/Prism Duet te] (rev 01) eth1 configuration: wlan-id-00:09:5b:94:d2:bc eth1 dhcpcd is still waiting for data wpa_state=ASSOCIATING Supplicant PAE state=DISCONNECTED suppPortStatus=Unauthorized EAP state=DISABLED waiting Checking mandatory network interfaces: lo IP address: 127.0.0.1/8 running Checking service network . . . . . . . . . . . . . . . running linux:/home/daniel # rcnetwork status Checking optional network interfaces: eth0 device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90) eth0 configuration: eth-id-00:0e:a6:28:b2:23 eth0 dhcpcd is still waiting for data waiting eth1 device: Intersil Corporation Intersil ISL3890 [Prism GT/Prism Duet te] (rev 01) eth1 configuration: wlan-id-00:09:5b:94:d2:bc eth1 DHCP client (dhcpcd) is running eth1 IP address: 192.168.178.21/24 eth1 IEEE 802.11b/g ESSID:"FRITZ" Mode:Managed Frequency:2.417 GHz Access Point: 00:04:0E:2D:E3:95 Bit Rate:24 Mb/s Tx-Power=31 dBm Sensitivity=20/200 Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B Encryption key:XXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Security mode:restri cted Link Quality:187/0 Signal level:-74 dBm Noise level:-230 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 running Checking mandatory network interfaces: lo IP address: 127.0.0.1/8 running Checking service network . . . . . . . . . . . . . . . running
This driver (prism54) has incomplete support for wpa_supplicant and therefore it shouldn't be used with that card, that's a bug. I'll fix this in ifup-wireless. PREFER_WPA_SUPPLICANT="no" should work around this bug.
There is a fixed sysconfig package which will be available via YOU soon.