On Mon, May 23, 2011 at 9:48 PM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > On 05/23/2011 03:15 PM, Luis R. Rodriguez wrote: >> >> On Mon, May 23, 2011 at 2:59 PM, Ben Greear<greearb@xxxxxxxxxxxxxxx> >> Âwrote: >>> >>> On 05/23/2011 02:46 PM, Luis R. Rodriguez wrote: >>>> >>>> On Mon, May 23, 2011 at 2:42 PM, Luis R. Rodriguez<mcgrof@xxxxxxxxx> >>>> Âwrote: >>>> >>>>> No. You can only do this by trying to take the card out of compliance >>>>> purposely or unknowingly in software. >>>> >>>> Oh and my point was that "regulatory hacks" fit this description. >>> >>> Ok. ÂI believe you are right in general, but I can't see how enabling >>> a device to work on a non-scanned channel can break something, >> >> If a card is world roaming, how else on earth without seeing a beacon >> will you know if you can initiate radiation on that channel? > > I have a strong personal sense of location, and I'm 100% sure that > I'm in the US. ÂSo, the the computer could listen to it's human > and just trust that I know WTF I am asking for! > > It may currently be impossible for vendors to explicitly support > this due to regulatory domains that assume users are evil and/or > stupid and not to be trusted to know their current location, > but please don't pretend that receiving a beacon is rock solid > evidence of a channel's availability: ÂIt only means that someone > else that set up the AP thinks it's available for use. I agree completely but as you noted the issues are not with us, its with regulatory agencies who have explicitly mentioned user's intervention in location information and wanting the user out of the equation [1]. The more tangible solution then is to work on automatic locationing mechanisms which we can rely on and prove to regulatory agencies are solid. Slowly that's the path I believe we should take. One step at a time. [1] http://wireless.kernel.org/en/developers/Regulatory/CRDA#Helping_compliance_by_allowing_to_change_regulatory_domains >>> if it is perfectly legal and appropriate for there to be an AP on that >>> scanned channel. >> >> Agreed! In fact I'd go so far as to say that if you have multiple >> 802.11 cards they should be able to share the same beacon hints, and >> in fact -- this is what cfg80211 does ;) >> >>> In other words, if I change my Netgear to be on channel >>> 48, scanned it, and then created a VAP on that channel, that is OK with >>> un-hacked regdomain stuff, but if instead I change regdomain to 0x0 >>> and use channel 48 without re-configuring my Netgear, somehow that >>> suddenly causes issues? >> >> For Atheros EEPROM 0x0 is designed for usage for the US: > > Good..that's all I really wanted: ÂMy NIC to support my > location w/out undue complaint or limitations. Enjoy :) 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
