I don't see why the DNS plugin in NetworkManager would make any type of
difference with wireless authentication. Please don't recommend such
changes if it's not relevant to the problem at hard.

The most information we have here is the reason 8 messages just before
the CRDA domain gets re-updated. This is a clue to look into, since it
means "Disassociated because sending STA is leaving (or has left) BSS"
in other words, the client is leaving the access point for some reason.

To further debug this, we'll need wpasupplicant logs. Please run:

sudo python /usr/lib/NetworkManager/debug-helper.py --wpa debug

Then see if you can reproduce the issue. This will add debugging
information from wpasupplicant to /var/log/syslog; so once you can
reproduce the issue with this enabled, please attach the file
/var/log/syslog to this bug report so that it can be reviewed by a
developer.

Thanks!

** Package changed: network-manager (Ubuntu) => wpasupplicant (Ubuntu)

** Changed in: wpasupplicant (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/999977

Title:
  WPA2 Authentication Requested Multiple Times

Status in “wpasupplicant” package in Ubuntu:
  Incomplete

Bug description:
  Connecting to the WiFi LAN the first time when the PC has booted up
  with Ubuntu 12.04 is ok. However after a while there is a
  disconnection from the LAN. When network-manager attempts to reconnect
  it takes a long time before a WPA2 authentication dialog pops up
  asking for the password. After a while the same dialog pops up
  multiple times even though the dialog popped up the first time.

  When entering in the correct password to connect to the LAN via the
  dialog, network-manager takes a long time to connect but pops up with
  the same dialog again. No network connecion is ever made. A temporary
  workaround is to disable networking and re-enable it again from the
  network-manager applet. However if another connection needs to be made
  to the LAN then the same problems occur, and the workaround must be
  used again.

  This authentication issue is serious and if the workaround no longer
  works then the problem becomes a critical one. Noticed the same
  problems occuring on other PCs running Ubuntu 12.04, which use a
  ralink wireless chipset. It appears as though this problem affects all
  Ubuntu 12.04 PCs that use a ralink wirless chipset for WiFi
  networking.

  In the previous Ubuntu LTS version (10.04) the authentication problem
  rarely occured. Initially in Ubuntu 12.04 it was like Ubuntu 10.04 but
  after some updates then authentication problem has become much worse
  (huge regression).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  CRDA:
   country NZ:
        (2402 - 2482 @ 40), (N/A, 30)
        (5170 - 5250 @ 20), (3, 23)
        (5250 - 5330 @ 20), (3, 23), DFS
        (5735 - 5835 @ 20), (3, 30)
  Date: Wed May 16 10:32:10 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.208  
metric 2
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME                      UUID                                   TYPE        
      TIMESTAMP    TIMESTAMP-REAL                     AUTOCONNECT   READONLY   
DBUS-PATH                                 
   Wired connection 1        d2b4065b-4fe9-4d80-8d80-b49fbb471963   
802-3-ethernet    1337115639   Wed 16 May 2012 09:00:39 NZST      yes           
no         /org/freedesktop/NetworkManager/Settings/2
   eaa Manual                01f43cca-69f5-41b4-b7e3-4d1623e18f57   
802-11-wireless   1336354110   Mon 07 May 2012 13:28:30 NZST      yes           
no         /org/freedesktop/NetworkManager/Settings/1
   eaa DHCP                  a23c474e-2ddf-4621-a160-749bfdebd49d   
802-11-wireless   1337121038   Wed 16 May 2012 10:30:38 NZST      yes           
no         /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE     TYPE              STATE         DBUS-PATH                         
         
   wlan0      802-11-wireless   connected     
/org/freedesktop/NetworkManager/Devices/1  
   eth0       802-3-ethernet    unavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING         VERSION    STATE           NET-ENABLED   WIFI-HARDWARE   
WIFI       WWAN-HARDWARE   WWAN      
   running         0.9.4.0    connected       enabled       enabled         
enabled    enabled         enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/999977/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to