NetworkManager fails to open wlan0 after successfully authenticating against access points

Bug #1144720 reported by Thomas Schweikle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

NetworkManager fails to connect to various wireless networks. All times the same: it authenticates successfully against the access point, obtains an IP-Address, then disconnects because of "reason 3". This is done over and over again. In between having obtained an IP-Address and then disconnecting again you'll have full access to the network. Then again no access to the network, access, no access, access, no access.

If you are able to kill NetworkManager and wpa_supplicant while you have access to the network, it will work until the access point requests you to authenticate again (?).

Taking wicd and disabling NetworkManager the whole thing works. Only drawback: the WiFI-LED will constantly blink, instead being light constantly if connected.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4.2
Uname: Linux 3.4.34 x86_64
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Mon Mar 4 17:27:53 2013
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=de_DE:en
 TERM=screen-bce
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-07-16 (230 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-03T12:29:43.912070
mtime.conffile..etc.init.network.manager.conf: 2013-03-04T17:15:37.443693
nmcli-con:
 Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9:
 ** (process:18348): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files
 Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running.
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 not running unknown unknown unknown unknown unknown unknown unknown

Revision history for this message
Thomas Schweikle (tps) wrote :
Revision history for this message
Thomas Schweikle (tps) wrote :

The NetworkManager file "/etc/NetworkManager/NetworkManager.conf was edited and the line "managed=false" added, as expected by various tips – I had to notice, this having no effect at all. NetworkManager still tried to manage all Network equipment. Only renaming "/usr/sbin/NetworkManager" to "/usr/sbin/NetworkManager.dontuse" made the system not starting this peace of software.
Afterwards I disabled /etc/init/network-manager.conf by commenting out the "start" line.

Revision history for this message
Thomas Schweikle (tps) wrote :

Further testing gave the following:
- Ubuntu 10.10 - NetworkManager configures wlan0, obtains an IP, then disconnects because of "reason 3"
- Ubuntu 11.04 - NetworkManager configures wlan0, obtains an IP, then disconnects because of "reason 3"
- Ubuntu 11.10 - NetworkManager configures wlan0, obtains an IP, then disconnects because of "reason 3"
- Ubuntu 12.04 - NetworkManager configures wlan0, obtains an IP, then disconnects because of "reason 3"
- Ubuntu 12.04.2 - NetworkManager configures wlan0, obtains an IP, then disconnects because of "reason 3"
- Ubuntu 13.04 - NetworkManager configures wlan0, obtains an IP, then disconnects because of "reason 3"

The bug is known since Ubuntu 10.10! (at least) it is not fixed. It is there with the default install if using NetworkManager.

Revision history for this message
Thomas Schweikle (tps) wrote :

This problem further exists.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.