Search Linux Wireless

Re: [PATCH] Add new regulatory framework for Linux wireless

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jul 14, 2008 at 2:45 PM, Tomas Winkler <tomasw@xxxxxxxxx> wrote:
> On Mon, Jul 14, 2008 at 11:39 PM, Luis R. Rodriguez
> <lrodriguez@xxxxxxxxxxx> wrote:
>> On Mon, Jul 14, 2008 at 3:21 AM, Tomas Winkler <tomasw@xxxxxxxxx> wrote:
>>> I've submitted RFC patch for Country IE parsing in mac80211 as part of
>>> the work on 802.11h.  (TGh)
>>
>> I saw, I have to review it now with this in mind.
>>
>>> Q. How do you plan to merge CRDA and Country IE
>>
>> When a Country IE is received and parsed in mac80211 its up to
>> mac80211 then to decide what to do. As per the specification you
>> should use what the AP sends in the country IE but from what I am
>> seeing vendors tend to do different things with the Country IE. Some
>> considerations against parsing the Country IE and trusting it
>> completely is concerns about "rogue" APs. So as a compromise I was
>> thinking that initially we can simply call CRDA with the alpha2 passed
>> in the Country IE. Then later we can have it actually get the
>> intersection between what the AP provides and what CRDA has. The
>> driver will *always* have the ultimate say though through the callback
>> if it is registered. The callback will usually be used by vendor
>> drivers who have more stringent requirements on their regulatory
>> considerations. In the end though if trust is built around the data
>> CRDA provides it should be more than enough.
>
> If you use encryption u should probably trust the AP unless it's buggy.

I get the impression others think differently so perhaps we can leave
this as a tunable parameter, trust AP, use CRDA, or get the more
paranoid option would be to get the subset of both. What do you think?

>> Now these are just my observations so far. Please feel free to chime
>> in if there are better alternatives. We probably should take some time
>> to talk about this at OLS but for now that's what I'm aiming for.
>>
>
>>> where you will keep
>>> Country IE info cfg80211 or mac80211?
>>
>> That belongs in mac80211. You only need to tell cfg80211 the alpha2 so
>> it can query CRDA for you.
>
> I mean in case we use all the data from IE elements, should we have
> the placeholder for this in
> struct ieee80211_regdomain?

The Country IE is based on channels, the struct ieee80211_regdomain is
based on frequency ranges. We could have a regulatory rule for each
channel though so it is possible to use this structure for it. So yes,
we can use it. Once built it can be passed to cfg80211 using
set_reg(), which is what nl802111 uses.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux