NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/comp/os/os2/misc/29262

Text File | 1992-09-03 | 1.9 KB | 42 lines

Newsgroups: comp.os.os2.misc
Path: sparky!uunet!gatech!news.ans.net!ans.net!db3l
From: [e-mail] (David Bolen)
Subject: Re: OS2 TO SUN
Sender: [e-mail] (News Administrator)
Message-ID: <[e-mail]>
In-Reply-To: [e-mail]'s message of Thu, 3 Sep 1992 22: 03:45 GMT
Date: Thu, 3 Sep 1992 23:40:18 GMT
References: <[e-mail]>
    <[e-mail]>
Organization: Advanced Network & Services, Inc. - Elmsford, NY
Followup-To: comp.os.os2.networking
Lines: 27

In article <[e-mail]> [e-mail] (Lutz Grueneberg) writes:

>Yes, the answer is the SLIP protocol. But pay attention: not all SLIP's
>can talk which each other. I've never tested SLIP between SUN's and
>OS/2 machines.

Just for the record - anyone who implements SLIP and calls it SLIP is going
to be able to talk to anyone else who has an implementation of SLIP.  SLIP
is a framing protocol for IP packets over a serial line, and if two
implementations frame things differently, one of them isn't doing SLIP.

Now there is an issue of CSLIP (compressed slip) which is a way to compress
TCP packets going over a SLIP link.  If one implementation supports CSLIP
and another doesn't, then you can't use CSLIP on the link.  But most any
implementation will be able to disable the compressed SLIP if necessary,
since CSLIP is not a universally supported protocol.

(Followup and other questions to comp.os.os2.networking)

--
-- David
--
/-----------------------------------------------------------------------\
 \              David Bolen             \  Internet: [e-mail]      /
  |   Advanced Network & Services, Inc.   \   Phone: [phone]   |
 / 100 Clearbrook Road, Elmsford, NY 10523  \   Fax: [phone]    \
\-----------------------------------------------------------------------/