From pdh@minotaur.bit.net.au  Wed Aug  2 21:02:37 2000
Return-Path: <pdh@minotaur.bit.net.au>
Received: from minotaur.bit.net.au (minotaur.bit.net.au [203.18.94.87])
	by hub.freebsd.org (Postfix) with ESMTP id 1312037B5D0
	for <FreeBSD-gnats-submit@freebsd.org>; Wed,  2 Aug 2000 21:02:25 -0700 (PDT)
	(envelope-from pdh@minotaur.bit.net.au)
Received: (from pdh@localhost)
	by minotaur.bit.net.au (8.9.3/8.9.3) id OAA02189;
	Thu, 3 Aug 2000 14:02:18 +1000 (EST)
	(envelope-from pdh)
Message-Id: <200008030402.OAA02189@minotaur.bit.net.au>
Date: Thu, 3 Aug 2000 14:02:18 +1000 (EST)
From: Phil Homewood <pdh@minotaur.bit.net.au>
Reply-To: pdh@minotaur.bit.net.au
To: FreeBSD-gnats-submit@freebsd.org
Subject: dhclient inserts bogus configurations
X-Send-Pr-Version: 3.2

>Number:         20371
>Category:       bin
>Synopsis:       dhclient inserts bogus configurations
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    mbr
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Aug 02 21:10:02 PDT 2000
>Closed-Date:    Sat Jun 26 10:55:52 GMT 2004
>Last-Modified:  Sat Jun 26 10:55:52 GMT 2004
>Originator:     Phil Homewood
>Release:        FreeBSD 4.1-STABLE i386
>Organization:
>Environment:

	RELENG_4, cvsupped within the last 4 hours
	Bugs not evident as of last cvsup around mid-June.

>Description:

	dhclient seems to have two odd bugs:

	1) the broadcast address applied to the interface, if
	   not specified by the DHCP server, is wrong - on this
	   /24 it gets a.b.c.0 instead of a.b.c.255

	2) the "domain" specified by the DHCP server somehow
	   gets "\000" (four characters, NOT a literal null)
           appended to it before dhclient-script uses it to
	   build /etc/resolv.conf.


>How-To-Repeat:

	run dhclient with a DHCP server that doesn't supply
	broadcast address. (Not sure what triggers the "\000"
	feature.)

>Fix:

	Unknown.



>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->obrien 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Thu Aug 3 00:25:20 PDT 2000 
Responsible-Changed-Why:  
Over to the maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20371 
Responsible-Changed-From-To: obrien->freebsd-bugs 
Responsible-Changed-By: obrien 
Responsible-Changed-When: Sat Dec 23 11:24:31 PST 2000 
Responsible-Changed-Why:  
I am not the single dhclient maintainer now. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20371 
State-Changed-From-To: open->feedback 
State-Changed-By: murray 
State-Changed-When: Wed Mar 27 04:46:06 PST 2002 
State-Changed-Why:  
Does this problem still exist with DHCP 3.0? 

Can you try DHCP 3.0 from ports (or in the base system of -CURRENT). 



Responsible-Changed-From-To: freebsd-bugs->murray 
Responsible-Changed-By: murray 
Responsible-Changed-When: Wed Mar 27 04:46:06 PST 2002 
Responsible-Changed-Why:  
Does this problem still exist with DHCP 3.0? 

Can you try DHCP 3.0 from ports (or in the base system of -CURRENT). 


http://www.freebsd.org/cgi/query-pr.cgi?pr=20371 

From: Phil Homewood <pdh@snapgear.com>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: bin/20371: dhclient inserts bogus configurations
Date: Mon, 1 Jul 2002 12:29:59 +1000

 No can do. I left that employer over 12 months ago, and that
 particular network was dismantled not long thereafter.
Responsible-Changed-From-To: murray->mbr 
Responsible-Changed-By: mbr 
Responsible-Changed-When: Mon Feb 10 01:55:02 PST 2003 
Responsible-Changed-Why:  
Take this PR. I'll look into this. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20371 
State-Changed-From-To: feedback->closed 
State-Changed-By: mbr 
State-Changed-When: Sat Jun 26 10:54:51 GMT 2004 
State-Changed-Why:  
The submitter cannot test this anymore. As many many releases 
have passed, I think this PR can be closed. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20371 
>Unformatted:
