From owner-freebsd-current Mon Feb 8 22:37:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14511 for freebsd-current-outgoing; Mon, 8 Feb 1999 22:37:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14505 for ; Mon, 8 Feb 1999 22:37:31 -0800 (PST) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id WAA08081; Mon, 8 Feb 1999 22:37:31 -0800 (PST) (envelope-from sef) Date: Mon, 8 Feb 1999 22:37:31 -0800 (PST) From: Sean Eric Fagan Message-Id: <199902090637.WAA08081@kithrup.com> To: current@FreeBSD.ORG Reply-To: current@FreeBSD.ORG Subject: Re: adding DHCP client to src/contrib/ In-Reply-To: References: Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Hmmm.. This annoyed me actually.. >There is NO config file which means its damn annoying for you to tweak how it works.. Would you please settle on a set of misinformation and stick with it? isc-dhcp's client *does* have a very extensive configuration file. Same parser as the server. In 99.9% of cases, it needs to be a 0-length file. In some other cases, it needs to be configured. Due to a bug in the version of isc-dhcpd at work, for example, I needed to have a /etc/dhclient.conf file that looked like: send dhcp-client-identifier "sef-laptop"; There are a bunch of things I could specify. Interestingly enough, they're documented in dhclient.conf(5), which comes with the isc-dhcp package. So: not only does isc-dhcp have extensive configuration options, but, in the common case, it's not needed at all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message