Bugzilla – Bug 115207
WEP key lost at each start
Last modified: 2007-06-05 10:05:11 UTC
At each start, the WEP key of my WIFI network isn't in memory. I must enter it each time. This problem doesn't exists in beta 3.
Please attach /var/log/messages and 'hwinfo --netcard' output.
/var/log/messages makes 5,5mo ! The start is : Sep 4 12:00:05 linux syslog-ng[4413]: new configuration initialized Sep 4 12:00:05 linux syslog-ng[4413]: Changing permissions on special file /dev/xconsole Sep 4 12:00:05 linux syslog-ng[4413]: Changing permissions on special file /dev/tty10 Sep 4 12:00:05 linux kernel: Asus ACPI: Error reading LCD status Sep 4 12:00:05 linux kernel: Asus ACPI: Error reading LCD status Sep 4 12:00:05 linux kernel: Asus ACPI: Error reading LCD status Sep 4 12:00:05 linux kernel: Asus ACPI: Error reading LCD status ... This last line is repeat every second ! ----------------------------- This is hwinfo --netcard : 24: PCI 200.0: 0200 Ethernet controller [Created at pci.277] UDI: /org/freedesktop/Hal/devices/pci_10ec_8139 Unique ID: rBUF.SMQak7ZBX+8 Parent ID: 6NW+.1yBhv2xnpj4 SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: network Model: "ASUSTeK RTL-8139/8139C/8139C+" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8139 "RTL-8139/8139C/8139C+" SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1045 Revision: 0x10 Driver: "8139too" Device File: eth0 I/O Ports: 0xc800-0xc8ff (rw) Memory Range: 0xfeaffc00-0xfeaffcff (rw,non-prefetchable) IRQ: 185 (87180 events) HW Address: 00:11:d8:bf:2e:1c Link detected: no Module Alias: "pci:v000010ECd00008139sv00001043sd00001045bc02sc00i00" Driver Info #0: Driver Status: 8139too is active Driver Activation Cmd: "modprobe 8139too" Driver Info #1: Driver Status: 8139cp is active Driver Activation Cmd: "modprobe 8139cp" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #18 (PCI bridge) 25: PCI 204.0: 0282 WLAN controller [Created at pci.277] UDI: /org/freedesktop/Hal/devices/pci_8086_4220 Unique ID: JNkJ.9J1F3mK3OuC Parent ID: 6NW+.1yBhv2xnpj4 SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:04.0 SysFS BusID: 0000:02:04.0 Hardware Class: network Model: "Intel PRO/Wireless 2200BG" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x4220 "PRO/Wireless 2200BG" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x2701 Revision: 0x05 Driver: "ipw2200" Device File: eth1 Features: WLAN Memory Range: 0xfeafe000-0xfeafefff (rw,non-prefetchable) IRQ: 185 (87180 events) HW Address: 00:12:f0:20:ae:39 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54 WLAN encryption modes: WEP40 WEP104 WLAN authentication modes: open sharedkey Requires: ipw-firmware Module Alias: "pci:v00008086d00004220sv00008086sd00002701bc02sc80i00" Driver Info #0: Driver Status: ipw2200 is active Driver Activation Cmd: "modprobe ipw2200" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #18 (PCI bridge)
We don't need /var/log/messages necessarily. But please attach your /etc/sysconfig/network/ifcfg-wlan-* and the output of 'ifup eth1'.
Created attachment 48800 [details] ifcfg-wlan
ifup eth1 gives : ifup eth1 eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05) eth1 configuration: wlan-bus-pci-0000:02:04.0 eth1 warning: wpa_supplicant already running on interface SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... SuSEfirewall2: batch committing... SuSEfirewall2: Firewall rules successfully set
Your interface configuration has the WEP key set, and ifup finds the configuration on startup. So I can't see the problem. Please describe what's not working.
Effectively, now it's working but if I restart the computer, the WEP key will be lost and I must re-enter it.
What do you mean with 'the WEP key will be lost and I must re-enter it'? The ifcfg-file has your key, so it can't get lost. Maybe your network does not get set up correctly. To check this it would be useful if you could run 'rcnetwork status eth1' and 'rcnetwork start eth1' directly after booting without re-enter your WEP key. Btw, how do you re-enter your key? Using YaST or iwconfig?
I'm using the applet Kinternet. * rcnetwork status eth1 : eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05) eth1 configuration: wlan-bus-pci-0000:02:04.0 eth1 IP address: 192.168.0.101/24 bssid=00:07:cb:52:03:ed ssid=maison pairwise_cipher=WEP-104 group_cipher=WEP-104 key_mgmt=NONE wpa_state=COMPLETED ip_address=192.168.0.101 Supplicant PAE state=UNKNOWN suppPortStatus=Authorized EAP state=FAILURE running Checking service network . . . . . . . . . . . . . . . running * rcnetwork start eth1 : Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05) eth1 configuration: wlan-bus-pci-0000:02:04.0 eth1 warning: wpa_supplicant already running on interface eth1 IP address: 192.168.0.101/24 done SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... SuSEfirewall2: batch committing... SuSEfirewall2: Firewall rules successfully set
Kinternet does not save your WEP key. Besides that, kinternet is broken in conjunction with wpa_supplicant up to beta4. Does your connection work when configured directly in YaST?
It's the same with YAST. I've just seen that if at start, I disconnect and then reconnect, the network works (without enter the wep key).
This problem still exists in RC1. But now I cannot disconnect/reconnect with the applet. And WEP key is no more in memory at start. And now I must also do a "ifdown eth0" and a "ifup eth1" at each start...
Same problem here. By the way there's one line when issuing "dmesg" that says: ieee80211_crypt_wep: module not supported by Novell, setting U taint flag. ieee80211_crypt: registered algorithm 'WEP' I don't know if it's related to this problem.
*** Bug 117736 has been marked as a duplicate of this bug. ***
Does the problem still exist in 10.0 final?
A problem still exists but it is less important and I don't know if it's exactly the same one... Now, with the 10 final, I must disconnect and then reconnect to make my wifi connection works (I use the Kinternet's applet to do this). Any ideas ?
*** Bug 116955 has been marked as a duplicate of this bug. ***
Could you test whether a newer version of wpa_supplicant helps? I'll attach a package. If it doesn't, adding PREFER_WPA_SUPPLICANT='no' to /etc/sysconfig/network/ifcfg-wlan-* may work around it.
Created attachment 56591 [details] updated wpa_supplicant install with 'rpm -Uhv ...'
With the RPM, it doesn't work more. But with the RPM and the line PREFER_WPA_SUPPLICANT='no', it works ! Thanks ;-) Will this be automaticly available by YOU ?
Probably not, as there is a work-around. Are you willing to do another test? Could you add WIRELESS_AP_SCANMODE='2' to your ifcfg-file and restart the network? PREFER_WPA_SUPPLICANT needs to be "yes" (or empty) for this test.
Works for me with this new settings (I've leave the RPM).
I've change the PREFER_WPA_SUPPLICANT default to "no" in 10.1.