linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Morrison <bdm@fenrir.org.uk>
To: linux-wireless@vger.kernel.org
Subject: Re: [ipw3945-devel] iwl3945: Disabled channels
Date: Mon, 21 Apr 2008 10:14:39 +0100	[thread overview]
Message-ID: <480C5AFF.5020005@fenrir.org.uk> (raw)
In-Reply-To: <fuhkfp$mnk$1@ger.gmane.org>

Thomas B=E4chler wrote:
> Using iwl3945 from compat-wireless, I can not use all the channels I=20
> should be allowed to use. In particular, I cannot see some 802.11a=20
> networks which I could see with ipw3945. Here is what I get:
>=20
> iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
>=20
> But:
>=20
> # ./iw dev wlan0 info
> Band 1:
> 	Frequencies:
> 		* 2412 MHz
> 		* 2417 MHz
> 		* 2422 MHz
> 		* 2427 MHz
> 		* 2432 MHz
> 		* 2437 MHz
> 		* 2442 MHz
> 		* 2447 MHz
> 		* 2452 MHz
> 		* 2457 MHz
> 		* 2462 MHz
> 		* 2467 MHz (disabled, passive scanning, no IBSS)
> 		* 2472 MHz (disabled, passive scanning, no IBSS)
> 	Bitrates:
> 		* 1.0 Mbps
> 		* 2.0 Mbps (short preamble supported)
> 		* 5.5 Mbps (short preamble supported)
> 		* 11.0 Mbps (short preamble supported)
> 		* 6.0 Mbps
> 		* 9.0 Mbps
> 		* 12.0 Mbps
> 		* 18.0 Mbps
> 		* 24.0 Mbps
> 		* 36.0 Mbps
> 		* 48.0 Mbps
> 		* 54.0 Mbps
> Band 2:
> 	Frequencies:
> 		* 5170 MHz (disabled, passive scanning, no IBSS)
> 		* 5180 MHz
> 		* 5190 MHz (disabled, passive scanning, no IBSS)
> 		* 5200 MHz
> 		* 5210 MHz (disabled, passive scanning, no IBSS)
> 		* 5220 MHz
> 		* 5230 MHz (disabled, passive scanning, no IBSS)
> 		* 5240 MHz
> 		* 5260 MHz (passive scanning, no IBSS, radar detection)
> 		* 5280 MHz (passive scanning, no IBSS, radar detection)
> 		* 5300 MHz (passive scanning, no IBSS, radar detection)
> 		* 5320 MHz (passive scanning, no IBSS, radar detection)
> 		* 5500 MHz (disabled, passive scanning, no IBSS, radar detection)
> 		* 5520 MHz (disabled, passive scanning, no IBSS, radar detection)
> 		* 5540 MHz (disabled, passive scanning, no IBSS, radar detection)
> 		* 5560 MHz (disabled, passive scanning, no IBSS, radar detection)
> 		* 5580 MHz (disabled, passive scanning, no IBSS, radar detection)
> 		* 5600 MHz (disabled, passive scanning, no IBSS, radar detection)
> 		* 5620 MHz (disabled, passive scanning, no IBSS, radar detection)
> 		* 5640 MHz (disabled, passive scanning, no IBSS, radar detection)
> 		* 5660 MHz (disabled, passive scanning, no IBSS, radar detection)
> 		* 5680 MHz (disabled, passive scanning, no IBSS, radar detection)
> 		* 5700 MHz (disabled, passive scanning, no IBSS, radar detection)
> 	Bitrates:
> 		* 6.0 Mbps
> 		* 9.0 Mbps
> 		* 12.0 Mbps
> 		* 18.0 Mbps
> 		* 24.0 Mbps
> 		* 36.0 Mbps
> 		* 48.0 Mbps
> 		* 54.0 Mbps
>=20
> Most of the 802.11a channels are disabled, as are channel 12 and 13 i=
n=20
> the 802.11g band (I am sure those 11g channels should be enabled).

If you're in the EU, I contributed a fix that has not yet made it into=20
the iwlwifi code as it is under review (the whole regulatory aspect is=20
difficult, there are so many caveats!).

Temporarily I'd suggest that you add:

options cfg80211 ieee80211_regdom=3D"JP"

into your /etc/modprobe.conf as it will enable the 2.4GHz channel 12 an=
d=20
13 for you, I'm not sure that the 802.11a channels will be correct, but=
=20
it's better than it was.

Eventually this should become:

options cfg80211 ieee80211_regdom=3D"EU"

once things are correctly defined again. But it may take a little while=
=2E=20
I need to check what's in 2.6.25 before I think about tweaking my patch=
,=20
but it will depend on John Linville as to whether it goes in to the=20
mainline kernel.

All a bit tricky!

A look here would be useful as a starting point:

http://en.wikipedia.org/wiki/List_of_WLAN_channels

but be aware there is a lot of legislation that affects the available=20
frequencies and it's not easy to get an overview of what is and isn't=20
allowed.

--=20

Brian

--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2008-04-21  9:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fuhkfp$mnk$1@ger.gmane.org>
2008-04-21  9:14 ` Brian Morrison [this message]
2008-04-21 13:50   ` [ipw3945-devel] iwl3945: Disabled channels Johannes Berg
2008-04-21 14:19     ` Brian Morrison
2008-04-21 14:41       ` Johannes Berg
2008-04-21 15:01         ` Brian Morrison
2008-04-21 15:12           ` Johannes Berg
2008-04-21 15:36             ` Brian Morrison
2008-04-21 14:28     ` Brian Morrison
2008-04-21 15:38   ` Thomas Bächler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=480C5AFF.5020005@fenrir.org.uk \
    --to=bdm@fenrir.org.uk \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).