From owner-freebsd-mobile@FreeBSD.ORG Tue Jun 17 00:12:15 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 1494337B401 for ; Tue, 17 Jun 2003 00:12:15 -0700 (PDT) Received: from happygiraffe.net (happygiraffe.net [81.6.215.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 683E843FAF for ; Tue, 17 Jun 2003 00:12:14 -0700 (PDT) (envelope-from dom@happygiraffe.net) Received: by happygiraffe.net (Postfix, from userid 1001) id EE2945C2C; Tue, 17 Jun 2003 08:12:12 +0100 (BST) Date: Tue, 17 Jun 2003 08:12:12 +0100 To: "M. Warner Losh" Message-ID: <20030617071212.GA66426@ppe.happygiraffe.net> References: <20030613.192941.78708305.imp@bsdimp.com> <3EED1634.30404@cs.unisa.edu.au> <20030616.225708.08322880.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030616.225708.08322880.imp@bsdimp.com> User-Agent: Mutt/1.4.1i From: dom@happygiraffe.net (Dominic Mitchell) cc: freebsd-mobile@freebsd.org 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 07:12:15 -0000 On Mon, Jun 16, 2003 at 10:57:08PM -0600, M. Warner Losh wrote: > In message: <3EED1634.30404@cs.unisa.edu.au> > Benjamin Close writes: > : Is there any likely hood this will change in the future? Not beingable > : to do dhcp on more than one interface seems insane. > : For example a laptop with a hardwired ethernet card and a wireless card. > > I'd love to remove it. I don't recall the reasons it was added. It > is completely insane when you have, say, a laptop with a wired network > built in, which you want to run dhclient on, and you want to run a > dhclient on a wireless interface you plug in... 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... -Dom