Bug 372926

Summary: dhclient errors out getting dhcp address for ath5k
Product: [openSUSE] openSUSE 11.0 Reporter: JP Rosevear <jpr>
Component: KernelAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None CC: dimstar, sshaw
Version: Alpha 3   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description JP Rosevear 2008-03-21 14:36:50 UTC
Starting WPA2 connection for atheros  with NM causes dhclient error, from /var/log/messages:

Mar 21 10:32:11 gambit klogd: wlan0_rename_re: Initial auth_alg=0
Mar 21 10:32:11 gambit klogd: wlan0_rename_re: authenticate with AP 00:1a:70:df:ed:14
Mar 21 10:32:11 gambit klogd: wlan0_rename_re: RX authentication from 00:1a:70:df:ed:14 (alg=0 transaction=2 status=0)
Mar 21 10:32:11 gambit klogd: wlan0_rename_re: authenticated
Mar 21 10:32:11 gambit klogd: wlan0_rename_re: associate with AP 00:1a:70:df:ed:14
Mar 21 10:32:11 gambit klogd: wlan0_rename_re: RX AssocResp from 00:1a:70:df:ed:14 (capab=0x411 status=0 aid=1)
Mar 21 10:32:11 gambit klogd: wlan0_rename_re: associated
Mar 21 10:32:11 gambit klogd: wlan0_rename_re: switched to long barker preamble (BSSID=00:1a:70:df:ed:14)
Mar 21 10:32:11 gambit klogd: ADDRCONF(NETDEV_CHANGE): wlan0_rename_re: link becomes ready
Mar 21 10:32:11 gambit dhclient: Internet Systems Consortium DHCP Client V3.0.6
Mar 21 10:32:11 gambit dhclient: Copyright 2004-2007 Internet Systems Consortium.
Mar 21 10:32:11 gambit dhclient: All rights reserved.
Mar 21 10:32:11 gambit dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Mar 21 10:32:11 gambit dhclient: 
Mar 21 10:32:11 gambit dhclient: ath0: unknown hardware address type 801
Mar 21 10:32:11 gambit dhclient: ath0: unknown hardware address type 801
Mar 21 10:32:11 gambit dhclient: Bind socket to interface: No such device
Mar 21 10:32:11 gambit dhclient: 
Mar 21 10:32:11 gambit dhclient: If you did not get this software from ftp.isc.org, please
Mar 21 10:32:11 gambit dhclient: get the latest from ftp.isc.org and install that before
Mar 21 10:32:11 gambit dhclient: requesting help.
Mar 21 10:32:11 gambit dhclient: 
Mar 21 10:32:11 gambit dhclient: If you did get this software from ftp.isc.org and have not
Mar 21 10:32:11 gambit dhclient: yet read the README, please read it before requesting help.
Mar 21 10:32:11 gambit dhclient: If you intend to request help from the dhcp-server@isc.org
Mar 21 10:32:11 gambit dhclient: mailing list, please read the section on the README about
Mar 21 10:32:11 gambit dhclient: submitting bug reports and requests for help.
Mar 21 10:32:11 gambit dhclient: 
Mar 21 10:32:11 gambit dhclient: Please do not under any circumstances send requests for
Mar 21 10:32:11 gambit dhclient: help directly to the authors of this software - please
Mar 21 10:32:11 gambit dhclient: send them to the appropriate mailing list as described in
Mar 21 10:32:11 gambit dhclient: the README file.
Mar 21 10:32:11 gambit dhclient: 
Mar 21 10:32:11 gambit dhclient: exiting.

nm-tool shows no ath0 device, the device in question is:
- Device: wlan0_rename_re ----------------------------------------------------------------
  Type:              802.11 Wireless
  Driver:            ath5k_pci
  Active:            no
  HW Address:        00:05:4E:50:1F:7B

  Capabilities:
    Supported:       yes

  Wireless Settings
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points
    23 Robert Hunter:Infra, 00:1A:70:DF:ED:14, Freq 2412 MHz, Rate 54 Mb/s, Strength 70 WPA2
    23 Robert Hunter:Infra, 00:18:39:71:AB:33, Freq 2412 MHz, Rate 54 Mb/s, Strength 50 WPA2
    GRogers:         Infra, 00:1D:7E:46:A3:49, Freq 2437 MHz, Rate 54 Mb/s, Strength 32 WEP

However ifconfig shows both:

ath0      Link encap:UNSPEC  HWaddr 00-05-4E-50-1F-7B-F4-3F-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0_ren Link encap:Ethernet  HWaddr 00:05:4E:50:1F:7B  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4981 (4.8 Kb)  TX bytes:7000 (6.8 Kb)
Comment 1 JP Rosevear 2008-03-21 14:38:05 UTC
From the NM log:

d.
Mar 21 10:32:09 gambit NetworkManager: <info>  Config: added 'ssid' value '23 Robert Hunter'
Mar 21 10:32:09 gambit NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Mar 21 10:32:09 gambit NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Mar 21 10:32:09 gambit NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Mar 21 10:32:09 gambit NetworkManager: <info>  Config: added 'proto' value 'WPA RSN'
Mar 21 10:32:09 gambit NetworkManager: <info>  Config: added 'pairwise' value 'TKIP CCMP'
Mar 21 10:32:09 gambit NetworkManager: <info>  Config: added 'group' value 'WEP40 WEP104 TKIP CCMP'
Mar 21 10:32:09 gambit NetworkManager: <info>  Activation (wlan0_rename_re) Stage 2 of 5 (Device Configure) complete.
Mar 21 10:32:09 gambit NetworkManager: <info>  Config: set interface ap_scan to 1
Mar 21 10:32:09 gambit NetworkManager: <info>  (wlan0_rename_re) Supplicant interface state change: 1 -> 2
Mar 21 10:32:11 gambit NetworkManager: <info>  (wlan0_rename_re) Supplicant interface state change: 2 -> 3
Mar 21 10:32:11 gambit NetworkManager: <info>  (wlan0_rename_re) Supplicant interface state change: 3 -> 4
Mar 21 10:32:11 gambit NetworkManager: <info>  (wlan0_rename_re) Supplicant interface state change: 4 -> 5
Mar 21 10:32:11 gambit NetworkManager: <info>  (wlan0_rename_re) Supplicant interface state change: 5 -> 6
Mar 21 10:32:11 gambit NetworkManager: <info>  (wlan0_rename_re) Supplicant interface state change: 6 -> 7
Mar 21 10:32:11 gambit NetworkManager: <info>  Activation (wlan0_rename_re/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network '23 Robert Hunter'.
Mar 21 10:32:11 gambit NetworkManager: <info>  Activation (wlan0_rename_re) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 21 10:32:11 gambit NetworkManager: <info>  Activation (wlan0_rename_re) Stage 3 of 5 (IP Configure Start) started...
Mar 21 10:32:11 gambit NetworkManager: <info>  Activation (wlan0_rename_re) Beginning DHCP transaction.
Mar 21 10:32:11 gambit NetworkManager: <info>  dhclient started with pid 31753
Mar 21 10:32:11 gambit NetworkManager: <info>  Activation (wlan0_rename_re) Stage 3 of 5 (IP Configure Start) complete.
Mar 21 10:32:11 gambit NetworkManager: <info>  DHCP: device wlan0_rename_re state changed normal exit -> preinit

Mar 21 10:32:56 gambit NetworkManager: <info>  Device 'wlan0_rename_re' DHCP transaction took too long (>45s), stopping it.
Mar 21 10:32:56 gambit NetworkManager: <info>  wlan0_rename_re: canceled DHCP transaction, dhclient pid 31753
Mar 21 10:32:56 gambit NetworkManager: <info>  Activation (wlan0_rename_re) Stage 4 of 5 (IP Configure Timeout) scheduled...
Mar 21 10:32:56 gambit NetworkManager: <info>  Activation (wlan0_rename_re) Stage 4 of 5 (IP Configure Timeout) started...
Mar 21 10:32:56 gambit NetworkManager: <info>  Activation (wlan0_rename_re) failed for access point (23 Robert Hunter)
Mar 21 10:32:56 gambit NetworkManager: <info>  Marking connection 'Auto 23 Robert Hunter' invalid.
Mar 21 10:32:56 gambit NetworkManager: <info>  Activation (wlan0_rename_re) failed.
Mar 21 10:32:56 gambit NetworkManager: <info>  Deactivating device wlan0_rename_re.
Mar 21 10:32:56 gambit NetworkManager: <info>  Activation (wlan0_rename_re) Stage 4 of 5 (IP Configure Timeout) complete.


Comment 2 JP Rosevear 2008-03-21 14:51:24 UTC
Appears to be:
http://madwifi.org/ticket/1767
Comment 3 JP Rosevear 2008-03-21 14:53:24 UTC
From my factory machine:

gambit:~ # dhclient 192.168.1.1 ath0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

ath0: unknown hardware address type 801
SIOCSIFADDR: No such device
192.168.1.1: unknown interface: No such device
192.168.1.1: unknown interface: No such device
ath0: unknown hardware address type 801
Listening on LPF/ath0/
Sending on   LPF/ath0/
Bind socket to interface: No such device

If you did not get this software from ftp.isc.org, please
get the latest from ftp.isc.org and install that before
requesting help.

If you did get this software from ftp.isc.org and have not
yet read the README, please read it before requesting help.
If you intend to request help from the dhcp-server@isc.org
mailing list, please read the section on the README about
submitting bug reports and requests for help.

Please do not under any circumstances send requests for
help directly to the authors of this software - please
send them to the appropriate mailing list as described in
the README file.

exiting.
gambit:~ # rpm -q kernel-default
kernel-default-2.6.25-rc5.git3.6
Comment 4 Dominique Leuenberger 2008-03-24 13:22:09 UTC
I see the same dhclient bailout on my machine. 

I have an ipw2200 wlan card (Intel).
The device it should bind is eth1_rename_ren (only the system itself why it renames the interface twice on every reboot)
Comment 5 JP Rosevear 2008-03-26 15:59:54 UTC

*** This bug has been marked as a duplicate of bug 354141 ***