From owner-cvs-all Wed Sep 16 15:43:23 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29113 for cvs-all-outgoing; Wed, 16 Sep 1998 15:43:23 -0700 (PDT) (envelope-from owner-cvs-all) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29055 for ; Wed, 16 Sep 1998 15:42:46 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (root@woof.lan.awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id XAA25123; Wed, 16 Sep 1998 23:30:44 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id XAA01129; Wed, 16 Sep 1998 23:30:46 +0100 (BST) (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199809162230.XAA01129@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com cc: Studded , Garrett Wollman , Brian Somers , cvs-committers@FreeBSD.ORG Subject: Re: DHCP in the base In-reply-to: Your message of "Wed, 16 Sep 1998 11:51:08 PDT." <19980916115108.F24012@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Sep 1998 23:30:41 +0100 From: Brian Somers Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I use DHCP for my net connection every day for over a year, and the WIDE > client has performed very, very well for me. > > ``dhcpc fxp0'' > > Is all I do and all I need is /usr/local/sbin/dhcpc. With the ISC client > there is a VERY extensive config file needed. Mine says: interface "ep0" { send host-name "woof"; prepend domain-name-servers 127.0.0.1; } And that's only because I want it that way. AFAIK, dhcpc doesn't allow you to send anything interesting in your request... whereas the above config says that I want to be called "woof". This gives you the ability to configure a network with known machines as well as on-demand machines. Also, dhcps (the wide server) insists on each IP number in a range being specified in dhcpdb.pool - at least this is the way I've ended up using it. Dhcpd (the isc server) allows range specs, and also allows specifics based on the information sent in the initial REQUEST by the client. I'm no dhcp expert, so feel free to knock any of these points - I may be missing something in the man pages. It seems to me that the (optional) config complexity reflects the capabilities of both :-| > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) > -- Brian , , Don't _EVER_ lose your sense of humour....