Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!usc!zaphod.mps.ohio-state.edu!sdd.hp.com!apollo!spear_r
From: spear_r@apollo.HP.COM (Robert Spear)
Newsgroups: comp.sys.apollo
Subject: Re: Netwoing Problems
Message-ID: <4f3e90d0.20b6d@apollo.HP.COM>
Date: 16 Jan 91 19:16:00 GMT
References: <1991Jan15.181655.4585@EE.Surrey.Ac.UK> <79764@unix.cis.pitt.edu> <4f3e1cec.1bc5b@pisa.ifs.umich.edu>
Sender: root@apollo.HP.COM
Reply-To: spear_r@apollo.COM (Robert Spear)
Organization: "The land of sun and fun"
Lines: 44

In article <4f3e1cec.1bc5b@pisa.ifs.umich.edu> rees@citi.umich.edu (Jim Rees) writes:
>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.


  Jim, the sr10.2 version of routed is not "broken" as in 10.1.  10.1 routed was
prematurely aging routes (metric 16) and therefore, you would loose the route to 
the destination.  10.2's routed would cause an access violation if invoked as
/etc/routed -t (with no filename).  It worked fine in every other way.  The 
recommended patch for 10.2 only is patch m0183 and m0139 (lib/streams) for 68k
based machines.  If you were using 10.1, we encouraged upgrading the os to 10.2.  
The primary purpose for the 10.2 patch is to fix the pty problem.
  Most problems with tcp result from misconfiguration, especially when a machine
has two network interfaces.  You must use the explicit network interface in the 
rc.local file, make sure that /etc/hostname and bldt return the same name for the
node.  Routing tables are setup for both interfaces when they are initialized 
and routed should run -f (flush route tables on initialization).  Another area
for misconfiguration involves the netmask.  Netmasks must be uniformly applied
to all hosts on the wire.  For example, if you have a class "B" address, the
first two octets are network bytes followed by host address in the last two
octets.  If you do not subnet for a class "B" address, a default mask value
of 255.255.0.0 (ffff0000) is applied.  If you subnet the third octet, you must 
specify a netmask of 255.255.255.0 (ffffff00) on the explicit interface as well 
as all hosts on that "wire".  The subnet mask "tells" tcp to consider the third 
octet as a continuation of the network address.  The gateway will route accordingly.
Hope this helps.




 Bob "The Renegade" Spear            spear_r@apollo.hp.com  
"Anything worth knowing, cannot be understood"  Woody Alan