From owner-freebsd-questions@freebsd.org Sun Aug 30 05:37:01 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D9989C5240 for ; Sun, 30 Aug 2015 05:37:01 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC73987F for ; Sun, 30 Aug 2015 05:37:00 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id t7U5RqFK061438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 29 Aug 2015 22:27:53 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id t7U5Rp0c061437; Sat, 29 Aug 2015 22:27:51 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA02613; Sat, 29 Aug 15 22:26:51 PDT Date: Sat, 29 Aug 2015 22:27:41 -0700 From: perryh@pluto.rain.com (Perry Hutchison) To: nightrecon@hotmail.com Cc: freebsd-questions@freebsd.org Subject: Re: disabling dhclient Message-Id: <55e2944d.MRhLE3hY7fqOZUby%perryh@pluto.rain.com> References: <55e25852.0Xpg4zY1btmbpx9Z%perryh@pluto.rain.com> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2015 05:37:01 -0000 Michael Powell wrote: > Perry Hutchison wrote: > > My FreeBsd 8 system has recently developed an annoying habit of > > running dhclient during reboot. There is only one Ethernet card > > (xl0), and it is not supposed to be using DHCP -- it has a static > > IP address assigned in rc.conf. During the last couple of reboots > > dhclient has assigned a second IP address, and things have gone > > downhill from there. > ... > I don't remember for sure if these were showing up in 10.0 or if they > started after upgrading to 10.1: > > Aug 24 21:11:54 testbed devd: Executing '/etc/rc.d/dhclient quietstart em0' > Aug 26 00:33:13 testbed devd: Executing '/etc/rc.d/dhclient quietstart em0' > > Never investigated it but was wondering at the time why devd was running it, > even though I have static ifconfig(s). > > From devd.conf: > # Try to start dhclient on Ethernet-like interfaces when the link comes > # up. Only devices that are configured to support DHCP will actually > # run it. No link down rule exists because dhclient automatically exits > # when the link goes down. > > The above entries are incorrect; it runs no matter what. > ... > According to the line in devd.conf it's not supposed to start on interfaces > that are not configured for DHCP in rc.conf, and all mine are static. I think what the comment is trying to say is that, while devd will run the dhclient script on any "link up" event, the dhclient script will not actually run the dhclient daemon unless the device is configured to use DHCP. So, getting log entries from devd does not, by itself, point to a problem. However, I am getting reports like this (seen in "dmesg -a", but not in "dmesg"): add net default: gateway 192.168.0.1 Starting devd. DHCPREQUEST on xl0 to 255.255.255.255 port 67 DHCPACK from 192.168.0.1 bound to 192.168.0.3 -- renewal in 706607801 seconds. which seems to indicate that the dhclient script is running the daemon, even on this static-addressed interface.