Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!ucsd!ucbvax!WUBIOS.WUSTL.EDU!david From: david@WUBIOS.WUSTL.EDU ("David J. Camp") Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: telnet over 9600 baud SLIP impressions (fwd) Message-ID: <9012061404.AA05017@wubios.wustl.edu> Date: 6 Dec 90 14:04:15 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 33 >How effective is it to run NCSA telnet over a 9600 baud slip link >for interactive use (ie editting)? Is it somewhat like running >over a 2400 baud modem...better...worse? I'm more concerned >about the "feel" of the connection (character echo-back time) than >burst transfer speed (displaying a whole page). > >Thanks, >-Henry Bland > I have done this. I must say I had a lot of problems, but I think they can be blamed on the hardware. I had a simply 3-wire RS232 connection, and SLIP expects to be able to use the flow control lines. The SLIP server on the Unix system kept exiting. I was able to continue the session by restarting the SLIP server, and it continued where it left off! I finally put the sliplogin call in a script with a loop. Then, when it exits, it is immediately restarted. When it worked, it worked almost as well as an Ethernet connection for a single session with nothing else active. If I started some activity on a separate session using the same link, things got ssllooww. I later got a lot more experience with slip between two Suns, but never got around to using that experience with a PC. I had long since given up on using SLIP with NCSA_Telnet, and never had a strong reason to try again. Good luck, and let me know if you have any more questions. -David- david@wubios.wustl.edu ^ Mr. David J. Camp david%wubios@wugate.wustl.edu < * > +1 314 382 0584 ...!uunet!wugate!wubios!david v "God loves material things."