bin/76305: dhclient resets configured interfaces on startup

[Brooks Davis]

On Thu, Sep 22, 2005 at 12:04:51PM +0200, Erik Norgaard wrote:
> 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.

dhcp configuration of diskless clients has not worked for a very long
time unless said clients use an md /. This is mostly a documentation
issue.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-bugs/attachments/20050926/3f71d7b9/attachment.bin