From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 18 23:51:34 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 1B3F016A4CE for ; Sun, 18 Jan 2004 23:51:34 -0800 (PST) Received: from mailhub02.unibe.ch (mailhub02.unibe.ch [130.92.9.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACC5D43D45 for ; Sun, 18 Jan 2004 23:51:29 -0800 (PST) (envelope-from roth@lara.unibe.ch) Received: from localhost (scanhub02.unibe.ch [130.92.254.66]) by mailhub02.unibe.ch (Postfix) with ESMTP id 8B18276485; Mon, 19 Jan 2004 08:51:28 +0100 (MET) Received: from mailhub02.unibe.ch ([130.92.9.53]) by localhost (scanhub02 [130.92.254.66]) (amavisd-new, port 10024) with LMTP id 29414-01-51; Mon, 19 Jan 2004 08:51:26 +0100 (CET) Received: from asterix.unibe.ch (asterix.unibe.ch [130.92.64.4]) by mailhub02.unibe.ch (Postfix) with ESMTP id 6F32076473; Mon, 19 Jan 2004 08:51:24 +0100 (MET) Received: from lara.unibe.ch (lara [130.92.64.90]) by asterix.unibe.ch (8.11.7p1+Sun/8.11.7) with ESMTP id i0J7pO519338; Mon, 19 Jan 2004 08:51:24 +0100 (MET) Received: (from roth@localhost) by lara.unibe.ch (8.12.9+Sun/8.12.9/Submit) id i0J7pNid022218; Mon, 19 Jan 2004 08:51:23 +0100 (MET) Date: Mon, 19 Jan 2004 08:51:22 +0100 From: Tobias Roth To: Jesse Guardiani Message-ID: <20040119075122.GA22187@lara.unibe.ch> Mail-Followup-To: Jesse Guardiani , freebsd-mobile@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Operating-System: SunOS lara 5.9 Generic_112233-04 sun4u sparc SUNW,Ultra-5_10 X-Virus-checked: by University of Berne cc: freebsd-mobile@freebsd.org 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: Mon, 19 Jan 2004 07:51:34 -0000 [shortened quote] > I recently asked this list how I could automatically detect and > initialize my wireless interface based on any available SSIDs. > > I received three responses for the three different "solutions" > listed below: > > rcng patch for "autoconf at boot" > http://lists.freebsd.org/pipermail/freebsd-mobile/2003-November/002284.html just to clear things up a bit: what profile.diff does is detect the network at boot or resume, whether wireless or ethernet, and configures the whole system (not just network, everything: proxy, nfs mounts/, firewall, ...) according to where the laptop is located. it also seamlessly integrates into rcng and is easily removed as well since i did not receive much feedback back in november when i sent the patch to -current and -mobile, i will try again now that 5.2 is out and everyone has some more time. this will be in three weeks or so, i first have to make the patch acpi compliant. > "wiconf" utility > http://www.csh.rit.edu/~psionic/projects/wiconf/ > > "wlandetect" daemon > http://jelmer.vernstok.nl/oss/wlandetect/ > > What I'm particularly interested in discussing is the IDEA > behind the above three utilities: "wireless roaming" as someone else already pointed out, "wireless roaming" is not something simple. if you want real roaming as with mobile phones, you need a connection handover, so protocols with connections (tcp) do not get torn down when being handed over. thus you want "mobile ip", and that is, afaik, not yet ready for prime time. for more mobile ip infos, see here or check google: http://www.computer.org/internet/v2n1/perkins.htm > 1.) Solutions that allow "realtime" roaming > 2.) Solutions that trigger only when external events occur > > I'd like to discuss these two categories with this list and > get some feedback. Particularly, I'd like to get a feel for > what other people think is the "correct" solution and why. in short: 2) is much simpler and can be integrated into FreeBSD right now while 1) requires something like mobile ip which in turn requires infrastructure changes to the whole network environment. > Solutions that allow "realtime" roaming > --------------------------------------- > As far as I can tell, "wlandetect" is the only "solution" that > falls into this category. It runs as a daemon, actively polls > the network for available SSIDs, and reconfigures the wireless > interface on the fly. but what do you get out of that? one thing is to roam between different access points of the same wireless network, but when would you want to switch between different networks? without seamless tcp handover, this is not usable i think. cheers, t.