Xref: utzoo comp.unix.ultrix:4857 comp.sys.mips:1088
Path: utzoo!attcan!uunet!world!decwrl!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iugate!iuvax!maytag!gamiddle
From: gamiddle@maytag.waterloo.edu (Guy Middleton)
Newsgroups: comp.unix.ultrix,comp.sys.mips
Subject: Re: TCP chokes between Ultrix 4 and 3.1c systems
Message-ID: <1990Oct9.161624.6400@maytag.waterloo.edu>
Date: 9 Oct 90 16:16:24 GMT
References: <1990Oct9.031736.2569@hayes.fai.alaska.edu> <1990Oct9.040440.23066@watcgl.waterloo.edu> <41981@mips.mips.COM>
Organization: University of Waterloo Disinformation Technology Research Centre
Lines: 15

In article <41981@mips.mips.COM> len@mips.COM (Len Lattanzi) writes:
> In article <1990Oct9.040440.23066@watcgl.waterloo.edu> idallen@watcgl.waterloo.edu (Ian! D. Allen [CGL]) writes:
> :Aha!  We see this behaviour between real MIPS machines and our Ultrix
> :3.1C DECsystem 5400's.  BSD Vaxen, Suns, other machines, have no
> :problem talking to the 5400's, but connecitons from those three MIPS
> :machines hang on large packets.  And it's asymmetric -- we can rcp *out*
> :of the DS5400, but not in.
> 
> The first M/120's did not support trailers on enet packets and silently
> hung connections to other hosts that sent them. (just a guess but try
> turning off trailers on all interfaces -- I have no idea if Ultrix
> 3.1/4.0 enet hangs have similar causes) 

Aha.  That seems to fix the problem.  I'll disable trailers on all our mips
boxes; they are evil in any case.