From owner-freebsd-net@FreeBSD.ORG Wed Feb 1 19:13:18 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBABC16A420 for ; Wed, 1 Feb 2006 19:13:18 +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 4D3A043D4C for ; Wed, 1 Feb 2006 19:13:18 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.199] ([10.0.0.199]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k11JD8o7014663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2006 11:13:08 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43E10844.50603@errno.com> Date: Wed, 01 Feb 2006 11:13:08 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Dan Swartzendruber References: <6.2.3.4.2.20060201131645.01ce5cb0@127.0.0.1> In-Reply-To: <6.2.3.4.2.20060201131645.01ce5cb0@127.0.0.1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: 'ifconfig ath0 scan' hangs under 6.0-STABLE (resolved?) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2006 19:13:18 -0000 Dan Swartzendruber wrote: > > Poking through ieee80211_ioctl.c in the kernel, I see this: > > case IEEE80211_IOC_SCAN_REQ: > if (ic->ic_opmode == IEEE80211_M_HOSTAP) /* XXX > ignore */ > break; > error = ieee80211_setupscan(ic, ic->ic_chan_avail); > if (error == 0) /* XXX background scan */ > error = ieee80211_new_state(ic, > IEEE80211_S_SCAN, -1); > break; > > So, it looks like if you're in hostap mode, it just ignores the > request? Unfortunately, the ifconfig code is looping waiting for a > response. Oh well... Yes this is a continuation of previous policy. I'll change it to return an error so ifconfig won't hang waiting for the scan complete notification. Sam