Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ucbvax!HARVARD.HARVARD.EDU!walsh
From: walsh@HARVARD.HARVARD.EDU.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: how to make use of redundant routes
Message-ID: <8701282038.AA25069@ucbvax.Berkeley.EDU>
Date: Wed, 28-Jan-87 13:52:24 EST
Article-I.D.: ucbvax.8701282038.AA25069
Posted: Wed Jan 28 13:52:24 1987
Date-Received: Thu, 29-Jan-87 06:44:34 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14
Approved: tcp-ip@sri-nic.arpa


	to deliver a packet.  The one implementation that tried to ping all of
	the gateways it knew about [TOPS-20] was roundly condemned by all.

The BBN VAX networking code pinged gateways.  You don't need to ping X if
you're getting acks back for any connection actively using gateway X as a
first hop.  You also don't need to ping if you're not currently using the
gateway.

	Since none of these methods seems very attractive, I proposed the next
	best thing that I could think of: watching the routing traffic between
	the gateways.

Using an Ethernet board in snoopy mode sounds awfully inefficient.