Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751206AbWAPVGx (ORCPT ); Mon, 16 Jan 2006 16:06:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751203AbWAPVGw (ORCPT ); Mon, 16 Jan 2006 16:06:52 -0500 Received: from rrcs-24-73-230-86.se.biz.rr.com ([24.73.230.86]:20894 "EHLO shaft.shaftnet.org") by vger.kernel.org with ESMTP id S1751201AbWAPVGv (ORCPT ); Mon, 16 Jan 2006 16:06:51 -0500 Date: Mon, 16 Jan 2006 16:06:26 -0500 From: Stuffed Crust To: Samuel Ortiz Cc: "ext John W. Linville" , Jeff Garzik , Johannes Berg , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: wireless: recap of current issues (configuration) Message-ID: <20060116210626.GA15495@shaftnet.org> Mail-Followup-To: Samuel Ortiz , "ext John W. Linville" , Jeff Garzik , Johannes Berg , netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20060113221935.GJ16166@tuxdriver.com> <1137191522.2520.63.camel@localhost> <20060114011726.GA19950@shaftnet.org> <43C97605.9030907@pobox.com> <20060115152034.GA1722@shaftnet.org> <20060116170951.GA8596@shaftnet.org> <20060116190629.GB5529@tuxdriver.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Greylist: Sender is SPF-compliant, not delayed by milter-greylist-2.0.2 (shaft.shaftnet.org [127.0.0.1]); Mon, 16 Jan 2006 16:06:27 -0500 (EST) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1808 Lines: 51 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=20 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. =20 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 --=20 Solomon Peachy ICQ: 1318344 Melbourne, FL =20 Quidquid latine dictum sit, altum viditur. --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFDzArSPuLgii2759ARAqx7AKCeOtC9h+zdwU5L9KozsoT4ZUgAcgCeIkT2 APaXfKBDnDXQ32wi7IeS4/s= =/Oyl -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/