From owner-freebsd-current@FreeBSD.ORG Tue Sep 13 07:16:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C721916A41F for ; Tue, 13 Sep 2005 07:16:49 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail1.fluidhosting.com (mail1.fluidhosting.com [204.14.90.61]) by mx1.FreeBSD.org (Postfix) with SMTP id 341AC43D5F for ; Tue, 13 Sep 2005 07:16:48 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 85540 invoked by uid 399); 13 Sep 2005 07:16:46 -0000 Received: from localhost (HELO dougb.net) (dougb@dougbarton.net@127.0.0.1) by localhost with SMTP; 13 Sep 2005 07:16:46 -0000 Date: Tue, 13 Sep 2005 00:16:45 -0700 (PDT) From: Doug Barton To: Daniel O'Connor In-Reply-To: <200509131607.12415.doconnor@gsoft.com.au> Message-ID: <20050913001126.Q52523@qbhto.arg> References: <200509131607.12415.doconnor@gsoft.com.au> Organization: http://www.FreeBSD.org/ X-OpenPGP-Key-ID: 0xD5B2F0FB X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: dhclient reusing old leases when it shouldn't X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 07:16:49 -0000 On Tue, 13 Sep 2005, Daniel O'Connor wrote: > Hi, > I have a bfe0 and an ath0 interface and I have > ifconfig_bfe0="DHCP" > ifconfig_ath0="WPA DHCP" > > in rc.conf. I use ath0 at home and bfe0 at work. > > I find that when I come to work I end up getting a lease on bfe0 but shortly > afterwards I find my resolv.conf is stomped with an old lease from ath0 and > stuff stops working. > > It would be nice if there was some higher level which decided what > information to use, but I'd settle for dhclient not touching per-machine > stuff (resolv.conf, routing etc) unless there is actually a link active on > the given interface :) I have a script that I use to prioritize which interface to start. If the wired interface is up, it starts that, and only that. If their is no link on the wired interface, it starts up the wireless. I was looking for a way to integrate that into our boot scripts when Brooks and Sam started roto-tilling them, so I've put that on hold for now. However I still think that some kind of functionality like that would be a good thing. hth, Doug -- This .signature sanitized for your protection