alexb@cfctech.cfc.com (Alex Beylin) (10/01/90)
A project have come up around here that require multiple PCs to get dial-in access to the TCP/IP network. One of the major requirements is support for Named Pipes down to the PC. Current plan is to use SLIP and a router with dial-in ports. Would someone care to recommend a PC package that would do good SLIP emulation and a router that would be suitable for this job? Comments, suggestions are most welcome. Thanks in advance, -- Alex Alex Beylin, Unix Specialist | +1 313 948-3386 alexb@cfctech.cfc.com | Chrysler Financial Corp. sharkey!cfctech!alexb | MIS, Distributed Systems ATT Mail ID: attmail!abeylin | Southfield, MI 48034
usenet@b11.ingr.com (Usenet Network) (10/02/90)
in article <1990Oct1.135507.27559@cfctech.cfc.com>, alexb@cfctech.cfc.com (Alex Beylin) says: > > Would someone care to recommend a PC package that would do good > SLIP emulation and a router that would be suitable for this job? --- The company I work for sells PC/NFS. I do not have experiance with the product over serial lines, but PC/NFS (from Sun) does support SLIP. SUN US SALES is listed as: 1-800-821-4643 For routers see cisco or there are terminal servers that support SLIP. I worked for an outfit that sold cisco and the company I work for now sells the Encore Annex II. cisco 415-326-1941 encore (terminal server with slip) 617-460-0500 NOTE: I am not endorsing these products, but they are worth investigation. -- * John E. Allen - Intergraph Corporation - (205) 730-8627 * * System Sales Support * * ingr!b23b!allen!jallen@uunet.uu.net * **************************************************************
jbvb@FTP.COM (James B. Van Bokkelen) (10/03/90)
If you want Named Pipes, you need LAN Manager, which means Netbios, which means RFC 1001/1002 if you want it over TCP/IP. I don't know of any RFC 1001/1002 Netbioses which implement "p-nodes" or "m-nodes", so you can't use a conventional router. TWG has a hack which uses static client configuration to avoid this problem, but a cleaner alternative (IMHO) is to use the cisco SLIP concentrator, which keeps the clients on the same net/subnet as its attached ethernet (fine as long as your servers are on that ethernet). If you use the latter approach, you can use our PC/TCP as well as TWG's WIN/PC. I can never remember if Beame & Whiteside has an RFC Netbios, but none of the others (Excelan, U-B, CMC, Interlan, Bridge) support SLIP. James B. VanBokkelen 26 Princess St., Wakefield, MA 01880 FTP Software Inc. voice: (617) 246-0900 fax: (617) 246-0901
kriger@Xylogics.COM (Sidney Kriger) (10/04/90)
In article <8879@allen.ingr.com> usenet@b11.ingr.com (Usenet Network) writes: >For routers see cisco or there are terminal servers that support SLIP. >I worked for an outfit that sold cisco and the company I work for now >sells the Encore Annex II. > >encore (terminal server with slip) >617-460-0500 > > * John E. Allen - Intergraph Corporation - (205) 730-8627 * > * System Sales Support * > * ingr!b23b!allen!jallen@uunet.uu.net * Xylogics now manufactures the Annex II terminal server and has for about 2 years, not Encore. 800-225-3317 Sidney Kriger Xylogics, Inc. voice: 617-272-8140 53 Third Ave. fax: 617-273-5392 Burlington, MA 01803 email: kriger@Xylogics.COM
SPGDRP@UCCVMA.UCOP.EDU ("Donald R. Proctor") (10/04/90)
>A project have come up around here that require multiple >PCs to get dial-in access to the TCP/IP network. One of the >major requirements is support for Named Pipes down to the PC. >Current plan is to use SLIP and a router with dial-in ports. > >Would someone care to recommend a PC package that would do good >SLIP emulation and a router that would be suitable for this job? > Alex: We intend on implementing a similar system here, although we don't have the named pipes requirement. We have a cisco terminal server that can be configured with several dial-in ports. The software angle is a bit more complex. As I understand it, the remote PC user will need to use a communications package like kermit or xmodem to connect to the terminal server. A commercial (such as FTP's PC/TCP) or public domain (such as NCSA telnet) TCP-IP package can then be run over SLIP. FTP's package can be ordered with SLIP, and there is a SLIP driver in Clarkson's pd packet driver distribution. I should point out that cisco's box can provide the telnet connection itself, so that a remote PC user can dial in and start a telnet session from the server without having the TCP-IP software installed on the PC. However, if need 3270 emulation (as we do), the current release of the cisco's software won't do the job. I hope my more knowledgeable colleagues will correct me if I have made any egregious errors... Don Proctor <spgdrp@uccvma.ucop.edu> Information Systems & Computing <spgdrp@uccvma.bitnet> University of California 415/987-0356
ljm@MERCURY.TWG.COM (10/05/90)
>A project have come up around here that require multiple >PCs to get dial-in access to the TCP/IP network. One of the >major requirements is support for Named Pipes down to the PC. >Current plan is to use SLIP and a router with dial-in ports. > >Would someone care to recommend a PC package that would do good >SLIP emulation and a router that would be suitable for this job? > Given your Named Pipes requirement, you actually have a much more fun problem to solve. You need a TCP/IP with support for not only SLIP but also NetBIOS over TCP/IP which works through IP routers. I think we are currently the only TCP/IP product with both, but I think FTP Software will be able to provide a NetBIOS which works through routers in the near to medium future. By the way, I do have to ask. Why Named Pipes? enjoy, leo j mclaughlin iii ljm@twg.com
bill@polygen.uucp (Bill Poitras) (10/05/90)
Phil Karn's KA9Q package would do just fine. KA9Q is a program that allows connection to the PC via ftp, telnet, smtp, et. al. at the same time. It has a builtin multitasking mechanism. It also supports slip, and routing. I have used it for a slip to ethernet router before. You can find it on thumper.bellcore.com under the /pub/ka9q directory.
raj@hpindwa.HP.COM (Rick Jones) (10/05/90)
A few new-to-named-pipes questions... Am I correct in assuming that it is the 'non-passing' for certain IP/UDP broadcast packets that prevents 'stock' named-pipes from working across IP routers? If that is the only reason, then could one expect named-pipes to work across a router that could be configured to pass these broadcasts in a controlled manner? (no loops and all that...) inquireing minds and all... rick ___ _ ___ |__) /_\ | Richard Anders Jones | MPE/XL Networking Engineer | \_/ \_/ Hewlett-Packard Co. | 'Tis nobler to suffer... ------------------------------------------------------------------------ Being an employee of a Standards Company, all Standard Disclaimers Apply
peiffer@cs.umn.edu (Tim Peiffer (The Net Guy)) (10/06/90)
In article <9987@xenna.Xylogics.COM> kriger@Xylogics.COM (Sidney Kriger) writes: >In article <8879@allen.ingr.com> usenet@b11.ingr.com (Usenet Network) writes: >>I worked for an outfit that sold cisco and the company I work for now >>sells the Encore Annex II. >Xylogics now manufactures the Annex II terminal server and has for about >2 years, not Encore. 800-225-3317 I have both the Encore and Xylogics varients of the Annex II terminal server running some ports under slip. I am very happy with the ease in configuration, but I would like to see something that supports the Van Jacobsen hdr compression algorithms( RFC 1144). Does anyone know of a product that supports this scheme? SLIP is sssoooo easy to configure slip on an Annex. It seems like a shame to waste it, but ftp and telnet are so gawdawfully slow even over a 38.4k link that I still resist putting it in place. For those that care, Xylogics is the Manufacturer of the Annex now, but Encore still oem's the product, and they have their own software line to support the normal Encore line of multimaxen. Tim -- ----------- Tim Peiffer peiffer@cs.umn.edu or Computer Science Dept ..!rutgers!umn-cs!peiffer University of Minnesota
BILLW@MATHOM.CISCO.COM (William "Chops" Westfield) (10/08/90)
Does anyone know of a product that supports [cslip]? SLIP is sssoooo easy to configure slip on an Annex. It seems like a shame to waste it, but ftp and telnet are so gawdawfully slow even over a 38.4k link that I still resist putting it in place. Really? FTP is slow? Our experience at cisco (with our own terminal servers, of course) was that FTP was quite zippy - the sliding window of TCP bought you much more than you lost from the big headers. Compared to DEC-20 to PC kermit, FTP's FTP over slip was nearly twice as fast. Telnet, however, was quite painful, and I don't even want to think about running telnet and FTP at the same time. BillW -------
fortinp@bwdls56.bnr.ca (Pierre Fortin) (10/10/90)
In article <12628063537.11.BILLW@mathom.cisco.com>, BILLW@MATHOM.CISCO.COM (William "Chops" Westfield) writes: > > Does anyone know of a product that supports [cslip]? SLIP is > sssoooo easy to configure slip on an Annex. It seems like a shame > to waste it, but ftp and telnet are so gawdawfully slow even over > a 38.4k link that I still resist putting it in place. > > Really? FTP is slow? Our experience at cisco (with our own terminal > servers, of course) was that FTP was quite zippy - the sliding window > of TCP bought you much more than you lost from the big headers. Compared > to DEC-20 to PC kermit, FTP's FTP over slip was nearly twice as fast. Care to share the test configuration with us? I use SLIP over a Microcom AX/9624c MNP Class 6 modem and a cisco terminal server. I see the modem lights grinding away, waiting..., grinding away, waiting..., etc. It's almost as though the VJ algorithms were throttling... I found I could get more files through by starting 2-3 FTPs so that one is still running when the other 1-2 are stalled. Sort of round-robin FTP transfers; doesn't work if I've only got one file to transfer though... :^( > > Telnet, however, was quite painful, and I don't even want to think about > running telnet and FTP at the same time. When you're FTPing and your only link is tied up, you're quite happy to be able to get *any* response to keep working. If only I had what ammounts to "local echo" or tn3270-type buffering on telnet over SLIP... sigh. > > BillW > ------- Pierre Fortin Bell-Northern Research I know, my postings are Internet Systems P.O.Box 3511, Stn C terse and humourless. So? (613)763-2598 Ottawa, Ontario RIP: aptly named protocol fortinp@bnr.ca Canada K1Y 4H7 AppleTalk: Adam&Eve's design
BILLW@MATHOM.CISCO.COM (William "Chops" Westfield) (10/11/90)
> > Really? FTP is slow? Our experience at cisco (with our own terminal > servers, of course) was that FTP was quite zippy - the sliding window > of TCP bought you much more than you lost from the big headers. Compared > to DEC-20 to PC kermit, FTP's FTP over slip was nearly twice as fast. Care to share the test configuration with us? I use SLIP over a Microcom AX/9624c MNP Class 6 modem and a cisco terminal server. I see the modem lights grinding away, waiting..., grinding away, waiting..., etc. It's almost as though the VJ algorithms were throttling... I found I could get more files through by starting 2-3 FTPs so that one is still running when the other 1-2 are stalled. Sort of round-robin FTP transfers; doesn't work if I've only got one file to transfer though... :^( The configuration was a 286 based PC clone running either (old, non-sliding window, 92 byte packet) MSDOS kermit or FTP software's package v 1.16, connected vai a 19.2kbps direct line to aa cisco terminal server (v6.1 software? This was slightly before SLIP was released on the cisco TS) We were talking to either HPUX or TOPS20 (no VJ algorthims in sight!) FTP software was configured with a window size of 1024, and an MSS of 512, if I remember correctly. It's sort of important (with no slow start) that the number of MSS packets in a window be both larger than 1 and smaller than the effective queue-size on the terminal server (then 3, now settable). (Your description of the problem sounds exactly like the MSS is > window/2, so that you end up operating lock-step instead of sliding windows, by the time SWS algorithms come into play.) FTP file transfer speeds were about 13kbps, while kermit was about half that. I haven't done those tests in a couple of years, though - I would hope that everything still works at least as well as it did then! Bill Westfield cisco Systems. -------