From owner-freebsd-hackers  Tue Apr 29 05:34:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id FAA14075
          for hackers-outgoing; Tue, 29 Apr 1997 05:34:55 -0700 (PDT)
Received: from darling.cs.umd.edu (darling.cs.umd.edu [128.8.128.115])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14070
          for <hackers@freebsd.org>; Tue, 29 Apr 1997 05:34:53 -0700 (PDT)
Received: by darling.cs.umd.edu (8.8.5/UMIACS-0.9/04-05-88)
	id IAA28439; Tue, 29 Apr 1997 08:34:51 -0400 (EDT)
Message-Id: <199704291234.IAA28439@darling.cs.umd.edu>
To: hackers@freebsd.org
To: Archie Cobbs <archie@whistle.com>, rohit@cs.umd.edu
Subject: Re: Bizzare Ping (and other) bugs. 
In-reply-to: Your message of "Mon, 28 Apr 1997 21:57:07 EDT."
             <199704290157.VAA27764@darling.cs.umd.edu> 
Date: Tue, 29 Apr 1997 08:34:51 -0400
From: Rohit Dube <rohit@cs.umd.edu>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 28 Apr 1997 21:57:07 -0400 rohit@cs.umd.edu writes:
=>The problem is that some PCBs cache routes. I haven't checked this out
=>but, these cached routes should still cause a problem as they would
=>point to the old in_ifaddr. These would have to be caught separately,
=>unless one wants to sweep thru all the PCBs and fix them when the interface
=>address changes. (I would go for the second option as address change is a
=>rare event).

I must have been stoned when I sent this (well it was rather late in the
evening) - current connections _are_ supposed to break. Therefore the above
is not a bug. Only new connections (or end points) should source packets with 
the new address.

Sorry!

--rohit.