slevy@UC.MSC.UMN.EDU ("Stuart Levy") (12/18/88)
We're on the ARPAnet and have also been having trouble talking to the core gw's this past week. Like yours, our gated has also been crashing mysteriously (about once per day) which it rarely did before. We're running 1.3.1.73, the October 3rd beta.tar.Z. It seems the ARPAnet cores are frequently telling us to cease, so that sometimes we've been peering with no core gateway even though several are reachable. However, we've been having trouble with our ARPAnet interface over about the same period, so it may be this is all our fault and unrelated to what you're seeing. Stuart Levy
mcc@ETN-WLV.EATON.COM (Merton Campbell Crockett) (12/18/88)
Stuart: We've experienced similar problems since the upgrade to PSN 7.0 on the MILNET. We had been running EGPUP and had to change to GATED due to the increased number of routes. I believe there is a newer version of GATED dated around the end of November. Contact my colleague Steve Schultz for more details. sms@etn-wlv.EATON.COM Since Steve maintains the systems, he can give you much more accurate inform- ation. He generally logs in several times over the weekend to keep tabs on the system. Merton
craig@CWH.CAM.NBS.GOV (Craig Hunt) (12/19/88)
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