Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!ames!sdcsvax!ucbvax!CS.UCL.AC.UK!jon
From: jon@CS.UCL.AC.UK (Jon Crowcroft)
Newsgroups: comp.protocols.tcp-ip
Subject: Invalidating ARP Caches
Message-ID: <8706011458.AA14445@ucbvax.Berkeley.EDU>
Date: Mon, 1-Jun-87 11:00:11 EDT
Article-I.D.: ucbvax.8706011458.AA14445
Posted: Mon Jun  1 11:00:11 1987
Date-Received: Wed, 3-Jun-87 00:52:02 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 30


I have only had one answer on how to invalidate arp caches in
hosts when i move my IP (proxy arp) subnet router, so here's my
thoughts...

--------------------------------------------------------------------

Could call this NARP (not arp):

I am considering writing  a service that listens for IP broadcasts
(multicasts when available) and invalidates arp caches on basis
of these. When (before/after) a router moves, it will still
forward these packets so sitting on any host I can (hopefully
only with certain privilages) say:

arpinval {ip addr}*

which will broadcast some packet like

IP header with NARP type + <IP Addr Addr etc)

(has to be IP broadcast, not lower level or the IP subnet routers wont
forward it). When routers get clever, they could send this
packet for me.

Any reason not to do this, apart from the obvious possible
misuses and broadcast traffic (though only one broadcast to fix
a lot of hosts)?

jon