Date: Fri, 27 Oct 2006 15:07:48 -0700 From: Doug Barton <dougb@FreeBSD.org> To: joe@joeholden.co.uk Cc: "Andrey V. Elsukov" <bu7cher@yandex.ru>, Harti Brandt <harti@freebsd.org>, net@freebsd.org Subject: Re: Instructing dhclient to set hostname of client Message-ID: <45428334.8010909@FreeBSD.org> In-Reply-To: <453E3085.7040003@joeholden.co.uk> References: <453C0E42.4010604@joeholden.co.uk> <453C5386.5080102@FreeBSD.org> <453C5979.4050408@yandex.ru> <453D35AB.3000908@joeholden.co.uk> <20061024091523.G45134@knop-beagle.kn.op.dlr.de> <20061024143940.GA52335@lor.one-eyed-alien.net> <453E3085.7040003@joeholden.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Joe Holden wrote:
> Brooks Davis wrote:
>> On Tue, Oct 24, 2006 at 09:16:07AM +0200, Harti Brandt wrote:
>>> On Mon, 23 Oct 2006, Joe Holden wrote:
>>>
>>> JH>Andrey V. Elsukov wrote:
>>> JH>> Doug Barton wrote:
>>> JH>>> If you're talking about a laptop where you're not sure what the DHCP
>>> JH>>> server is going to send you, then I have this in /etc/rc.local:
>>> JH>>
>>> JH>> Hi, Doug.
>>> JH>>
>>> JH>> What you think about adding a new feature to dhclient - Alternate IP
>>> JH>> Configuration. This configuration can be specified in dhclient.conf
>>> JH>> and take effect when a DHCP server not respond. MS Windows have a
>>> JH>> similar feature.
>>> JH>>
>>> JH>Really I was hoping dhclient would have this sort of functionality where
>>> JH>it would resolve the ip given and set that as hostname, as as far as im
>>> JH>aware, isc-dhcpd will not send hostnames?
>>>
>>> Sure it does. On my machines I set hostname to "" in rc.conf and let
>>> dhclient set it. Works fine.
>> Once upon a time I implemented some code to add a default_hostname
>> variable to rc.conf which was then used by the startup scripts and
>> dhclient-script to allow the local network to override the name if
>> desired while insuring that the system had a name at all times (required
>> for laptop use). I'd take patches to do this.
>>
>> -- Brooks
>>
>> P.S. hacking this into rc.local won't work longterm because addresses
>> will be assigned in a totally different context.
I wasn't suggesting it as a long term fix, I was just trying to answer
the OP's question. :)
> I wrote an rc.d script called updatehost that does this, its called
> after other net scripts, and basically gets the ip from $interface (set
> by updatehost_flags="blah0" in rc.conf, and resolves that, seems to
> work, a dirty hack but it does the trick.
My only concern with that as a longer term solution would be not
interfering with a hostname set by dhclient if one exists. I'd have to
think more about the different possible combinations here ...
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45428334.8010909>