Xref: utzoo comp.protocols.tcp-ip:14835 comp.unix.xenix.sco:1652
Path: utzoo!utgpu!watserv1!watmath!att!linac!uwm.edu!spool.mu.edu!sdd.hp.com!ucsd!nosc!crash!jadpc!jdeitch
From: jdeitch@jadpc.cts.com (Jim Deitch)
Newsgroups: comp.protocols.tcp-ip,comp.unix.xenix.sco
Subject: Re: why is 386 tcp limmited to one slip session?
Keywords: 386,slip
Message-ID: <1991Feb09.143548.11116@jadpc.cts.com>
Date: 9 Feb 91 14:35:48 GMT
References: <1991Feb8.162556.6584@jpusa1.chi.il.us>
Organization: Network Engineering Technologies, San Diego, CA.
Lines: 17

In article <1991Feb8.162556.6584@jpusa1.chi.il.us> stu@jpusa1.UUCP (Stu Heiss,925,6326,none) writes:
>Someone posted that most 386 tcp implementations are limmited to
>one slip.  This is true for the Lachman port on Xenix that we use.
>Why is this and is there any way to support more than one slip?
>-- 
>Stu Heiss - stu@jpusa1.chi.il.us

You know what is really interesting, I just got done doing some work
on a Altos 1000, it is a 386 box that is using a modified SCO Unix,
running Lachman tcp.  They can support more than 1 concurrent slip.  I
wonder if the altos tcp can be laid down into sco unix and work?

Jim
-- 
ARPANET:    jadpc!jdeitch@nosc.mil
INTERNET:   jdeitch@jadpc.cts.com
UUCP:	    nosc!jadpc!jdeitch