Date: Wed, 2 Nov 2005 20:34:12 -0700 From: James Flemer <jflemer@gmail.com> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: hackers@freebsd.org Subject: Re: fix for dhclient+aliases Message-ID: <e973fdb60511021934s173d7e6aj40b8e9a6cde6af4f@mail.gmail.com> In-Reply-To: <20051103001239.GA19590@odin.ac.hmc.edu> References: <20051103001239.GA19590@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Speaking of dhclient and aliases. Has anyone sucessfully used the
alias { ... } syntax of dhclient.conf after switching dhclients? I
used to use the following in my dhclient.conf, but had to comment it
out when the OpenBSD dhclient was imported.
|alias {
| interface "sis1";
| fixed-address 192.168.100.2;
| option subnet-mask 255.255.255.0;
|}
I hope to check out this patch shortly. Thanks.
-James
On 11/2/05, Brooks Davis <brooks@one-eyed-alien.net> wrote:
> I've got a proposed fix for dhclient interactions with IPv4 aliases. It
> turns out that my speculation that it was driver issues was wrong and
> that dhclient with reacting to the aliases themselves. I suspect there
> may be issues with some drivers, but that's not the main problem.
>
> This patch adds a flag which causes dhclient to ignore address changes
> that it didn't cause. Does this seem like an acceptable solution? I'd
> probably add an rc.conf variable similar to background_dhclient.
>
> -- Brooks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e973fdb60511021934s173d7e6aj40b8e9a6cde6af4f>