Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Dec 2005 19:29:18 +0200
From:      Giorgos Keramidas <keramida@ceid.upatras.gr>
To:        Doug Poland <doug@polands.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: dhclient.conf is being ignored
Message-ID:  <20051201172918.GA63343@flame.pc>
In-Reply-To: <65091.209.103.215.99.1133457841.squirrel@email.polands.org>
References:  <59724.209.103.215.99.1133455725.squirrel@email.polands.org> <20051201170039.GA63056@flame.pc> <65091.209.103.215.99.1133457841.squirrel@email.polands.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-12-01 11:24, Doug Poland <doug@polands.org> wrote:
>On Thu, December 1, 2005 11:00, Giorgos Keramidas wrote:
>> On 2005-12-01 10:48, Doug Poland <doug@polands.org> wrote:
>>> Hello,
>>>
>>> I'm running 6.0-STABLE and having an issue with dhclient "ignoring"
>>> dhclient.conf(5).
>>>
>>> On this dual-homed host, I've created dhclient.conf in it's proper
>>> location with the option modifiers I want.  However, everytime
>>> dhclient negotiates a new lease, I get my ISP's values in
>>> resolv.conf(5) and not my over-rides.
>>>
>>> and my dhclient.conf file:
>>>
>>> # cat /etc/dhclient.conf
>>> interface "fxp0" {
>>>         supersede domain mydomain.com
>>>         supersede domain-name-servers 172.16.1.17, 172.16.1.32;
>>> }
>>
>> You're missing a semicolon after the first supersede line:
>>
>>     interface "fxp0" {
>>             supersede domain mydomain.com;
>>             supersede domain-name-servers 172.16.1.17, 172.16.1.32;
>>     }
> 
> Duh.  Thanks for pointing that out Giorgos.  It would be nice if
> dhclient informed me of the error of my ways.

That's what I'd expect too.  If it doesn't, it's probably a usability
bug and you should file a problem report, IMHO.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051201172918.GA63343>