[Hardy] [madwifi] fails to associate using /e/n/i

[Matthew Tighe]

A config that worked in Gutsy for connecting to a corporate network did work in Hardy for me yesterday. I also tried the new improved gui nm-applet with no love there either (although it did "see" the wireless network I was trying to connect to - which was huge improvement from gutsy).

/etc/wpa_supplicant/wpa_supplicant.conf:

network={
        ssid="CORPWiFi"
        scan_ssid=1
        key_mgmt=IEEE8021X
        eap=PEAP
        identity="domain\user_n"
        password="Password"
}

/etc/interfaces:

auto lo
iface lo inet loopback
iface eth0 inet dhcp
auto eth0
auto wlan0
iface wlan0 inet dhcp
wpa-driver madwifi
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf.

Don't know what else to say except that it DID work under Gutsy but not under Hardy. It seemed like Hardy was just ignoring it.

[Matthew Tighe (tighem)]

That trailing period is not in the config file at the end of "wpa_supplicant.conf".

[Reinhard Tartler (siretart)]

that part didn't change in wpasupplicant. Could you please run wpasupplicant by hand using heavy debug (use -dd as parameters) and attach that to this bug, please.

Alas, please say the exact version of wpasupplicant you are using (output of `dpkg -l wpasupplicant`)

[Matthew Tighe (tighem)]

tighem@met:~$ dpkg -l wpasupplicant
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii wpasupplicant 0.6.0+0.5.8-0u Client support for WPA and WPA2 (IEEE 802.11
tighem@met:~$ sudo wpa_supplicant -iwlan0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf -dd > corpnetwifidebug.txt

[ubuntu_demon (ubuntu-demon)]

I reported a similar issue here :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/220640

[Reinhard Tartler (siretart)]

the relevant part of the debug log is this:

Trying to associate with 00:13:19:92:46:b0 (SSID='CorpNetWiFi' freq=2427 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=23
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:13:19:92:46:b0 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED

[Reinhard Tartler (siretart)]

oh, now I see that you are using 'madwifi' as driver for your card. That driver backend is deprecated by madwifi upstream.

Could you please try with 'wext' again? I'd need to see a new debug (-dd) log again.

[Jayson Rowe (jayson.rowe)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!