public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger•net>
To: Stefan Rompf <stefan@loplof•de>
Cc: Johannes Berg <johannes@sipsolutions•net>,
	netdev <netdev@vger•kernel.org>
Subject: Re: cfg80211 take 7
Date: Mon, 09 Oct 2006 09:16:42 -0500	[thread overview]
Message-ID: <452A59CA.7060708@lwfinger.net> (raw)
In-Reply-To: <200610091452.07098.stefan@loplof.de>

Stefan Rompf wrote:
> Am Montag, 9. Oktober 2006 13:49 schrieb Johannes Berg:
> 
>> Yeah, probably makes sense. Though, maybe not just the band but a set of
>> channels instead?
> 
> Yes, this would allow us to keep the definition of a band out of kernel. But 
> to distinguish between 802.11 b and g, we'd need a set of channels and 
> allowed modulations. I haven't looked at Larry's regulatory domain stuff yet, 
> but maybe band selection could use the same data structure. cfg80211 would 
> then just calculate the intersection of user supplied set and set permitted 
> by regulations.
> 
> Hopefully there is no country that forbids the user *NOT* to scan a specific 
> channel ;)
> 

Passive scanning is always allowed, AFAIK. Active scanning is a different matter. In the US, no one 
is allowed to active scan channels 12-14. In addition, there are a number of countries where the 
regulations prohibit active scanning in some or all of the 5 GHz bands.

Larry

  reply	other threads:[~2006-10-09 14:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 14:59 cfg80211 take 7 Johannes Berg
2006-10-06 15:07 ` Johannes Berg
2006-10-09 11:22 ` Stefan Rompf
     [not found] ` <200610091322.10495.stefan@loplof.de>
2006-10-09 11:49   ` Johannes Berg
2006-10-09 12:52     ` Stefan Rompf
2006-10-09 14:16       ` Larry Finger [this message]
2006-10-09 18:38 ` David Kimdon
2006-10-09 22:01   ` 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=452A59CA.7060708@lwfinger.net \
    --to=larry.finger@lwfinger$(echo .)net \
    --cc=johannes@sipsolutions$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=stefan@loplof$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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