dhclient does not recognize config file
 

dhclient in Squeeze pays no attention to the config file at /etc/dhcp/dhclient.conf

All I need it to do is prepend the local host to resolv.conf so dns caching will work.

How do you get dhclient to do anything other than the default behavior?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1337870001.52679.YahooMailNeo@web162602.mail.bf1.y ahoo.com">http://lists.debian.org/1337870001.52679.YahooMailNeo@web162602.mail.bf1.y ahoo.com

dhclient does not recognize config file
 

Hi

On Thu, May 24, 2012 at 03:33:21PM +0100, Paul Zimmerman wrote:
> dhclient in Squeeze pays no attention to the config file at /etc/dhcp/dhclient.conf

How about /etc/dhcp3/dhclient.conf ?


--
Karl E. Jorgensen
IT Operations


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120524154453.GV17862@hawking">http://lists.debian.org/20120524154453.GV17862@hawking

dhclient does not recognize config file
 

On Thu, 24 May 2012 07:33:21 -0700, Paul Zimmerman wrote:

> dhclient in Squeeze pays no attention to the config file at
> /etc/dhcp/dhclient.conf

How does the file look like? Also, did you restart dhclient after editing
the file?

> All I need it to do is prepend the local host to resolv.conf so dns
> caching will work.

You mean the "prepend domain-name-servers 127.0.0.1" stanza?

> How do you get dhclient to do anything other than the default behavior?

Are you using N-M?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: jplntu$a15$20@dough.gmane.org">http://lists.debian.org/jplntu$a15$20@dough.gmane.org

dhclient does not recognize config file
 

References: <1337870001.52679.YahooMailNeo@web162602.mail.bf1. yahoo.com>, <jplntu$a15$20@dough.gmane.org>

Camaleón <noelamac@gmail.com> wrote:

>On Thu, 24 May 2012 07:33:21 -0700, Paul Zimmerman wrote:

>> dhclient in Squeeze pays no attention to the config file at/etc/dhcp/dhclient.conf

>How does the file look like? Also, did you restart dhclient after editing the file?*

Rebooting does a pretty good job of restarting all programs, including daemons. :)
This is an ongoing problem through days or use, so yes, it gets restarted often.


>> All I need it to do is prepend the local host to resolv.conf so dnscaching will work.

>You mean the "prepend domain-name-servers 127.0.0.1" stanza?


Yes, that's what I tried first. It has absolutely no effect. Then I created some specific
"interface" entries. Since it left error messages in the log when I made mistakes, it
is clearly reading the config file.


>> How do you get dhclient to do anything other than the default behavior?

>Are you using N-M?


No, but I do use wicd. Does that write resolv.conf too? Avahi was running on the system,

but I removed it. Also checked for resolvconf and it doesn't show as installed even though

there is a resolvconf directory. Is there anything else that might be over-writing the file?



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1337897593.21629.YahooMailNeo@web162604.mail.bf1.y ahoo.com">http://lists.debian.org/1337897593.21629.YahooMailNeo@web162604.mail.bf1.y ahoo.com

dhclient does not recognize config file
 

On Thu, May 24, 2012 at 03:13:13PM -0700, Paul Zimmerman wrote:
> References: <1337870001.52679.YahooMailNeo@web162602.mail.bf1. yahoo.com>, <jplntu$a15$20@dough.gmane.org>
>
> Camaleón <noelamac@gmail.com> wrote:
>
> >On Thu, 24 May 2012 07:33:21 -0700, Paul Zimmerman wrote:
>
> >> All I need it to do is prepend the local host to resolv.conf so dnscaching will work.
>
> >You mean the "prepend domain-name-servers 127.0.0.1" stanza?
>
> Yes, that's what I tried first. It has absolutely no effect.

I'm listening, too, as was frustrated trying to use
this option the last time I sought to set up DNS caching.

--
Joel Roth


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120525092847.GA30176@sprite">http://lists.debian.org/20120525092847.GA30176@sprite

dhclient does not recognize config file
 

On Thu, 24 May 2012 15:13:13 -0700, Paul Zimmerman wrote:

> Camaleón <noelamac@gmail.com> wrote:
>
>>On Thu, 24 May 2012 07:33:21 -0700, Paul Zimmerman wrote:
>
>>> dhclient in Squeeze pays no attention to the config file
>>> at/etc/dhcp/dhclient.conf
>
>>How does the file look like? Also, did you restart dhclient after
>>editing the file?
>
> Rebooting does a pretty good job of restarting all programs, including
> daemons. :) This is an ongoing problem through days or use, so yes, it
> gets restarted often.

Oh, okay. I just wanted to be sure the "dhclient" process was aware of
the changes done in the file :-)

>>> All I need it to do is prepend the local host to resolv.conf so
>>> dnscaching will work.
>
>>You mean the "prepend domain-name-servers 127.0.0.1" stanza?
>
>
> Yes, that's what I tried first. It has absolutely no effect. Then I
> created some specific "interface" entries. Since it left error messages
> in the log when I made mistakes, it is clearly reading the config file.

That was going to be my next question: if the file is being read at all.
As so it seems, then is just that specific line that fails or that has no
visible effect, meaning your "/etc/resolv.conf" file remains the same,
right?

Let me try it in wheezy. Mmm, here it works :-?

I use N-M with a wireless card and I have edited "/etc/dhcp/
dhclient.conf" and set:

prepend domain-name-servers 127.0.0.1;

Then restarted the NM service ("service network-manager restart") and
checked for the content of "/etc/resolv.conf". The first line now is:

nameserver 127.0.0.1

>>> How do you get dhclient to do anything other than the default
>>> behavior?
>
>>Are you using N-M?
>
>
> No, but I do use wicd. Does that write resolv.conf too? Avahi was
> running on the system,
>
> but I removed it. Also checked for resolvconf and it doesn't show as
> installed even though
>
> there is a resolvconf directory. Is there anything else that might be
> over-writing the file?

Then wicd will be in charge of editing/configuring "/etc/resolv.conf"
like N-M does but I'm not sure what could be the difference here, I mean,
between using N-M or Wicd ... or wait, the difference can also be in the
package version, as I'm on wheezy mine is "4.2.2.dfsg.1-5" while squeeze
has "4.1.1-P1-15+squeeze3"... maybe is that you're hitting a bug? :-?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: jpo9ii$4v3$12@dough.gmane.org">http://lists.debian.org/jpo9ii$4v3$12@dough.gmane.org

dhclient does not recognize config file
 

On Fri, May 25, 2012 at 11:47 AM, Camaleón <noelamac@gmail.com> wrote:
> On Thu, 24 May 2012 15:13:13 -0700, Paul Zimmerman wrote:
>> Camaleón <noelamac@gmail.com> wrote:
>>>On Thu, 24 May 2012 07:33:21 -0700, Paul Zimmerman wrote:
>>>>
>>>> dhclient in Squeeze pays no attention to the config file
>>>> at/etc/dhcp/dhclient.conf
>>>>
>>>> All I need it to do is prepend the local host to resolv.conf so
>>>> dnscaching will work.
>>>
>>> You mean the "prepend domain-name-servers 127.0.0.1" stanza?
>>
>> Yes, that's what I tried first. It has absolutely no effect. Then I
>> created some specific "interface" entries. Since it left error messages
>> in the log when I made mistakes, it is clearly reading the config file.
>
> That was going to be my next question: if the file is being read at all.
> As so it seems, then is just that specific line that fails or that has no
> visible effect, meaning your "/etc/resolv.conf" file remains the same,
> right?
>
> I use N-M with a wireless card and I have edited "/etc/dhcp/
> dhclient.conf" and set:
>
> prepend domain-name-servers 127.0.0.1;
>
> Then restarted the NM service ("service network-manager restart") and
> checked for the content of "/etc/resolv.conf". The first line now is:
>
> nameserver 127.0.0.1

For the record, this works for squeeze without NM or WICD - for me.

Check how well or badly dhclient's behaving by changing "RUN=no" to
"RUN=yes" in "/etc/dhcp/dhclient-enter-hooks.d/debug", restarting your
network (in your case, I assume that "service wicd restart" will do it
but I've never used WICD), and checking
"/var/lib/dhcp/dhclient.eth0.leases" and /tmp/dhclient-script.debug".


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAOdo=SybC3=yr=8rCpWZqCLWQtN4uvrYAmT_pC23V8Y22RzzB A@mail.gmail.com">http://lists.debian.org/CAOdo=SybC3=yr=8rCpWZqCLWQtN4uvrYAmT_pC23V8Y22RzzB A@mail.gmail.com