Date: Tue, 13 Sep 2005 09:44:44 -0700 From: Sam Leffler <sam@errno.com> To: Doug Barton <dougb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: dhclient reusing old leases when it shouldn't Message-ID: <432701FC.7080909@errno.com> In-Reply-To: <20050913001126.Q52523@qbhto.arg> References: <200509131607.12415.doconnor@gsoft.com.au> <20050913001126.Q52523@qbhto.arg>
index | next in thread | previous in thread | raw e-mail
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? Samhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?432701FC.7080909>