Path: utzoo!attcan!uunet!convex!killer!ames!pasteur!ucbvax!CWH.CAM.NBS.GOV!craig
From: craig@CWH.CAM.NBS.GOV (Craig Hunt)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  core routing capacity exceeded?
Message-ID: <8812191426.AA00163@cwh.cam.nbs.gov>
Date: 19 Dec 88 14:26:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 21

Locally we have been having a very similar problem so I don't
think it is your ARPAnet interface.  We are on the Milnet and
SURAnet.  Since ~the beginning of December we have had difficulty
maintaining our Milnet routes.  Routes via milnet age and die
because we stop receiving updates from the core gateways.  Local
actions (restarting gated, even rebooting) have no effect.
Occasionally the routes will again start to flow.  We continue to
run because of routes through SURAnet to the remote hosts but we
notice the following symptoms.  Some routes will not be picked up
by alternate routes through SURAnet and we receive "network
unreachable" errors when attempting to connect to the remote
host.  In addition remote hosts are apparently not getting
routing information about us.  The symptom of this is to be able
to reach a remote host from our gateway system which has a 26
address, but not being able to reach the same remote system from
any system interior to our gateway.  We get "connection time out"
errors because the remote system has lost the route to 129.6.  I
have been told by the Milnet NOC that they are working on this.

If you discover anything please let me know,
---Craig Hunt