On Mon, Jan 16, 2006 at 10:16:06PM +0200, Samuel Ortiz wrote: > Well, I'd rather trust a governement regulated network than my neighbour's > AP ;-) In fact, some phones set their 802.11 regulatory domain based on > the information they received from a somehow government regulated network, > e.g. a GSM one. The asumption is that 802.11d information, like current "regdomain" settings, is fixed and not user-configurable. If the regdomain is changeable by the user, that unit would not be approved for sale in that particular locale. (Now 802.11d doesn't specify what to do when you hear two conflicting 802.11d beacons.... there go those assumptions again..) Stations respecting 802.11d rules are not allowed to transmit on any supported frequency until they hear an AP on that frequency first. This essentially means that all scans are passive until we hear an AP, and we can't transmit on any other (presumably still silent) frequencies unless we hear an 802.11d beacon that says we can. - Solomon -- Solomon Peachy ICQ: 1318344 Melbourne, FL Quidquid latine dictum sit, altum viditur.
Attachment:
pgp2jBojN79em.pgp
Description: PGP signature
- References:
- wireless: recap of current issues (configuration)
- From: "John W. Linville" <[email protected]>
- Re: wireless: recap of current issues (configuration)
- From: Johannes Berg <[email protected]>
- Re: wireless: recap of current issues (configuration)
- From: Stuffed Crust <[email protected]>
- Re: wireless: recap of current issues (configuration)
- From: Jeff Garzik <[email protected]>
- Re: wireless: recap of current issues (configuration)
- From: Stuffed Crust <[email protected]>
- Re: wireless: recap of current issues (configuration)
- From: Samuel Ortiz <[email protected]>
- Re: wireless: recap of current issues (configuration)
- From: Stuffed Crust <[email protected]>
- Re: wireless: recap of current issues (configuration)
- From: Samuel Ortiz <[email protected]>
- Re: wireless: recap of current issues (configuration)
- From: "John W. Linville" <[email protected]>
- Re: wireless: recap of current issues (configuration)
- From: Samuel Ortiz <[email protected]>
- wireless: recap of current issues (configuration)
- Prev by Date: Re: [PATCH 1/4] SATA ACPI build (applies to 2.6.16-git9)
- Next by Date: Re: [patch] networking ipv4: remove total socket usage count from /proc/net/sockstat
- Previous by thread: Re: wireless: recap of current issues (configuration)
- Next by thread: Re: wireless: recap of current issues (configuration)
- Index(es):