Problem with CMU Bootpd-DD2.4.3

Daran.Rowlands@reef.bucknell.edu Thu, 23 May 1996 11:15 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13177; 23 May 96 7:15 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13173; 23 May 96 7:15 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa05823; 23 May 96 7:15 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA13876; Thu, 23 May 1996 07:07:54 -0400
Date: Thu, 23 May 1996 07:07:54 -0400
Message-Id: <9605231056.AA2130@NYC-NTGW-N02.ny.jpmorgan.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Daran.Rowlands@reef.bucknell.edu
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Problem with CMU Bootpd-DD2.4.3
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0

All,
I'm currently testing the CMU bootpd-DD2.4.3 daemon in order to provide static 
addresses to NT clients (I have compiled the code without the DDYNAMIC flag 
since we have no intention of using dynamic addressing as we would lose 
auditing functionality.) while maintaining current BootP functionality for all 
BootP clients.

I have come across a problem with the NT 3.51 clients in that issuing a 
"ipconfig/release" command on the client sometimes causes the server daemon to 
crash with a BUS ERROR.  Putting a Sniffer on the network has revealed that the 
client sometimes releases the IP address without sending any packets out onto 
the network - occasionally however, the client sends a DHCP packet out before 
releasing the address and it is this packet that seems to cause the server 
daemon to crash.

Has anyone else experienced this problem, and if so, do you have a solution/fix?

regards,

Daran Rowlands
JP Morgan