Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!rutgers!aramis.rutgers.edu!geneva.rutgers.edu!hedrick From: hedrick@geneva.rutgers.edu (Charles Hedrick) Newsgroups: comp.protocols.tcp-ip Subject: Re: 48 Kbps SLIP? Message-ID: Date: 12 Jun 89 02:16:25 GMT References: <396@levels.sait.edu.au> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 14 To: cccar@levels.sait.edu.au I don't know of anything that makes 48Kbps SLIP unworkable, assuming that the equipment on both ends can support it. However in general I'd only use SLIP if the cost of real routers is too high. There are advantages to the more conventional synchronous protocols. One is that typically the synchronous controller cards will deal with a whole HDLC packet at once, so that the load on the processor is less. Another is that SLIP is a minimal protocol. Most vendors' synchronous support has provisions for detecting when the line has hung and doing things to reset it, and also for passing multiple protocols (e.g. IP and DECnet) on the same line. You mention needing Sunlink/IR in order to do this on a Sun. We have a SLIP connection between a terminal server and a Sun acting as a gateway, and are not using Sunlink/IR. There's a P.D. SLIP implementation for the Sun. However we're using 9600. It may be that you need something more exotic at 48Kbps.