From owner-freebsd-current@FreeBSD.ORG Mon Feb 27 18:12:55 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 875F916A420 for ; Mon, 27 Feb 2006 18:12:55 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C4FA43D45 for ; Mon, 27 Feb 2006 18:12:55 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k1RICso7092542 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Feb 2006 10:12:54 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <440341E7.6010303@errno.com> Date: Mon, 27 Feb 2006 10:16:07 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5 (X11/20060210) MIME-Version: 1.0 To: Yamamoto Shigeru References: <43F3FAF3.7010000@errno.com> <20060217.122420.38719049.shigeru@iij.ad.jp> <43F60C99.2090006@errno.com> <20060227.212918.78702145.shigeru@iij.ad.jp> In-Reply-To: <20060227.212918.78702145.shigeru@iij.ad.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: new ath+hal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 18:12:55 -0000 Yamamoto Shigeru wrote: > Hi, sam, > > I install 20060130 current to same note PC to compare 'current 20060130' and > 'current 20060222'. > After installing, I watch control message with > 'tcpdump -n -i ath0 -y IEEE802_11'. > > When using '20060130 current', I can watch "Probe request" from my note PC. > But I can't watch "Probe request" when using '20060222 current'. > > I add 'printf()' to codes and I check when 'IEEE80211_CHAN_PASSIVE' is set. > I found ath_getchannels() at @src/sys/dev/ath/if_ath.c sets > 'IEEE80211_CHAN_PASSIVE', because 'CHANNEL_PASSIVE' in channelFlags is set. FWIW if you do: ifconfig ath0 list chan you will see which channels are marked for passive scan (they have a '*' appended--though it appears this is not explained in the man page). Also doing wlandebug scan should show information like this. Otherwise adding debug; e.g. wlandebug scan+debug will show additional info including when probe request frames are sent. It should not be necessary to add printf's to the kernel to diagnose stuff like this (at least that is the intent). > > I think ath driver send "Probe request" if ignore 'CHANNEL_PASSIVE' in > channelFlags. > So I add a code to ignore 'CHANNEL_PASSIVE' and to unset > 'IEEE80211_CHAN_PASSIVE'. > I test this test code at "broadcast SSID in beacon", and my note PC can > associate an AP. > > It seems me current ath hal returns 'CHANNEL_PASSIVE' for all channels. > In @src/sys/contrib/dev/ath/ah.h, comment for 'CHANNEL_PASSIVE' is "Only > passive scan allowed in the channel". > Does it mean my note PC can't send a probe message? I answered this in previous mail but to add to it; you should be aware that regulatory agencies are very sticky about code that violates passive scan requirements. What I want to do is make sure the new hal is doing the right thing for the regdomain you are using (hence my request for the info). The rules in Japan have changed significantly since the 0.9.14.9 hal was released so it is not surprising you are seeing different behaviour with the new code. Sam