Date: Thu, 22 Sep 2005 12:04:51 +0200 From: Erik Norgaard <norgaard@locolomo.org> To: Tilman Linneweh <arved@FreeBSD.org> Cc: freebsd-bugs@FreeBSD.org Subject: Re: bin/76305: dhclient resets configured interfaces on startup Message-ID: <433281C3.4040708@locolomo.org> In-Reply-To: <200506071801.j57I15tR032550@freefall.freebsd.org> References: <200506071801.j57I15tR032550@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Tilman Linneweh wrote:
> Synopsis: dhclient resets configured interfaces on startup
>
> State-Changed-From-To: open->feedback
> State-Changed-By: arved
> State-Changed-When: Tue Jun 7 18:00:19 GMT 2005
> State-Changed-Why:
> OpenBSD's dhclient has been imported into CURRENT.
>
> Does this solve your problems?
Sorry for not getting back on this before, it was not of ignorance but
lack of time. I mentioned two problems that I thought were related:
a) Starting dhclient for one device will reset all other devices
configured by dhclient.
This problem has been solved with the new dhclient from OpenBSD.
b) Starting dhclient will reset the device, if it was previosly
configured, before getting a lease.
This is a problem for diskless operation where the root device is nfs
mounted. In that case the diskless client looses the mount and hangs.
This has not been solved.
This may not be a bug, but rather a documentation problem.
According to the documentation of the new dhclient, the -l option allows
to specify a different location for the lease file. I have tried
specifying a memory disk device but this does not solve the problem.
The old dhclient had an option -n which should force dhclient not to
reset the interface and rather get a renewed lease. The option didn't
work as mentioned in the original pr. The new dhclient does not support
such behaviour.
On one hand, it makes sense that dhclient should not be used for
diskless clients since these will never change ip.
But on the other hand, it is well documented (including the FreeBSD
documentation) how to use dhcp to pass on client configuration
parameters with the dhcp reponse (in particular mounts for /var, /tmp
and swap, which must be client specific).
Work around:
Strictly one do not need dhclient for diskless operation, the system is
alive and kicking, so post boot configuration parameters could centrally
be mananged in some LDAP directory say, and passed by other means. I
have not gone into this yet.
If dhcp configuration of diskless clients will no longer be supported
then please pass on this note to the doc-project.
Best regards, Erik
--
Ph: +34.666334818 web: www.locolomo.org
S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt
Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72
Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?433281C3.4040708>