From owner-freebsd-current@FreeBSD.ORG Tue Sep 13 16:37:43 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 0259616A41F; Tue, 13 Sep 2005 16:37:43 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9C2543D45; Tue, 13 Sep 2005 16:37:42 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.200] ([10.0.0.200]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j8DGbd6j039438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Sep 2005 09:37:39 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <432701FC.7080909@errno.com> Date: Tue, 13 Sep 2005 09:44:44 -0700 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050327) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Barton References: <200509131607.12415.doconnor@gsoft.com.au> <20050913001126.Q52523@qbhto.arg> In-Reply-To: <20050913001126.Q52523@qbhto.arg> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 16:37:43 -0000 Doug Barton wrote: > 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. It's been suggested multiple times that it would be good to add some sort of prioritization mechanism to the dhclient-script so you could control which network is used for the default route et. al. It sounds like you've got something started so perhaps you could expand on it? Sam