linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: p4u <hakais@gmail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: IBSS channel support
Date: Fri, 29 Jul 2011 18:07:34 +0200	[thread overview]
Message-ID: <4E32DAC6.7030308@gmail.com> (raw)
In-Reply-To: <1311954873.3084.2.camel@dcbw.foobar.com>

Thanks.
I think I can use it

On 29/07/11 17:54, Dan Williams wrote:
> On Fri, 2011-07-29 at 17:27 +0200, p4u wrote:
>> Hi,
>> This is my first mail to this list, I'm Pau from Barcelona working in
>> guifi.net (wireless community)
>> First of all I want to say thank you guys for your amazing job :-)
>>
>> Now, I have a little question. Using command "iw phy phy0 info" I can
>> see that IBSS mode is only avaiable in some channels for 5ghz spectrum.
>> I have been looking for information about it, but I cannot find from
>> what depends if some channel can by used in IBSS mode or not. So I think
>> it depends on the driver and on the regdomain, is it right?
> Yes.
>
>> Also I'm working in some scripts, and I need to know if a channel has
>> IBSS support or not. The only way I found is with iw command, but pharse
>> this data is very dirty. Furthermore I can read in the end of iw help:
>>
>> "Do NOT screenscrape this tool, we don't consider its output stable."
>>
>> So I need another way to get this information. Any idea?
> Couldn't you use the CRDA database?  That's got bits that indicate
> whether or not some channels allow IBSS in your domain or not.
>
> http://wireless.kernel.org/download/wireless-regdb/
>
> Dan
>
>


-- 
./p4u


  reply	other threads:[~2011-07-29 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 15:27 IBSS channel support p4u
2011-07-29 15:54 ` Dan Williams
2011-07-29 16:07   ` p4u [this message]
2011-08-08  8:41 ` Johannes Berg

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=4E32DAC6.7030308@gmail.com \
    --to=hakais@gmail.com \
    --cc=dcbw@redhat.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).