From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 20 17:46:12 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8AE516A401 for ; Mon, 20 Mar 2006 17:46:12 +0000 (UTC) (envelope-from frank@pinky.sax.de) Received: from pinky.frank-behrens.de (pinky.frank-behrens.de [82.139.199.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA91043D69 for ; Mon, 20 Mar 2006 17:46:09 +0000 (GMT) (envelope-from frank@pinky.sax.de) Received: from [192.168.20.31] (pulse.behrens [192.168.20.31]) by pinky.frank-behrens.de (8.13.4/8.13.4) with ESMTP/MSA id k2KHk5Ie008808 for ; Mon, 20 Mar 2006 18:46:06 +0100 (CET) (envelope-from frank@pinky.sax.de) Message-Id: <200603201746.k2KHk5Ie008808@pinky.frank-behrens.de> From: "Frank Behrens" To: freebsd-hackers@freebsd.org Date: Mon, 20 Mar 2006 18:46:05 +0100 MIME-Version: 1.0 Priority: normal In-reply-to: <200603181026.k2IAQxJZ007181@pinky.frank-behrens.de> References: <20060317192029.GB10869@odin.ac.hmc.edu> X-mailer: Pegasus Mail for Windows (4.31, DE v4.31 R1) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: Re: [RFE] dhclient(8) should send hostname X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Mar 2006 17:46:12 -0000 Frank Behrens wrote on 18 Mar 2006 11:26: > Brooks Davis wrote on 17 Mar 2006 11:20: > > > >On Fri, Mar 17, 2006 at 04:02:17PM +0100, Frank Behrens wrote: > > > >>I propose a change, that dhclient sends always the current hostname > > > >>to the server, the value can be overwritten in dhclient.conf. I see > > > >>no negative impact, because the server has always the possibility to > > > >>reject the name and to choose another one. It would simplify the > > > >>setup and lead to the same behaviour as in other (operating) systems. > > > >>A possible (I'm sure not the best) solution I appended as attachment. > > > > > > I'm inclined to add this feature, possibly with an option to turn it > > off. It seems like a useful default and it's what other OSes do. I > > don't believe the objection above has much relevance since the actual > > update if any is only performed if the DHCP server is configured to make > > one. Incorrect DHCP packets sent by DHCP servers are my problem. Side > > effects caused by misconfiguration is not. > > Yes, this is my intention. The dhcp server gets from a client always > the MAC address and - with my proposal - the clients host name as > additional information. The decision what to make with this > information has to make the dhcp server (administrator). It can make > dynamic DNS updates or not. Meanwhile I made a short investigation about other systems and created a PR. All info can you read at http://www.freebsd.org/cgi/query-pr.cgi?pr=94743 It would give me great pleasure, if somebody could improve our dhcp client. Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available.