Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!SAYSHELL.UMD.EDU!louie
From: louie@SAYSHELL.UMD.EDU ("Louis A. Mamakos")
Newsgroups: comp.sys.proteon
Subject: Re: Restart/Reload connection loss
Message-ID: <9009251635.AA01664@sayshell.umd.edu>
Date: 25 Sep 90 16:35:21 GMT
References: <14032@brahms.udel.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 14

The problem is caused by traffic through the router just after restart/reload,
when the router doesn't have a route to the destination.  It sends a Destination
Unreachable ICMP advisory to the source of the traffic.  Most BSD based TCP
implementations and applications tend to give up when such an ICMP message
arrives.

You could try to configure a default route to handle this interval after you
restart/reload the router, but before it has got routing information via RIP,
EGP, OSFP, etc.  This is sort of ugly.  But I suppose, so is restarting the
router to give it a new configuration.  I once suggested to Proteon that they
inhibit generation of ICMP messages for some interval after the router starts
up to avoid this problem.

louie