From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 18 15:19:40 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E10C16A4CE for ; Sun, 18 Jan 2004 15:19:40 -0800 (PST) Received: from nebula.sm.sony.co.jp (widefw.sm.sony.co.jp [133.138.0.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58AA043D53 for ; Sun, 18 Jan 2004 15:19:38 -0800 (PST) (envelope-from onoe@sm.sony.co.jp) Received: from nest.sm.sony.co.jp (onoe@localhost)i0INJaCn007297 for ; Mon, 19 Jan 2004 08:19:36 +0900 (JST) Received: (from onoe@localhost) by nest.sm.sony.co.jp (8.12.9p1/8.12.8) id i0INKWXt016722; Mon, 19 Jan 2004 08:20:32 +0900 (JST) Date: Mon, 19 Jan 2004 08:20:32 +0900 (JST) From: Atsushi Onoe Message-Id: <200401182320.i0INKWXt016722@nest.sm.sony.co.jp> To: freebsd-mobile@freebsd.org In-Reply-To: Your message of "Fri, 16 Jan 2004 11:24:52 -0500" References: X-Mailer: Cue version 0.6 (040109-1550/onoe) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Subject: Re: managing multiple wireless SSIDs (summary discussion) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2004 23:19:40 -0000 > The questions I'd like to discuss > --------------------------------- > So here are the questions that come to mind after digesting the > above information: > > 1.) Which category is preferable? > > Currently, I think the event based solutions are the most > _practical_ on FreeBSD, but are they the "correct" long term > solution? It is pretty difficult to have a generic solution for all users. Windows do background scan periodically, and sometimes switch to another SSID. It is OK for WWW and Mail client, but it is difficult to use ssh login. For long time connection, sticking only single SSID even without radio for a while, should be preferable feature unless Mobile IP is much more popular. But I know there are many users who only want to use www and e-mail. > 2.) What is the future of the `wicontrol` command? I've noticed > that `wicontrol -L` only works if the wi interface is > configured with an empty SSID: > > ifconfig wi0 ssid '' wepmode off I guess wicontrol just scans configured SSID. To scan the APs of 'hidden' SSID, wicontrol -L requires SSID configured. > Are there plans to make a more general interface for things > like SSID enumeration? > > Does wicontrol -L work for the ath driver? Or just wi? Obviously, wicontrol is designed for wi, and it uses wi specific interface. But since there are no other utilities, net80211 wlan framework provides a compatible interface for wicontrol. So wicontrol -L should work for ath (and awi). The same condition applies for wiconfig -D on NetBSD, JFYI. Regards, Atsushi Onoe