All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Farina <sidhayn@gmail.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Pavel Roskin <proski@gnu.org>,
	John Linville <linville@tuxdriver.com>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: wireless-regdb: flaw in general functionality
Date: Mon, 24 Nov 2008 21:26:06 -0500	[thread overview]
Message-ID: <492B623E.5030202@gmail.com> (raw)
In-Reply-To: <43e72e890811241526o1ea6ecf7ge05a2319d6ff3641@mail.gmail.com>

Luis R. Rodriguez wrote:
> On Mon, Nov 24, 2008 at 3:21 PM, Pavel Roskin <proski@gnu.org> wrote:
>   
>> On Mon, 2008-11-24 at 15:12 -0800, Luis R. Rodriguez wrote:
>>
>>     
>>> Your point about not being able to listen is a good one, and a patch to
>>> update the the US in consideration of part 15 rules would be
>>> appreciated. Keep in mind we have flags for such things:
>>>
>>>   -Passive scan
>>>   -No-IBSS
>>>
>>> We should probably rename no-ibss to no-beaconing though as that is the
>>> real meaning inention behind it.
>>>       
>> Maybe you mean no-transmit?
>>     
>
> Yeah sure, that seems to make more sense.
>
>   
I'm all for adding it to crda as no-transmit but, is that a valid flag?  
Also, how well does it work?  From a monitor mode interface you can 
inject raw packets out of the interface.  Would just adding 
"no-transmit" into the crda line work?  I certainly don't see this in 
the crda code anywhere, nor in the definition of regdb file.  I presume 
this has to be added?

Thanks,
Rick Farina




>  Luis
>
>   


  reply	other threads:[~2008-11-25  2:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 22:32 wireless-regdb: flaw in general functionality Richard Farina
2008-11-24 23:12 ` Luis R. Rodriguez
2008-11-24 23:21   ` Pavel Roskin
2008-11-24 23:26     ` Luis R. Rodriguez
2008-11-25  2:26       ` Richard Farina [this message]
2008-11-25  2:31         ` Pavel Roskin
2008-11-26  0:19           ` Luis R. Rodriguez
2008-11-26  0:35             ` Pavel Roskin
2008-11-26  1:02               ` Luis R. Rodriguez
2008-11-26  3:10                 ` Richard Farina
2008-11-26 17:05                   ` Luis R. Rodriguez
2008-11-26  5:53                 ` Michael Renzmann
2008-11-26 17:17                   ` Luis R. Rodriguez
2008-11-26 19:55                     ` Michael Renzmann
2008-11-26 20:04                       ` Johannes Berg
2008-11-27  5:26                         ` Michael Renzmann
2008-11-26 17:19                   ` 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=492B623E.5030202@gmail.com \
    --to=sidhayn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=proski@gnu.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.