dhclient reusing old leases when it shouldn't
sam at errno.com
Tue Sep 13 09:37:43 PDT 2005
Doug Barton wrote:
> On Tue, 13 Sep 2005, Daniel O'Connor wrote:
>> I have a bfe0 and an ath0 interface and I have
>> 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
>> 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
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?
More information about the freebsd-current