cannot connect to wireless networks using iwl3945 and network-manager

Bug #604845 reported by Andrew Krawchyk
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
dhcp3 (Ubuntu)
Incomplete
High
Unassigned

Bug Description

dmesg output:
[ 87.478612] wlan0: authenticate with 00:xx:xx:xx:xx:xx (try 1)
[ 87.480371] wlan0: authenticated
[ 87.480990] wlan0: associate with 00:xx:xx:xx:xx:xx (try 1)
[ 87.484120] wlan0: RX AssocResp from 00:xx:xx:xx:xx:xx (capab=0x421 status=0 aid=5)
[ 87.484125] wlan0: associated
[ 87.485958] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 87.499428] type=1400 audit(1278983197.082:27): operation="getattr" pid=1834 parent=1010 profile="/sbin/dhclient3" name="/lib/" pid=1834 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 87.499458] type=1400 audit(1278983197.082:28): operation="getattr" pid=1834 parent=1010 profile="/sbin/dhclient3" name="/usr/lib/" pid=1834 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 98.340028] wlan0: no IPv6 routers present
[ 132.650164] wlan0: deauthenticating from 00:xx:xx:xx:xx:xx by local choice (reason=3)
[ 132.674021] cfg80211: All devices are disconnected, going to restore regulatory settings
[ 132.674032] cfg80211: Restoring regulatory settings
[ 132.674038] cfg80211: Calling CRDA to update world regulatory domain
[ 132.678072] cfg80211: World regulatory domain updated:
[ 132.678079] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 132.678086] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 132.678092] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 132.678098] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 132.678103] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 132.678109] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

It looks related to this bug which suggests AppArmor may be the culprit: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/400349. I have tried using WEP, WPA and WPA2 as well as an unsecured network, and nothing works for me. However, my ethernet connection using b44 works which suggests an iwl3945 driver issue. But, if i turn off network-manager, I can connect to my wireless network using "iwconfig wlan0 essid dlink", then dhclient still fails when I run "dhclient wlan0" after it has been connected with iwconfig.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: dhcp3-client 3.1.3-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
Uname: Linux 2.6.35-7-generic x86_64
Architecture: amd64
Date: Mon Jul 12 21:28:04 2010
DhclientLeases:

InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100630)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-7-generic root=/dev/sda3 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: dhcp3

Revision history for this message
Andrew Krawchyk (akrawchyk) wrote :
Revision history for this message
Rasmus Iversen (rasive) wrote :

I think i am having the same issues, dhcp hangs, exactly the same error messages in dmesg.

I attached the output of network-manager --no-daemon

Revision history for this message
Thierry Carrez (ttx) wrote :

Might be an apparmor profile issue. Did you suffer from the same issues in Lucid ? Or is it just a Maverick thing ?

Changed in dhcp3 (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Andrew Krawchyk (akrawchyk) wrote :

This is just a Maverick issue, Lucid could connect to any wirless network I asked it to. I did use the alternative iso to install Maverick (as opposed to the desktop iso for Lucid) so I could test btrfs. I haven't tried using the maverick desktop iso but I can burn one and boot into live ubuntu to see if it still occurs there.

Thierry Carrez (ttx)
tags: added: apparmor
Revision history for this message
Thierry Carrez (ttx) wrote :

Duplicate of bug 599450...
As a workaround, you can disable apparmor (or just the apparmor profile for dhcp3)

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.