From dfr@render.com  Thu Dec 15 02:19:29 1994
Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id CAA21214 for <FreeBSD-gnats-submit@freebsd.org>; Thu, 15 Dec 1994 02:19:25 -0800
Received: (from root@localhost) by minnow.render.com (8.6.9/8.6.9) id KAA16522; Thu, 15 Dec 1994 10:22:11 GMT
Message-Id: <199412151022.KAA16522@minnow.render.com>
Date: Thu, 15 Dec 1994 10:22:11 GMT
From: Doug Rabson <dfr@render.com>
Reply-To: dfr@render.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: bootpd sometimes fails to respond to requests
X-Send-Pr-Version: 3.2

>Number:         57
>Category:       bin
>Synopsis:       bootpd sometimes fails to respond to requests
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    core (FreeBSD core team)
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Dec 15 02:20:02 1994
>Closed-Date:    Mon Jan 16 11:00:42 PST 1995
>Last-Modified:
>Originator:     
>Release:        FreeBSD 2.0-RELEASE i386
>Organization:
RenderMorphics Ltd.
>Environment:

	

>Description:

	We use bootpd locally to provide IP addresses for various PCs.  This
	worked fine under 1.1.5.  With 2.0R, sometimes the PC will not get a
	response to its request.  This appears to be due to the bootpd process
	being hung and can be remedied by killing it (inetd then starts a new
	one immediately, indicating that unread bootp packets were available).

>How-To-Repeat:

	

>Fix:
	
	

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: dfr 
State-Changed-When: Mon Jan 16 11:00:42 PST 1995 
State-Changed-Why:  
Fixed by change to rtmsg.c of bootpd.  Caused by bootpd failing to overwrite 
an incomplete arp entry for the host which was booting. 
>Unformatted:



