Date: Tue, 26 Jul 2005 20:48:10 -0600 From: Scott Long <scottl@samsco.org> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: Mike Jakubik <mikej@rogers.com>, freebsd-current@freebsd.org, =?UTF-8?B?TWF0ZXVzeiBKxJlkcmFzaWs=?= <imachine@toya.net.pl>, Peter Wemm <peter@freebsd.org> Subject: Re: dhclient sucks Message-ID: <42E6F5EA.7030801@samsco.org> In-Reply-To: <200507271215.14369.doconnor@gsoft.com.au> References: <42E583F9.3070703@rogers.com> <200507261853.07513.peter@wemm.org> <1242.172.16.0.199.1122429678.squirrel@172.16.0.1> <200507271215.14369.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel O'Connor wrote:
> On Wednesday 27 July 2005 11:31, Mike Jakubik wrote:
>
>>On Tue, July 26, 2005 9:53 pm, Peter Wemm said:
>>
>>>I'd love to know which items in dhclient.conf allow you to disable the
>>>default route handling and the resolv.conf handling..
>>
>>supersede { [option declaration] [, ... option declaration] }
>>
>>Ex, I use "supersede domain-name-servers 127.0.0.1;" to set my own name
>>server.
>
>
> That just means you have to hardcode your resolver and default route into
> dhclient.conf - there is no "Don't touch this setting on my computer even if
> the DHCP server tells you to" flag in the config file I believe.
>
Part of the point of going to the new codebase was to free us from being
locked into vendor sources that we couldn't easily change. If there is
a need for a new option, please code it up and commit it!
Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42E6F5EA.7030801>