From owner-freebsd-current@FreeBSD.ORG Thu Jul 4 16:43:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A569A13B for ; Thu, 4 Jul 2013 16:43:08 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 6E50C108E for ; Thu, 4 Jul 2013 16:43:08 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r64Gh4eI080302; Thu, 4 Jul 2013 09:43:04 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r64Gh4bS080301; Thu, 4 Jul 2013 09:43:04 -0700 (PDT) (envelope-from sgk) Date: Thu, 4 Jul 2013 09:43:04 -0700 From: Steve Kargl To: Mark Felder Subject: Re: devd or dhclient or ifconfig behavior seems broken Message-ID: <20130704164304.GA80279@troutmask.apl.washington.edu> References: <20130704071521.GA77965@troutmask.apl.washington.edu> <1372945821.29477.140661251893633.4436F6D3@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1372945821.29477.140661251893633.4436F6D3@webmail.messagingengine.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jul 2013 16:43:08 -0000 On Thu, Jul 04, 2013 at 08:50:21AM -0500, Mark Felder wrote: > Check the man page for dhclient.conf. You can use the supercede > functionality to always force the settings you prefer. Thanks for the suggestion. I was trying to use resolvconf.conf to put specific nameservers into resolv.conf, but dhclient (or the dhcp server I currently hooked to) is nuking resolv.conf. -- Steve