From: Pavel Roskin <proski@gnu.org>
To: Alfonso Fiore <alfonso.fiore@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Setting up an AP @ 5 GHz 802.11a - hostapd refuses [Could not select hw_mode and channel. (-1)]
Date: Tue, 7 Feb 2012 17:15:38 -0500 [thread overview]
Message-ID: <20120207171538.3336af0c@mj> (raw)
In-Reply-To: <CAO=xpBGT7ovdSOV77AV6wpUcTDFYr0t8GEab474mVmZm0-BhVA@mail.gmail.com>
On Tue, 7 Feb 2012 09:20:53 +0100
Alfonso Fiore <alfonso.fiore@gmail.com> wrote:
> I also found out about ath_info
> http://madwifi-project.org/wiki/UserDocs/AthInfo and I rewrote my
> regdomain:
> ./ath_info -v -g 4:0 -w 0xeffd0000 regdomain 0x68
That may be dangerous. Not all cards work with ath_info, and some can
be broken by it permanently. It's much safer to adjust
ath_regd_sanitize() in drivers/net/wireless/ath/regd.c.
That way, you can play with different regdomain settings.
> * 2472 MHz [13] (20.0 dBm)
> * 2484 MHz [14] (disabled)
>
> *** But why I still can't access any channel at 5 GHz? *** and what's
> the meaning of (disabled)? Is this due to a hardware limitation?
I believe it's a regdomain limitation.
> This is the situation at 5 Ghz:
> * 5260 MHz [52] (30.0 dBm) (passive scanning,
> no IBSS, radar detection)
I think it means it should be possible to use the band as long as DFS
is implemented, but it's not (in ath5k).
Try other regdomains, I think some should enable 5GHz unconditionally,
but please keep in mind that you may be breaking regulations.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2012-02-07 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 18:46 Setting up an AP @ 5 GHz 802.11a - hostapd refuses [Could not select hw_mode and channel. (-1)] Alfonso Fiore
2012-02-07 8:20 ` Alfonso Fiore
2012-02-07 22:15 ` Pavel Roskin [this message]
2012-02-09 23:06 ` Alfonso Fiore
2012-02-10 6:54 ` Andreas Hartmann
2012-02-10 17:47 ` Alfonso Fiore
2012-02-10 21:15 ` Andreas Hartmann
2012-02-11 1:26 ` Alfonso Fiore
2012-02-11 11:59 ` Andreas Hartmann
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=20120207171538.3336af0c@mj \
--to=proski@gnu.org \
--cc=alfonso.fiore@gmail.com \
--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).