[comp.unix.xenix.sco] why is 386 tcp limmited to one slip session?

stu@jpusa1.chi.il.us (Stu Heiss) (02/09/91)

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

jdeitch@jadpc.cts.com (Jim Deitch) (02/09/91)

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

ericd@sco.COM (Eric Davis) (02/12/91)

In article <1991Feb09.143548.11116@jadpc.cts.com> jdeitch@jadpc.cts.com (Jim Deitch) writes:
>They (altos) can support more than 1 concurrent slip.  I
>wonder if the altos tcp can be laid down into sco unix and work?

SCO TCP/IP for Unix can have more than one SLIP connection. As for
Xenix TCP/IP, not sure. I can check an post when I find out.

Ericd

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Eric Davis                      () INTERNET -=> ericd@sco.COM
Technical Support Engineer II   () UUCP     -=> {uunet|sun|att|ucsc}!sco!ericd
The Santa Cruz Operation Inc.   ()
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=