Ubuntu

Cannot use wireless channels 12 and 13

Reported by Edward on 2008-09-10
40
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Linux
Invalid
Unknown
linux (Ubuntu)
Undecided
Unassigned
Nominated for Gutsy by Narj
Nominated for Hardy by Narj
Nominated for Intrepid by adso58
Nominated for Jaunty by Narj

Bug Description

Since upgrading to Intrepid, the iwl3945 module (possibly others) cannot access wireless networks on channels 12 or 13 (in Australia, where those channels are permitted). I have read that it may now be necessary to set the ieee80211_regdom parameter on the cfg80211 module for regions that allow the use of channels above 11, but have been unable to produce any result by this method.

Edward (edward-coffey) wrote :
Edward (edward-coffey) wrote :
Edward (edward-coffey) wrote :
Edward (edward-coffey) wrote :

Hi Edward,

The following bug filed upstream might be helpful:

http://intellinuxwireless.org/bugzilla/show_bug.cgi?id=1690

Just out of curiosity, how were you setting the ieee80211_regdom param? Thanks.

Changed in linux:
status: New → Incomplete
Changed in linux:
status: Unknown → Invalid
Edward (edward-coffey) wrote :

Thanks Leann,

I was removing and reinserting cfg80211 on the command-line to adjust the ieee80211_regdom param. What I didn't realise is that it's case-sensitive, so the correct command is:

modprobe cfg80211 ieee80211_regdom=JP

I was using lower-case - "=jp". I've tried "=AU" (Australia) but it doesn't work.

Using the correct case has now allowed me to select channel 13 with iwconfig, but with the ieee80211_regdom set, the network-manager tools aren't seeing any wireless networks at all.

Suzan (suzan72) wrote :

Same for me (here in germany, there this channels area also legal) since I've upgraded to Intrepid Beta yesterday. I use an Intel 3945, I know this is also an issue with 4965 and others.

When setting the channel to 12 or 13, the wireless network don't work, is not even recognized. Setting channel to 11 or lower, everything works OK as before.

For users who live in a country in which channels 12 and 13 are allowed and legal, this is a serious bug, since you cannot connect to every network anymore. Especially because it was no problem before.

syscon-hh (syscon-kono) wrote :

Comparable for me (also located in Germany) - but I'm using the RT2500 and additionally the RT61 Chipset in Intrepid Ibex Installations, Gnome together with nm-applet.

Otherwise as above I can see the Networks using channel 12 and 13, but the nm-applet do not connect anyway.

Florian Schnell (floschnell) wrote :

I do also have this problem, my network ran on channel 13 which wasn't listed on second boot.
First boot after upgrading the network manager even hasn't been started - dunno if this is linked to this bug.
After setting network channel to 9 it was listed, but a connection could only be established after another reboot ...
[ 25.955863] iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
[ 26.000010] iwlagn: Tunable channels: 13 802.11bg, 19 802.11a channels

Christoph Langner (chrissss) wrote :

Why is this Bug Invalid or Incomplete? A lot of people live outside the US. A lot of people use channel 12 and 13 legally. A lot of people who access a WLAN on those channels don't have the the influence that the owner of the user WLAN changes channels.

Changed in linux:
status: Incomplete → Confirmed
Fabus (fabian-gebert-hh) wrote :

Just if somebody is wondering about how to use the workaround with the backported modules: Use this line:
modprobe lbm_cw_cfg80211 ieee80211_regdom=JP
(or EU instead of JP)
You can install the backports using the linux-backports-modules-intrepid package.

Ludwig Baum (ludwigbaum) wrote :

Same problem for me in Germany. I could not connect to a given network on channel 12.

The solution I found:
Add the following line :
options cfg80211 ieee80211_regdom="EU"
in
/etc/modprobe.d/options
As every file in /modprobe.d is read, it should be possible to put that line in a new file.

I'm marking this as a duplicate of bug 288401. Please continue to follow up with this issue at that bug report. Thanks.

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

Other bug subscribers

Remote bug watches

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