Bugzilla – Bug 116955
WLAN not up after reboot
Last modified: 2005-11-07 15:19:21 UTC
I have an "open" 802.11g WLAN connection that I configured via YaST (using an ASCII passphrase for WEP). After YaST is done, the WLAN is operational (via the ipw-2200 driver). However, after a reboot the device is not configured correctly - the DHCP client does not get an IP address, "iwconfig" shows that the WEP key was not set. I have to manually run "iwconfig eth1 key s:xxxxxx open" to get online. This is the /etc/sysconfig/network/ifcfg-wlan-bus-pci-0000:02:02.0 file: [SNIP] BOOTPROTO='dhcp' BROADCAST='' IPADDR='' MTU='' NAME='Intel PRO/Wireless 2200BG' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='LHB6.wqRSB8CC3SF' USERCONTROL='yes' WIRELESS_AP='' WIRELESS_AUTH_MODE='open' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='' WIRELESS_CLIENT_CERT='' WIRELESS_DEFAULT_KEY='0' WIRELESS_ESSID='lenznet' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='s:xxxxxxxx' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_POWER='yes' WIRELESS_WPA_IDENTITY='' WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='' _nm_name='bus-pci-0000:02:02.0' [SNIP] wireless-tools-28pre8-16 wpa_supplicant-0.4.4-2 What other info do you need?
So it did work directly after configuring but not after booting? Strange. Could you check whether /var/run/wpa_supplicant-eth1.conf has the right WEP key? And please also attach 'ifstatus eth1' output.
BTW, the same happens when the system wakes up from a suspend-to-disk - the WEP key is not set.
After a reboot, this is the content of /var/run/wpa_supplicant-eth1.conf: ctrl_interface=/var/run/wpa_supplicant network={ scan_ssid=1 ssid="lenznet" key_mgmt=NONE wep_key0=[SNIP] wep_tx_keyidx=0 } The wep_key0 value corresponds to the numeric value that "iwconfig" displays, when I manually set the key by using "iwconfig eth1 key s:<key> open". However, "iwconfig" does not indicate that a key was set after reboot. "ifstatus eth1" shows: eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05) eth1 configuration: wlan-bus-pci-0000:02:02.0 eth1 dhcpcd is still waiting for data eth1 is up 4: eth1: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0e:35:45:2f:49 brd ff:ff:ff:ff:ff:ff inet6 fe80::20e:35ff:fe45:2f49/64 scope link valid_lft forever preferred_lft forever bssid=00:01:e3:04:a7:8b ssid=lenznet pairwise_cipher=WEP-104 group_cipher=WEP-104 key_mgmt=NONE wpa_state=COMPLETED Supplicant PAE state=UNKNOWN suppPortStatus=Authorized EAP state=IDLE Any additional info I can provide you with?
Once I manually set the key using "iwconfig eth1 key s:<key> open", ifstatus eth1 shows: eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05) eth1 configuration: wlan-bus-pci-0000:02:02.0 eth1 DHCP client (dhcpcd) is running IPADDR=192.168.2.104 NETMASK=255.255.255.0 GATEWAY=192.168.2.1 DNS=192.168.2.1 DHCPSIADDR=0.0.0.0 DHCPCHADDR=00:0E:35:45:2F:49 REBINDTIME=226800 eth1 is up 4: eth1: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0e:35:45:2f:49 brd ff:ff:ff:ff:ff:ff inet 192.168.2.104/24 brd 192.168.2.255 scope global eth1 inet6 fe80::20e:35ff:fe45:2f49/64 scope link valid_lft forever preferred_lft forever eth1 IP address: 192.168.2.104/24 Configured routes for interface eth1: 169.254.0.0 - 255.255.0.0 eth1 Active routes for interface eth1: 192.168.2.0/24 proto kernel scope link src 192.168.2.104 169.254.0.0/16 scope link default via 192.168.2.1 1 of 1 configured routes for interface eth1 up bssid=00:01:e3:04:a7:8b ssid=lenznet pairwise_cipher=WEP-104 group_cipher=WEP-104 key_mgmt=NONE wpa_state=COMPLETED ip_address=192.168.2.104 Supplicant PAE state=UNKNOWN suppPortStatus=Authorized EAP state=FAILURE
I think this bug should be marked as duplicate. It seems to be the same as 115207 (https://bugzilla.novell.com/show_bug.cgi?id=115207). Marc
Yes, I think you're right. *** This bug has been marked as a duplicate of 115207 ***