Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!cornell!batcomputer!feigin
From: feigin@batcomputer.tn.cornell.edu (Adam Feigin)
Newsgroups: comp.sys.apollo
Subject: Re: TCP3.1 Experiences?
Summary: much better, it works good, go ahead and install it
Keywords: TCP/IP 3.1, excellent
Message-ID: <5257@batcomputer.tn.cornell.edu>
Date: 22 Jun 88 12:08:52 GMT
References: <5400026@iuvax>
Reply-To: feigin@tcgould.tn.cornell.edu (Adam Feigin)
Followup-To: adam@arclight.TN.CORNELL.EDU & comp.sys.apollo
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 20

In article <5400026@iuvax> jec@iuvax.cs.indiana.edu writes:
>
>   Does anyone have any experience with the new TCP3.1 just released
>from Apollo.  I haven't installed it yet since what we have seems to
>mostly work.  I'll probably install it in a week or so unless someone
>tells me that it doesn't work.

Well, we were running TCP3.1BETA at the Language Analysis Project (my former
workplace) for several months prior to the release. IT is much better
than 3.0, and seems to work without any problems. The only problem (in the
beta stuff) was that if you were running X, and aborted out of the server,
it would sometimes take out the routing information. The tcp_server, inetd,
and routed would still be running, and you could r(sh, login etc.) to 
other nodes on the Domain ring, but you couldn't get out through the gateway.
Pinging the gateway (ethernet side) from the Ring and the outside world
would show it as dead. This is probably fixed in the release version,
although I cannot vouch for that since we had not received it at LAP by the
time I left 3 weeks ago.

						Adam