From: Jouni Malinen <jouni.malinen@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] hostAPd operating in 5Ghz channels
Date: Fri, 3 Apr 2009 11:33:17 +0300 [thread overview]
Message-ID: <1238747597.7153.3.camel@jm-desktop> (raw)
In-Reply-To: <7439b3d10904030120k50dbb02bsfb1a5fb3a2a93e73@mail.gmail.com>
On Fri, 2009-04-03 at 01:20 -0700, Giorgio Mazzucchelli wrote:
> Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=17 dBm
> Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=17 dBm
> Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=17 dBm
> Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=17 dBm
> #These are the channels listed by 'iw list' in 5Ghz band:
> Frequencies:
> * 5180 MHz [36] (17.0 dBm)
> * 5200 MHz [40] (17.0 dBm)
> * 5220 MHz [44] (17.0 dBm)
> * 5240 MHz [48] (17.0 dBm)
> * 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
...
> * 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> #So, from channel 52 to 140 where did they gone?
> #Why hostAPd can't see them?
We do not currently support radar detection in ath9k which is required
for these channels. Consequently, hostapd will not allow them to be
enabled. In addition, those passive scanning and no IBSS flags would
also prevent the channel from being used as an AP.
> #These are the frequencies that I should see and use:
>
> country IT:
> (2402 - 2482 @ 40), (N/A, 20)
> (5170 - 5250 @ 40), (N/A, 20)
>
> (5250 - 5330 @ 40), (N/A, 20), DFS
> (5490 - 5710 @ 40), (N/A, 27), DFS
That DFS there indicates the regulatory requirement for detecting radars
and being able to change channels if a radar is present on the selected
channel.
- Jouni
next prev parent reply other threads:[~2009-04-03 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 8:20 [ath9k-devel] hostAPd operating in 5Ghz channels Giorgio Mazzucchelli
2009-04-03 8:33 ` Jouni Malinen [this message]
2009-04-03 21:16 ` Giorgio Mazzucchelli
2009-04-03 21:28 ` Luis R. Rodriguez
2009-04-03 21:31 ` Pavel Roskin
2009-04-03 21:44 ` Giorgio Mazzucchelli
2009-04-03 22:01 ` Luis R. Rodriguez
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=1238747597.7153.3.camel@jm-desktop \
--to=jouni.malinen@atheros.com \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.