Re: Win95 won't forget old IP address

Ted Lemon <mellon@fugue.com> Wed, 12 June 1996 01:58 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04235; 11 Jun 96 21:58 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa04231; 11 Jun 96 21:58 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa25034; 11 Jun 96 21:58 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA03377; Tue, 11 Jun 1996 21:56:14 -0400
Date: Tue, 11 Jun 1996 21:56:14 -0400
Message-Id: <199606120123.SAA02615@toccata.fugue.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: Ted Lemon <mellon@fugue.com>
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

> Therefore, apparently being on the other side of the Cisco causes some
> breakdown in the transmission, receipt, or recognition of the NAK.  Anyone
> have any thoughts on that before I break out the sniffer?

A trace of the output of DHCP would be very helpful here - it should
be telling you if the packets are coming and going through a BOOTP
gateway or not.   If the DHCPREQUEST is coming through a BOOTP
gateway, it'll be printed like this:

DHCPREQUEST for <ip-address> from <hardware-address> via <gateway-ip-address>

Otherwise, it'll be printed like this:

DHCPREQUEST for <ip-address> from <hardware-address> via <network-interface>

Likewise, the response should be printed as either

DHCPNAK on <ip-address> to <hardware-address> via <gateway-ip-address>

or

DHCPNAK on <ip-address> to <hardware-address> via <network-interface>

If the DHCPDISCOVER is reported as having come through gateway and
the DHCPNAK is not going through the same gateway, that's a bug.   If
it's reported as having come in through an interface with no gateway
and the client is on another net, you have a weird routing botch going
on.   If it says the request has come in through a gateway and the
response has been sent through a gateway, then either for some reason
the Cisco isn't getting the NAK, or it's not forwarding it correctly.
In this latter case, you will definitely need to break out a sniffer
to get to the bottom of this.

			       _MelloN_