From owner-freebsd-net@FreeBSD.ORG Wed Feb 1 19:34:26 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 973EF16A420 for ; Wed, 1 Feb 2006 19:34:26 +0000 (GMT) (envelope-from dswartz@druber.com) Received: from mail.druber.com (dsl-216-129-135-2.lightband.com [216.129.135.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D33C43D49 for ; Wed, 1 Feb 2006 19:34:25 +0000 (GMT) (envelope-from dswartz@druber.com) Received: from mail.druber.com (localhost.druber.com [127.0.0.1]) by mail.druber.com (Postfix) with ESMTP id AEC5E104; Wed, 1 Feb 2006 14:34:24 -0500 (EST) Received: from SWARTZEN-D3.druber.com (localhost.druber.com [127.0.0.1]) by mail.druber.com (Postfix) with ESMTP id 02E9793; Wed, 1 Feb 2006 14:34:23 -0500 (EST) Message-Id: <6.2.3.4.2.20060201143401.01cf1a90@127.0.0.1> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Wed, 01 Feb 2006 14:34:23 -0500 To: Sam Leffler From: Dan Swartzendruber In-Reply-To: <43E10844.50603@errno.com> References: <6.2.3.4.2.20060201131645.01ce5cb0@127.0.0.1> <43E10844.50603@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: ClamAV using ClamSMTP 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:34:26 -0000 At 02:13 PM 2/1/2006, Sam Leffler wrote: >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. Not complaining, mind you - I'm just relieved to know why this was happening. Thx!