epc1@ra.MsState.Edu (Ellis P. Carter Jr.) (01/30/91)
I heard of a program called slip that makes your serial port a virtual ethernet port. The version I found, though, is in SunOS format. Does anyone know where I can get a version of slip for the sysv386 unix? Perhaps an anonymous ftp site. Any help will be greatly appreciated! Also, if you happen to be a slip guru, and wish to divulge some basic info about slip so that I can get famillar with it BEFORE reading the doc files, feel free to send me some mail. Please mail your responses to: Ellis P. Carter Jr. epc1@ra.msstate.edu
wilko@idca.tds.PHILIPS.nl (W.C. Bulte) (01/31/91)
In article <1019@ra.MsState.Edu> epc1@ra.MsState.Edu (Ellis P. Carter Jr.) writes: >I heard of a program called slip that makes your serial port a virtual >ethernet port. The version I found, though, is in SunOS format. Does anyone >Also, if you happen to be a slip guru, and wish to divulge some basic info Please, let the aforementioned slip guru post the responses to this news group. I sure like to know more about slip also _ ______________________________________________________________________ | / o / / _ Wilko Bulte Domain: wilko@idca.tds.philips.nl |/|/ / / /( (_) uucp : [mcsun,hp4nl]!philapd!wilko * Philips Information Systems Nederland phone: 055-432372 fax: 055-432103 ____________________________________________________________________________
s900387@minyos.xx.rmit.oz.au (Craig Macbride) (02/01/91)
Well, SLIP in ISC's version 2.2 certainly works ... well, for most things, anyway. rcp, rlogin, and so on across a serial line are not too slow (if you are used to modems!), but if I attempt to use talk, it sits and puts up a message about contacting the other machine. Unfortunately that's all it does: put up a message. It will sit there all day if you let it, without any sign of activity at the other machine. Admittedly, the documentation is pathetic, and assumes you already know what you are doing. Basically (for ISC, at least), you set up net addresses on machines, configure them to use run state 3 to start up inetd, and insert appropriate calls to slattach in some rc.d file for that run state. (The last of these is not done for you by the system admin menus, which also fail to create the sl login account, as the script for this is missing from the 2.2 distribution!!!) -- _____________________________________________________________________________ | Craig Macbride, s900387@minyos.xx.rmit.oz.au | Reality is for people who | | Only the equipment belongs to Victoria Uni. | can't handle science fiction.| | of Technology (RMIT); The opinions are mine. |______________________________|
jim@piggy.ucsb.edu (Jim Lick) (02/02/91)
In article <1991Feb1.130904.14880@minyos.xx.rmit.oz.au> s900387@minyos.xx.rmit.oz.au (Craig Macbride) writes: >Well, SLIP in ISC's version 2.2 certainly works ... well, for most things, >anyway. rcp, rlogin, and so on across a serial line are not too slow (if you >are used to modems!), but if I attempt to use talk, it sits and puts up a >message about contacting the other machine. Unfortunately that's all it does: >put up a message. It will sit there all day if you let it, without any sign of >activity at the other machine. This is a common problem. The problem is that there is more than one 'standard' for talk. In particular, I understand that there is a big difference between the versions for 4.2 and 4.3 BSD, and many machines use the former, while some use the latter. I've also heard that there is also a byte-order problem, but haven't had this confirmed. In practice, since I use Sun computers mostly, I can pretty much only talk to other Sun systems. I've heard that you can sort of solve this by getting the BSD sources to talk and compile it, but this still leaves a lot to be desired. I prefer to take a different route and use either irc, Tinymud, or another 'chat' system. In any case, ISC is not really to blame for this problem. Jim Lick Work: University of California | Home: 6657 El Colegio #24 Santa Barbara | Isla Vista, CA 93117-4280 Dept. of Mechanical Engr. | (805) 968-0189 voice/msg 2311 Engr II Building | (805) 968-1239 data (805) 893-4113 | (805) 968-2734 fax jim@ferkel.ucsb.edu | Soon: jim@cave.sba.ca.us
larry@nstar.rn.com (Larry Snyder) (02/02/91)
wilko@idca.tds.PHILIPS.nl (W.C. Bulte) writes: >Please, let the aforementioned slip guru post the responses to this news >group. I sure like to know more about slip also slip comes with Interactive Unix - and we use it here in nstar - as a matter of fact, MCI is installing a dedicated line next week and we have a pair of USR V.32 with v.32bis modems here - and tests are yielding around 2.4 kb/sec doing ftp over the pair of modems.. -- Larry Snyder, NSTAR Public Access Unix 219-289-0287 (HST/PEP/V.32/v.42bis) regional UUCP mapping coordinator {larry@nstar.rn.com, ..!uunet!nstar!larry, larry%nstar@iuvax.cs.indiana.edu}
alexb@cfctech.cfc.com (Alex Beylin) (03/03/91)
In article <1113@idcapd.idca.tds.philips.nl> wilko@idca.tds.PHILIPS.nl (W.C. Bulte) writes: >Please, let the aforementioned slip guru post the responses to this news >group. I sure like to know more about slip also > Better yet, have anyone ported PPP to 386 platform yet? It is my understanding that PPP is meant to replace SLIP. Performance should be much better. FTP Software should be releasing PPP for DOS drivers Real Soon Now, according to the sales office. Alex Beylin, Systems Specialist | +1 313 759-7114 alexb@cfctech.cfc.com | Chrysler Corp. MIS sharkey!cfctech!alexb | Distributed Systems Group