From owner-freebsd-hackers  Thu Oct 10 13:11:38 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA12556
          for hackers-outgoing; Thu, 10 Oct 1996 13:11:38 -0700 (PDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA12540
          for <hackers@freebsd.org>; Thu, 10 Oct 1996 13:11:23 -0700 (PDT)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15242(9)>; Thu, 10 Oct 1996 13:10:45 PDT
Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177476>; Thu, 10 Oct 1996 13:10:26 -0700
X-Mailer: exmh version 1.6.7 5/3/96
To: michael butler <imb@scgt.oz.au>
cc: julian@whistle.com (Julian Elischer), hackers@freebsd.org
Subject: Re: Annoying artifact of the routing code 
In-reply-to: Your message of "Thu, 10 Oct 1996 01:37:58 PDT."
             <199610100838.SAA19800@asstdc.scgt.oz.au> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 10 Oct 1996 13:10:20 PDT
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <96Oct10.131026pdt.177476@crevenia.parc.xerox.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199610100838.SAA19800@asstdc.scgt.oz.au>you write:
>... invalidate any
>cached arp entries (held by others) for the old address by means of some
>broadcast on the ether concerned. Is such an arp packet defined or is it a
>'Cisco special' ?  If it is a 'standard' mechanism, why don't we use it in
>such cases ?

We do, if you "tcpdump arp" while changing your address you will notice an arp 
packet being broadcasted.  I think Julian was talking about something more 
subtle, where packets get sent with an incorrect source address.

  Bill