From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis R. Rodriguez Date: Fri, 30 Jan 2009 09:39:01 -0800 Subject: [ath9k-devel] Reg domain won't change and forced to CO (I'm in US) In-Reply-To: <13B020AB-A335-449D-8672-DFF3D71B5486@groovy.org> References: <31A1D18C-62A4-4813-B1FC-EAC860E32FCE@groovy.org> <20090128031701.GB6174@tesla> <9E657A77-CD42-4D7A-8586-A31C90CFAC55@groovy.org> <20090128061027.GD6174@tesla> <13B020AB-A335-449D-8672-DFF3D71B5486@groovy.org> Message-ID: <20090130173901.GH6534@tesla> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Wed, Jan 28, 2009 at 01:39:51AM -0800, Chris Kennedy wrote: > > On Jan 28, 2009, at 12:10 AM, Luis R. Rodriguez wrote: > > > On Tue, Jan 27, 2009 at 08:24:31PM -0800, Chris Kennedy wrote: > >> > >> On Jan 27, 2009, at 9:17 PM, Luis R. Rodriguez wrote: > >> > >>> On Tue, Jan 27, 2009 at 06:55:20PM -0800, Chris Kennedy wrote: > >>>> I have a DWA-552 and am in the US, using the newest wireless > >>>> testing > >>>> as of an hour ago. > >>>> I have things working from the Jan 20th wireless testing, but since > >>>> then these newer > >>>> ones have not let me change the reg domain (even with newest > >>>> version > >>>> containing the > >>>> fix). I have attached my boot up log and trying to change the reg > >>>> domain to US, iw --debug > >>>> output. It just won't use anything but the CO reg domain, can't > >>>> change it from that for some > >>>> odd reason. I'm trying to use AP mode, but just booting up and > >>>> trying set the reg domain > >>>> properly to US doesn't happen, and I can't use it because all > >>>> channels are invalid I try (even > >>>> when having hostapd not fail when the set reg domain call > >>>> returns an > >>>> error). Something > >>>> seems wrong, if my card has the regdomain wrong and set to CO, that > >>>> seems like it's useless > >>>> unless that value is ignored, but works great as an AP in pre > >>>> Jan 16 > >>>> versions. > >>>> > >>>> Thanks, > >>>> Chris > >>> > >>> Chris, > >>> > >>> It seems you do not have CRDA or the wireless-regdb installed, > >>> please > >>> install these as they are now required, otherwise a minimal world > >>> regulatory > >>> domain is set (what you are seeing). By shifting code to userspace > >>> we have > >>> reduced the size of ath9k, and since CRDA is no part of the > >>> regulatory support > >>> for Linux in general distributions in general will be shipping it > >>> soon. > >>> > >>> http://wireless.kernel.org/download/wireless-regdb/wireless- > >>> regdb-2009.01.15.tar.bz2 > >>> Once in the directory just do (no need to build): > >>> > >>> sudo make install > >>> > >>> http://wireless.kernel.org/download/crda/crda-1.0.1.tar.bz2 > >>> > >>> crda requires proper building: > >>> > >>> make > >>> sudo make install > >>> > >>> http://wireless.kernel.org/en/developers/Regulatory > >> > >> > >> I've actually already installed the newest git versions of both crda > >> and wireless-regdb, Although I just realized I didn't put the udev > >> file into > >> the /etc/udev/ area for this system, after putting that file into > >> place It now > >> starts up hostapd alright and allows changing the regulatory domain > >> with the newest wireless testing kernel. > > > > Great. > > > >> That seems ok, except now my wireless clients can't connect, in > >> fact the > >> hostapd log doesn't seem like they are even talking properly, > >> there's no > >> loging of them trying to associate (but can see AP and stay forever > >> trying > >> to setup the network). I tried US and CO in hostapd but either does > >> the same > >> thing, tried channels 11, 1, 3 and 7 so far. > > > > Are you using hostapd from git? What are you using for your > > clients, what > > cards, what drivers, what OS? > > > I'm using the current hostapd from git, 2 Win XP clients using > Linksys WMP300N cards (newest driver for those) > (US ones with Broadcom chips), and a Ubuntu Linux client (newest git > wpa_supplicant) > with a ipw2200 (newest wireless testing kernel) Intel 802.11g card. > I've got it setup for 802.11n, although I tried just > turning that off in hostapd.conf and still didn't work. > > > > > >> WIth that udev file setup, it works nicely now in my Jan 16 wireless > >> testing kernel, > >> uses that now instead of the default kernel built-in stuff. Is there > >> anything I'm doing > >> wrong, seems like since the card is using CO and my clients are in US > >> that maybe > >> they aren't going to talk? > > > > If your AP is up I believe you should at least see some stuff in > > the logs, > > will see if I can try to reproduce your issue in the morning, for > > now going > > to get some sleep. > > > > Just one thing -- keep in mind that when you have a country value > > on your > > ath9k card it will be respected and when a user then enters a > > country you > > are helping compliance, not overriding it. That said you are > > getting the > > intersection between CO and US when trying to apply US on your CO > > card. > > > > Please show your latest 'iw list' output, and provide your hostapd > > log. > > I've attached a tar ball of logs, the iw list output, the debugging > dmesg again, > the hostapd logs in syslog and output with -dd as command line args. > Basically > on higher debugging for hostapd, I see the stations just constantly > repeat > trying to authenticate. I'm using WPA2 (tried with 80211d=1 and =0)... > > # IEEE 802.11 related configuration > ssid=MilkyWay > country_code=US > ieee80211d=1 > hw_mode=g > channel=7 > # > bridge=ap0 > > ieee80211n=1 > ht_capab=[HT40+][SHORT-GI-40] > > wpa=3 > wpa_passphrase=XXXXXXXXX > wpa_key_mgmt=WPA-PSK > wpa_pairwise=CCMP > rsn_pairwise=CCMP Jouni found there was an issue with this patch which breaks AP mode. commit e22cab741afdd1e9857ea9fe51e28a6fe3c97b90 Author: Stephen Hemminger Date: Tue Jan 27 05:29:25 2009 +1100 mac80211: convert to net_device_ops Convert to new net_device_ops in 2.6.28 and later. Signed-off-by: Stephen Hemminger Acked-by: Johannes Berg Signed-off-by: John W. Linville