Date: Thu, 14 Jul 2005 22:28:21 +0200 From: Andrea Campi <andrea+freebsd_current@webcom.it> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-current@freebsd.org, Robert Watson <rwatson@freebsd.org> Subject: Re: Problems with OpenBSD dhclient Message-ID: <20050714202820.GE1064@webcom.it> In-Reply-To: <42D6C686.4070407@centtech.com> References: <20050714182136.071B35D07@ptavv.es.net> <20050714192403.H35071@fledge.watson.org> <20050714185851.GE19351@odin.ac.hmc.edu> <1121368125.83653.12.camel@realtime.exit.com> <20050714193037.GF19351@odin.ac.hmc.edu> <42D6C686.4070407@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
picking one random message to answer to...
On Thu, Jul 14, 2005 at 03:09:42PM -0500, Eric Anderson wrote:
> Here's what I think would work well in most situations:
>
...
>
> Anything I missed?
let's not forget Zeroconf (169.254.x.x) address assignment. I have
(admittedly outdated now) patches to howl to make it work that are
waiting on someone to help me finalize them AND most integrate with
appropriate scripts so that things work as expected. This means
removing the autoconfigured address when obtaining a proper address
via DHCP, and vice versa.
A full solution should IMHO take this into account, too.
Bye,
Andrea
--
Press every key to continue.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050714202820.GE1064>