IETF Logo Mail Archive

Re: Win95 won't forget old IP address

Christopher Davis <chr+@andrew.cmu.edu> Wed, 12 June 1996 22:59 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06829; 12 Jun 96 18:59 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06825; 12 Jun 96 18:59 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa18524; 12 Jun 96 18:59 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA10583; Wed, 12 Jun 1996 17:22:14 -0400
Date: Wed, 12 Jun 1996 17:22:14 -0400
Message-Id: <IljmVHC00UM9B8CSkN@andrew.cmu.edu>
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: Christopher Davis <chr+@andrew.cmu.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Win95 won't forget old IP address
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

Excerpts from netdev.dhcp-v4: 12-Jun-96 Re: Win95 won't forget old .. by
Mark Sirota@isc.upenn.ed 
> We've just moved the client to a new subnet and attempted to boot.
> The sequence of events is:
> (1) Client sends REQUEST via all-1's broadcast
> (2) Router forwards to server via unicast
> (3) Server sends NAK to router via unicast
> (4) Router forwards to client via unicast
> (5) Client drops packet because it's not an all-1's broadcast
>  
> Conclusion?  The Win95 DHCP client is broken.

Actually Win95 is working, and whatever relay-agent/dhcp server you have
is broken. The drafts for sometime has clarified that NAK's MUST always
go to 0xffffffff.



Chris Davis
Network Development
Carnegie Mellon University

v2.8.7 | Report a Bug | By Email