Ubuntu
network-manager package

Does not connect when router is set to Wireless-N.

Bug #660879 reported by incogneato on 2010-10-15

This bug report is a duplicate of: Bug #630748: iwlagn degrades quickly during normal wifi session. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	network-manager (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: network-manager

Ubuntu connects just fine to the router when it is set to Wireless-G, but when I set it to Wireless-N it keeps trying to connect over and over and never does. The laptop connects to the router set to Wireless N on Windows, so I know that it's not the laptop or the router, but is in fact Linux related.

1) Description: Ubuntu 10.10
Release: 10.10

2) Installed: 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
  Candidate: 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
  Version table:
*** 0.8.1+git.20100810t184654.ab580f4-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

3) I expected to simply connect to my Wireless router at wifi-N speeds.

4) It did not connect, it simply kept trying over and over.

**Extra Information: hardware/driver information from command 'lshw -C network'**
*-network
       description: Wireless interface
       product: Ultimate N WiFi Link 5300
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:06:00.0
       logical name: wlan0
       version: 00
       serial: 00:21:6a:9e:99:b0
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlagn driverversion=2.6.35-22-generic firmware=8.24.2.12 ip=192.168.1.100 latency=0 link=yes multicast=yes wireless=IEEE 802.11abg
       resources: irq:51 memory:d7100000-d7101fff

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Thu Oct 14 20:24:18 2010
EcryptfsInUse: Yes
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IpRoute:
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.100 metric 2
169.254.0.0/16 dev wlan0 scope link metric 1000
default via 192.168.1.1 dev wlan0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: network-manager

Tags:

Revision history for this message

incogneato (incogneato) wrote on 2010-10-15:

Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
Gconf.txt Edit (606 bytes, text/plain; charset="utf-8")
IpAddr.txt Edit (804 bytes, text/plain; charset="utf-8")
IwConfig.txt Edit (557 bytes, text/plain; charset="utf-8")
PciNetwork.txt Edit (1.1 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
WifiSyslog.txt Edit (665.8 KiB, text/plain; charset="utf-8")
nm-system-settings.conf.txt Edit (313 bytes, text/plain; charset="utf-8")

Revision history for this message

Frederik Möllers (fredfredfred) wrote on 2010-10-19:

As the symptoms are the same, this bug is probably a duplicate of bug #630748
A workaround is in the comments there.

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2010-10-19:

Right. Please note comments 8 and 9 on bug 630748. As mentioned above, it's very relevant, so I'm marking this as duplicate since the issue of not being able to connect to a N network if the router is set to accept just N is directly caused by the temporary measure of disabling N support in iwlagn. As soon as the performance degradation issue is really fixed (or anyway, that N support is re-enabled), you should have no issues connecting.