Subject: bin/33565: dhcpd.conf.5 incorrectly claims next-server is optional
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org>
From: None <chap@NetBSD.org>
List: netbsd-bugs
Date: 05/26/2006 19:15:00
>Number:         33565
>Category:       bin
>Synopsis:       dhcpd.conf.5 incorrectly claims next-server is optional
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 26 19:15:00 +0000 2006
>Originator:     Chapman Flack
>Release:        NetBSD 3.99 after 11 August 2005
>Organization:
	
>Environment:
	
	
any
>Description:
	ISC changed the behavior of the DHCP server between 3.0.2 and
	3.0.3 (imported by drochner@ on 11 August 2005). Previously,
	the behavior was as described in dhcpd.conf.5:

	If no next-server parameter applies to a given client, the DHCP
	server's IP address is used.

	Since the change, from src/dist/dhcp/RELNOTES:

	The siaddr field is now left zeroed unless next-server is
	configured.

	However, ISC left the now-incorrect sentence in dhcpd.conf.5.
	(It has been removed in their 3.0.4 release.)

	Reported by Wojciech Puchar and Patrick Welche on current-users,
	20 and 22 September 2005.

>How-To-Repeat:
	Clear by observation.
>Fix:
	Remove the incorrect sentence (longer term, import 3.0.4).

>Unformatted: