From owner-freebsd-questions@freebsd.org Sun Aug 30 02:57:53 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 698F39C5EEC for ; Sun, 30 Aug 2015 02:57:53 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2B51CCC2 for ; Sun, 30 Aug 2015 02:57:52 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZVsoV-0004qV-6A for freebsd-questions@freebsd.org; Sun, 30 Aug 2015 04:57:47 +0200 Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 30 Aug 2015 04:57:47 +0200 Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 30 Aug 2015 04:57:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Subject: Re: disabling dhclient Date: Sat, 29 Aug 2015 22:57:30 -0400 Lines: 85 Message-ID: References: <55e25852.0Xpg4zY1btmbpx9Z%perryh@pluto.rain.com> Reply-To: nightrecon@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net 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 02:57:53 -0000 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. > > Is there a configuration knob somewhere that will say "never run > dhclient" or "never run dhclient on xl0", or do I need to take > a sledgehammer approach (like hacking on /etc/rc.d/dhclient, or > replacing /sbin/dhclient with a link to /bin/true)? > 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. For me it doesn't cause any problems so I ignored it. Figured if it wasn't a problem for anyone else either that I more than likely had just screwed up somewhere in mergemaster going from 10.0 to 10.1 (I do the source upgrade and do not use the binary update). 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. -Mike > These are the settings in /etc/rc.conf: > > ifconfig_xl0="192.168.0.81 netmask 255.255.0.0" > defaultrouter="192.168.0.1" > nfs_server_enable="YES" > check_quotas="NO" > rpcbind_enable="YES" > nfs_client_enable="YES" > sshd_enable="YES" > inetd_enable="YES" > kern_securelevel_enable="NO" > linux_enable="YES" > moused_enable="NO" > moused_type="NO" > sendmail_submit_enable="NO" > sendmail_outbound_enable="NO" > sendmail_msp_queue_enable="NO" > lpd_enable="YES" > > and this is what "ifconfig -a" reports (after I've used > "ifconfig xl0 -alias 192.168.0.3" to remove the extra IP address): > > xl0: flags=8843 metric 0 mtu 1500 > options=80009 > ether 00:b0:d0:22:5a:14 > inet 192.168.0.81 netmask 0xffff0000 broadcast 192.168.255.255 > media: Ethernet autoselect (100baseTX ) > status: active > plip0: flags=8810 metric 0 mtu 1500 > lo0: flags=8049 metric 0 mtu 16384 > options=3 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=3 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org"