NA: Thanks. So this is the relevant part of the logs, and seem to be consistently hitting the same issue:
May 29 11:19:13 uma-desktop wpa_supplicant[1087]: State: ASSOCIATED -> 4WAY_HANDSHAKE May 29 11:19:13 uma-desktop wpa_supplicant[1087]: WPA: RX message 1 of 4-Way Handshake from xx:xx:xx:xx:xx:xx (ver=1) May 29 11:19:13 uma-desktop wpa_supplicant[1087]: WPA: PTK derivation - A1=xx:xx:xx:xx:xx:xx A2=xx:xx:xx:xx:xx:xx May 29 11:19:13 uma-desktop wpa_supplicant[1087]: WPA: Sending EAPOL-Key 2/4 May 29 11:19:13 uma-desktop wpa_supplicant[1087]: RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP]) May 29 11:19:13 uma-desktop wpa_supplicant[1087]: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added May 29 11:19:13 uma-desktop wpa_supplicant[1087]: RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP]) May 29 11:19:13 uma-desktop wpa_supplicant[1087]: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added May 29 11:19:13 uma-desktop wpa_supplicant[1087]: RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP]) May 29 11:19:13 uma-desktop wpa_supplicant[1087]: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added May 29 11:19:13 uma-desktop wpa_supplicant[1087]: nl80211: Event message available May 29 11:19:13 uma-desktop wpa_supplicant[1087]: nl80211: Ignore connect event (cmd=46) when using userspace SME May 29 11:19:13 uma-desktop wpa_supplicant[1087]: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1 May 29 11:19:13 uma-desktop NetworkManager[702]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake May 29 11:19:13 uma-desktop kernel: [11049.903355] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903361] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903365] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903369] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903373] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903377] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903380] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903394] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903398] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903402] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903405] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903409] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903412] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903416] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903419] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903423] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903426] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903430] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903434] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903438] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903441] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903445] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903448] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903452] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903455] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule: May 29 11:19:13 uma-desktop kernel: [11049.903459] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903462] cfg80211: Disabling freq 2484 MHz May 29 11:19:13 uma-desktop kernel: [11049.903467] cfg80211: Regulatory domain changed to country: NZ May 29 11:19:13 uma-desktop kernel: [11049.903470] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) May 29 11:19:13 uma-desktop kernel: [11049.903473] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 3000 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903477] cfg80211: (5170000 KHz - 5250000 KHz @ 20000 KHz), (300 mBi, 2300 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903481] cfg80211: (5250000 KHz - 5330000 KHz @ 20000 KHz), (300 mBi, 2300 mBm) May 29 11:19:13 uma-desktop kernel: [11049.903484] cfg80211: (5735000 KHz - 5835000 KHz @ 20000 KHz), (300 mBi, 3000 mBm) May 29 11:19:13 uma-desktop wpa_supplicant[1087]: nl80211: Event message available May 29 11:19:13 uma-desktop wpa_supplicant[1087]: nl80211: Ignored unknown event (cmd=20) May 29 11:19:13 uma-desktop wpa_supplicant[1087]: nl80211: Event message available May 29 11:19:13 uma-desktop wpa_supplicant[1087]: nl80211: MLME event 40 May 29 11:19:13 uma-desktop wpa_supplicant[1087]: Disassociation notification May 29 11:19:13 uma-desktop wpa_supplicant[1087]: SME: Disassociation event received May 29 11:19:13 uma-desktop wpa_supplicant[1087]: SME: Deauthenticate to clear driver state May 29 11:19:13 uma-desktop wpa_supplicant[1087]: wpa_driver_nl80211_deauthenticate May 29 11:19:13 uma-desktop wpa_supplicant[1087]: nl80211: MLME command failed: ret=-107 (Transport endpoint is not connected) May 29 11:19:13 uma-desktop wpa_supplicant[1087]: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 29 11:19:13 uma-desktop wpa_supplicant[1087]: Setting scan request: 0 sec 100000 usec May 29 11:19:13 uma-desktop wpa_supplicant[1087]: BSSID xx:xx:xx:xx:xx:xx blacklist count incremented to 2 May 29 11:19:13 uma-desktop wpa_supplicant[1087]: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=8 What I seem from there is that it seems like it's all disassociations for reason 8 (leaving); all after regulatory domain changes. I'd be tempted to say it's because of the regdomain changes, in which case this would most likely be a driver bug. I'm reassigning this to 'linux'. Some things to think about: if the original auth dialog isn't filled in and just stays open, it's a known NetworkManager bug that more auth dialogs will be opened with new connection attempts. That's left to be fixed (and I'll look for the proper bug number for this). But it remains that there appears to be an issue with WPA authentication with your hardware, and that should be resolved: we'll use this bug report for that. As a next step, it would be useful if you could try a very similar wireless network with no encryption or with just WEP; so we can see if it's specific to WPA or if the regulatory domain gets changed regardless. @Thomas: I'm not trying to police anything there; I just really think we should strongly avoid resorting to such changes unless it's absolutely clear there is an issue directly related to DNS resolution. In this case, I don't think it is: authentication should normally have nothing at all to do with resolution, nor should failed connections like we're seeing. It's all going on at the WPA level AFAICS. It's much safer to get all the necessary files (/run/nm-dns-dnsmasq.conf, checking if dnsmasq is running, the contents of NM's resolvconf interface file, etc.) than having someone change their config, since it means such changes potentially need to be reverted at some point. ** Package changed: wpasupplicant (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Summary changed: - WPA2 Authentication Requested Multiple Times + [rt73usb] WPA2 Authentication Requested Multiple Times -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/999977 Title: [rt73usb] WPA2 Authentication Requested Multiple Times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/999977/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
