Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!pacbell.com!ucsd!celit!dave
From: dave@fps.com (Dave Smith)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: SLIP problems under SunOS 4.1.1
Message-ID: <16878@celit.fps.com>
Date: 16 Apr 91 05:19:28 GMT
References: <1991Apr12.060432.1266@solar.card.inpu.oz.au> <1991Apr12.140605.29819@oar.net>
Sender: daemon@fps.com
Reply-To: dave@fps.com (Dave Smith)
Organization: FPS Computing Inc., San Diego CA
Lines: 21

In article <1991Apr12.140605.29819@oar.net> karl.kleinpaste@osc.edu writes:
>brett@solar.card.inpu.oz.au writes:
>I've written a note about the problem to sunbugs@sun.com, but since it
>involves use of a non-standard driver, I doubt it'll get much
>attention.  Before installing 100149-02, I consistently got "panic:
>mclput" whenever substantial amounts of data would begin to transfer.

I have been using SLIP 4.0 on SLC's under 4.1.1 for about three weeks now
and have run a goodly number of megabytes through them.  I saw this mclput
panic fairly frequently for a while and then saw a real high correlation
with the answering side of the connection (I'm using dialup over T2500's)
panicing when the connection was dropped.  When I switched to V.42 mode
the panic's went away.  My feeling is that the utter garbage you get
when the other side hangs up is confusing the TCP routines incredibly
since they aren't used to being fed complete crap.

--
David L. Smith
FPS Computing, San Diego        ucsd!celit!dave or dave@fps.com
"It was time to stop playing games.  It was time to put on funny hats and
eat ice cream.  Froggie played his oboe" - Richard Scarry