Date: Thu, 10 Oct 1996 13:34:21 -0700 From: Julian Elischer <julian@whistle.com> To: michael butler <imb@scgt.oz.au> Cc: hackers@freebsd.org Subject: Re: Annoying artifact of the routing code Message-ID: <325D5DCD.167EB0E7@whistle.com> References: <199610100838.SAA19800@asstdc.scgt.oz.au>
next in thread | previous in thread | raw e-mail | index | archive | help
michael butler wrote: > > Julian Elischer writes: > > > The following bug has been annoying us here for ages > > I recently decided to track it down.. > > > set up device (ethernet) to use address A.B.C.D > > > do some work > > > change device to new address A.B.C.E > > I remember having a conversation with Ravi from Cisco in June about this > because I managed to totally confuse one of their routers (required reload) > by doing this :-) > > He seemed to think that the 'correct' thing to do was to 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 ? No that's something different.. WE (FREEBSD) are sending out packets FROM OUR OLD ADDRESS even though there is no interface with that address any more.. > > michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?325D5DCD.167EB0E7>