Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Netwoing Problems
Message-ID: <4f3e1cec.1bc5b@pisa.ifs.umich.edu>
Date: 16 Jan 91 17:10:14 GMT
References: <1991Jan15.181655.4585@EE.Surrey.Ac.UK> <79764@unix.cis.pitt.edu>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 14

In article <79764@unix.cis.pitt.edu>, csfst1@unix.cis.pitt.edu (Charles S. Fuller) writes:

  The SR10.1 version of routed was afflicted with a form of Alzheimer's;
  it would dutifully gather information from other routed's, then forget
  what it had heard.  There is a patch available, which (I believe) is
  essentially the SR10.2 routed.  Contact the Apollo Response Center.

The sr10.2 routed has this same problem.  Either get sr10.3 or the routed
patch, number 108.  sr10.1 tcp had other problems as well, you should at
least get sr10.2.

But since he can't even ping other hosts on his subnet, this isn't just a
routing problem.  I too would be worried about the address given by netstat
-i.  The first thing I would do in this case is install sr10.2 or sr10.3.