From owner-freebsd-mobile@FreeBSD.ORG Tue Jun 17 12:41:42 2003 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 A841537B401 for ; Tue, 17 Jun 2003 12:41:42 -0700 (PDT) Received: from gs166.sp.cs.cmu.edu (GS166.SP.CS.CMU.EDU [128.2.205.169]) by mx1.FreeBSD.org (Postfix) with SMTP id 27A4D43FA3 for ; Tue, 17 Jun 2003 12:41:42 -0700 (PDT) (envelope-from dpelleg@gs166.sp.cs.cmu.edu) Sender: dpelleg@gs166.sp.cs.cmu.edu To: freebsd-mobile@freebsd.org From: Dan Pelleg Date: 17 Jun 2003 15:41:18 -0400 Message-ID: Lines: 21 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: multiple DHCP interfaces 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: Tue, 17 Jun 2003 19:41:42 -0000 Dominic Mitchell wrote: > Just as a data point, this has bitten me in the past as well. The > annoying thing is that you don't even have to be using the builtin > network adaptor; just so long as it's running dhclient, you're screwed > when you put the wireless card in. You have to manually sort it all > out by running dhclient against both the old and the new interfaces... Apologies in advance for the "me too" post. While I find the net/nicmond port useful in this regard, it would be nice to have something at a higher level. In particular it should also let the user specify preferred SSIDs for association on wireless networks. I seem to remember a post here a few weeks ago announcing a project intended to unify user-level reactions to appearance and disappearance of new interfaces - unfortunately I can't find it in the archive. -- Dan Pelleg