From owner-freebsd-mobile@FreeBSD.ORG Mon Jun 16 09:32:23 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 C943237B401 for ; Mon, 16 Jun 2003 09:32:23 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id B949343FDF for ; Mon, 16 Jun 2003 09:32:22 -0700 (PDT) (envelope-from freebsd-mobile@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19Rwpk-0007wW-00 for ; Mon, 16 Jun 2003 18:27:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-mobile@freebsd.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19RwnG-0007dW-00 for ; Mon, 16 Jun 2003 18:25:18 +0200 From: Jesse Guardiani Date: Mon, 16 Jun 2003 12:28:11 -0400 Organization: WingNET Lines: 45 Message-ID: References: <3EEDAF4A.6902.DC2283@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@main.gmane.org User-Agent: KNode/0.7.2 X-Mail-Copies-To: never Sender: news Subject: Re: multiple DHCP interfaces X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2003 16:32:24 -0000 nadas@torrentnet.com wrote: > i understood this to be a dhclient issue, not a dhcpd issue. my 4.8 > stable > certainly runs dhcpd on multiple i/f's. Yes. On my box it is a dhclient issue. I'm not trying to run a dhcpd server. I suppose the speedstream was a bad example since it runs a dhcp client on one interface and a server on the other... > the original qn seemed to be from > a client that sometimes connects wired and sometimes wirelessly and did > not want to wait for dhcp timeouts. Yes, but I would also like to be able to run dhclient on both interfaces if they are both up. Alternatively, I could write a cron script to shut down the wireless interface when the wired interface detects a signal. This script would poll the wired interface for line presence every few seconds, and bring the wireless interface offline if a wired signal is detected. It would then kill the wireless dhclient session, and instantiate a dhclient session for the wired interface. The same script would then do the opposite when the wired signal is lost. I think I could write such a cron script to do all of that rather easily, but it sounds like a cludge that could be handled more efficiently by changes to the C networking libraries and the dhclient program. This all seems to be stemming from the fact that FreeBSD generally expects network connections to be always on. Is there any current effort to make the base FreeBSD networking code more "pluggable"? -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net