kernel-packages team mailing list archive

Thread
Date

[Bug 1017738] Re: NM fails to connect Wi-Fi; dhclient works -- Intel Centrino Wireless-N 1000 iwlwifi

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: jerrylamos <jerrylamos@xxxxxxxxxxxx>
Date: Tue, 27 Aug 2013 01:55:32 -0000
Reply-to: Bug 1017738 <1017738@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug is still present on latest Saucy Salamander 3.11.0-3.
On the same WPA encrypted network:
Precise on the same hardware boots up and connects automatically.
Nook HD+ boots up and connects autmatically even faster.
Asus Transformer TF101 boots up and connects automatically.
Samsung Galaxy Tab 2 7" boots up and connects automatically.
Boot Saucy and it "Disconnects" automatically.
1. Select internet applet.
2, Select connect to hidden wireless network.
3. Drop down window to show the networks.
4. Select the only network listed which Saucy had stored already.
5. Select connect to network.
Note, did not have to enter the network name, Ubuntu had it already.
Note, did not have to enter the encryption key, Ubuntu had it already.
Why did network manager decide not to use the info it had? Has to be a policy decision since it used to work.
Five manual mouse actions to do what Ubuntu's competition does automatically, and much faster.
Oh, on two different pc's same trouble. Ubuntu used to connect automatically, now it disconnects automatically.
Perhaps it might be worthwhile for ubuntu to look how easily the competition works....
BTW, I have tried the upstream kernel. Debian Development says their kernel has no problem, it authenticates as soon as Ubuntu asks it to.
Crawling through the syslogs etc. Saucy kernel authenticates as soon as it is asked to.
Saucy Network Manager tries to connect without using the key, of course it doesn't work, decides the network is out of range, it is not. Network Manager already has the key, knows it has the key, then and decides not to use it. ??

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1017738

Title:
NM fails to connect Wi-Fi; dhclient works -- Intel Centrino Wireless-N
1000 iwlwifi

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
Wireless WPA fails to "automatically connect" even though "enable
wireless" is on when rebooting.

Systems Settings Network is blank where it should have the network
name. That's a bug.

Correctly says wired network is unplugged.

Network Applet Edit Connections says wired connection last used 5
minutes ago. Has not been plugged in since yesterday. That's a bug.

Network Applet Edit Connections says wireless connection last used 2
hours ago. Not true, last used 5 minutes ago. That's a bug.

Selecting Network Applet Edit Connections Wireless Security tab should
ask for pathword authorization to set/change password. It does not.
That's a bug.

What the Wireless Security tab does is just sit there for a couple
minutes then (60 to 120 seconds) the menu appears. All the correct
data is already there. Save, close. No changes made.

Wireless WPA still does not connect even though it was running before
reboot. "connect automatically" does not. That's a bug.

Systems Settings Network still shows no network name while network applit edit connections shows the correct name.
Why don't they both show the same network name? That's a bug.

After 20 minutes, it suddenly does show the network name. Some time
after that the wireless WPA connects.

No new information was used. It already had network name, security
type, and password when it rebooted. "cinnect automatically" does
not. That's a bug.

Any clue what to do to "automatically connect"? This is a
"Regression" since Precise works very usably on the same hardware.

Jerry

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: network-manager 0.9.4.0+git201206081144.2efeac8-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic i686
ApportVersion: 2.2.5-0ubuntu1
Architecture: i386
Date: Mon Jun 25 18:39:51 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120625)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.3-0ubuntu4
Architecture: i386
DistroRelease: Ubuntu 12.10
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120708.1)
IpRoute:
default via 192.168.0.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.7 metric 9
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
Package: network-manager 0.9.4.0+git201206081144.2efeac8-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Tags: quantal running-unity
Uname: Linux 3.5.0-4-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
Wired connection 1 db29e980-6d85-4cd3-8f83-c4252d4f3755 802-3-ethernet 1342096724 Thu 12 Jul 2012 08:38:44 AM EDT yes no /org/freedesktop/NetworkManager/Settings/1
LAUREL 28dda2b6-dcd4-4a4d-8b33-6d4d1d9d99b5 802-11-wireless 1342097083 Thu 12 Jul 2012 08:44:43 AM EDT 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 disabled

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