I have a similar problem with an iwl4965 wireless device. wpa_supplicant works fine with WEP and WPA when I use the device independently, however when it is bonded, only WEP works, and WPA does not. Here is the output from dmesg:
Mar 30 13:20:55 localhost kernel: wlan0: Initial auth_alg=0 Mar 30 13:20:55 localhost kernel: wlan0: authenticate with AP 00:1c:10:41:cd:9e Mar 30 13:20:55 localhost kernel: wlan0: Initial auth_alg=0 Mar 30 13:20:55 localhost kernel: wlan0: authenticate with AP 00:1c:10:41:cd:9e Mar 30 13:20:55 localhost kernel: wlan0: RX authentication from 00:1c:10:41:cd:9e (alg=0 transaction=2 status=0) Mar 30 13:20:55 localhost kernel: wlan0: authenticated Mar 30 13:20:55 localhost kernel: wlan0: associate with AP 00:1c:10:41:cd:9e Mar 30 13:20:55 localhost kernel: wlan0: authentication frame received from 00:1c:10:41:cd:9e, but not in authenticate state - ignored Mar 30 13:20:55 localhost kernel: wlan0: authentication frame received from 00:1c:10:41:cd:9e, but not in authenticate state - ignored Mar 30 13:20:55 localhost kernel: wlan0: RX AssocResp from 00:1c:10:41:cd:9e (capab=0x431 status=0 aid=1) Mar 30 13:20:55 localhost kernel: wlan0: associated Mar 30 13:20:55 localhost kernel: wlan0: switched to long barker preamble (BSSID=00:1c:10:41:cd:9e) Mar 30 13:20:55 localhost kernel: bonding: bond0: link status definitely up for interface wlan0. Mar 30 13:20:59 localhost kernel: wlan0: RX deauthentication from 00:1c:10:41:cd:9e (reason=15) Mar 30 13:20:59 localhost kernel: wlan0: deauthenticated Mar 30 13:20:59 localhost kernel: bonding: bond0: link status definitely down for interface wlan0, disabling it Mar 30 13:21:00 localhost kernel: wlan0: authenticate with AP 00:1c:10:41:cd:9e Mar 30 13:21:00 localhost kernel: wlan0: RX authentication from 00:1c:10:41:cd:9e (alg=0 transaction=2 status=0) Mar 30 13:21:00 localhost kernel: wlan0: authenticated Mar 30 13:21:00 localhost kernel: wlan0: associate with AP 00:1c:10:41:cd:9e Mar 30 13:21:00 localhost kernel: wlan0: RX ReassocResp from 00:1c:10:41:cd:9e (capab=0x431 status=0 aid=1) Mar 30 13:21:00 localhost kernel: wlan0: associated Mar 30 13:21:00 localhost kernel: wlan0: switched to long barker preamble (BSSID=00:1c:10:41:cd:9e) Mar 30 13:21:00 localhost kernel: iwl4965: Error sending REPLY_RXON_ASSOC: Already sending a host command Mar 30 13:21:00 localhost kernel: bonding: bond0: link status definitely up for interface wlan0. Mar 30 13:21:04 localhost kernel: wlan0: RX deauthentication from 00:1c:10:41:cd:9e (reason=15) Mar 30 13:21:04 localhost kernel: wlan0: deauthenticated Mar 30 13:21:04 localhost kernel: bonding: bond0: link status definitely down for interface wlan0, disabling it This repeats in a loop - successful association with the AP, then 4 seconds after the bonding device notes that the wireless link is definitely up, there is a deauthentication with reason=15. As I said above, WEP works just fine, only WPA is failing. WPA works as long as bonding isn't involved. I'm using kernel 2.6.24.1, and have tried with the 2.6.24.1 iwl4965 module, as well as two of the more recent development snapshots from the compat-wireless project. wpasupplicant is version 0.6.3-1 -- wireless network not working now https://bugs.launchpad.net/bugs/99432 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
