Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!bcm!dimacs.rutgers.edu!rutgers!uwm.edu!src.honeywell.com!msi.umn.edu!cs.umn.edu!uc!noc.MR.NET!news.stolaf.edu!news.stolaf.edu!swansonc From: swansonc@acc.stolaf.edu (Chris Swanson) Newsgroups: comp.protocols.tcp-ip Subject: Re: Serial line IP packages over a net Message-ID: Date: 5 Mar 91 22:19:14 GMT References: Sender: news@news.stolaf.edu Organization: St. Olaf College / N.E.T. Ambulance Lines: 32 In-Reply-To: swansonc@acc.stolaf.edu's message of 3 Mar 91 21:02:24 Well here is the followup I said I would post. It seems that, using a "plain, no frills" terminal server, you are out of luck, however there are terminal servers that do support SLIP (some even support PPP). With these servers, you connect to the server as a regular session and then do the commands to start SLIP (something like "set terminal internet slip enable") and go back and start your SLIP connection without dropping the line. With these servers (Xyplex, Cisco, and some others) you do not even need to continue your SLIP link to a "gateway" machine. The server, in fact, acts like a slow router. Once you are SLIP'd to the terminal server, that is on the desired network, you are connected and _shuldn't_ need to do anything else then set up some nameservers if needed. There has been concern expressed about running a SLIP connection with a lot of high-density trafic over a terminal server as possibly being detrimental to throughput for other users. My application will be a very low density connection, however. Any more comments or questions are wlcome. Thank's again, -Chris -- Chris Swanson, Chem/CS/Pre-med Undergrad, St. Olaf College, Northfield,MN 55057 DDN: (CDS6) INTERNET: swansonc@acc.stolaf.edu UUCP: swansonc@stolaf AT&T: Work: (507)-645-6845 Home: (507)-663-6424 I would deny this reality, but that wouldn't pay the bills...