conf/51394: noschg /etc/resolv.conf causes dhclient problems

Alex Trull alexander at trull.com
Thu Apr 24 14:40:07 PDT 2003


>Number:         51394
>Category:       conf
>Synopsis:       noschg /etc/resolv.conf causes dhclient problems
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Apr 24 14:40:04 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Alex Trull
>Release:        FreeBSD 4.8-STABLE i386
>Organization:
>Environment:
System: FreeBSD moonbase.turandot.home 4.8-STABLE FreeBSD 4.8-STABLE #0: Sat Apr 19 01:32:26 BST 2003 atrull at moonbase.turandot.home:/usr/obj/usr/src/sys/MOONBASE i386

My Home Firewall, Nothing Fancy. P2-450.

>Description:

Background:

Home firewall (Moonbase) runs a dns server, so I added nameserver 127.0.0.1 to /etc/resolv.conf and in an effort to stop dhclient from changing it to use isp-dhcp-assigned name servers, I chflags schg'd it.

dhclient went incontinent, refusing to write out a /var/db/dhclient.lease file for itself.

the system also went on to keep getting new (different) ips (I counted five in one six hour period). - and on restarting dhclient, it took longer than usual to get a new address.

a small cutting of all /var/log/messages spam :

Apr 24 15:31:40 moonbase dhclient: New Network Number: 80.0.199.0
Apr 24 15:31:40 moonbase dhclient: New Broadcast Address: 255.255.255.255
Apr 24 15:31:40 moonbase dhclient: New IP Address (de0): 80.0.199.68
Apr 24 15:31:40 moonbase dhclient: New Subnet Mask (de0): 255.255.255.0
Apr 24 15:31:40 moonbase dhclient: New Broadcast Address (de0): 255.255.255.255
Apr 24 15:31:40 moonbase dhclient: New Routers: 80.0.199.1
Apr 24 15:31:40 moonbase dhclient: /usr/src/sbin/dhclient/client/../../../contrib/isc-dhcp/client/dhclient.c(2024): null pointer

>How-To-Repeat:

chflags schg /etc/resolv.conf ; attempt to keep a dhcp address for more than normal.

>Fix:

Don't do what I did, or alternatively stop dhclient from having to alter /etc/resolv.conf before writing it's lease file.

I also happen to now have the following which solves the original problem :

/etc/dhclient.conf:
interface "de0" {
        send host-name "turandot.net";
        supersede domain-name "turandot.net";
        prepend domain-name-servers 127.0.0.1;
        request subnet-mask, broadcast-address, time-offset, routers,
                domain-name, domain-name-servers;
        require subnet-mask;
        media "media autoselect";
}

>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list