guerra@lance.tis.llnl.gov (Frank Guerra) (09/07/90)
I've looked thorugh ftp archives, I've asked other newsgroups, I've been up and down the mountain and still I have not found an implementation of SLIP for the 3b2. I hope that someone in this newsgroup can be of SOME assistance. I've seen references to the osu-cis archive. What is it's full name and IP address? All really useful comments will probably receive some small token of my eternal gratitude (hint : this is a bribe). Frank guerra@lance.tis.llnl.gov
woods@eci386.uucp (Greg A. Woods) (09/07/90)
In article <1035@ncis.tis.llnl.gov> guerra@lance.tis.llnl.gov (Frank Guerra) writes: > I've looked thorugh ftp archives, I've asked other newsgroups, I've been > up and down the mountain and still I have not found an implementation of > SLIP for the 3b2. I hope that someone in this newsgroup can be of SOME > assistance. I've seen references to the osu-cis archive. What is it's > full name and IP address? All really useful comments will probably receive > some small token of my eternal gratitude (hint : this is a bribe). I would guess that there is at least one (commercial) implementation of SLIP available. It would be in the WIN/3B products, if anywhere, available from AT&T. Do you have TCP/IP (i.e. WIN/3B) for your 3B? If not, a simple SLIP implementation won't do you much good. I would also guess that if you could find any implementation of TCP/IP and/or SLIP for SysV STREAMS, it could be hammered into working on a 3B2, given that you don't mind mucking with kernel level code, and that you know something about TCP/IP. I've not actually tried this yet, though I hope to in the near future. I'm thinking particularly of some STREAMS modules I've heard rumors about. They supposedly implement TCP/IP, SLIP, and AX.25. The last place I heard anything about them is in the proceedings of last year's "ARRL Annual Computer Networking Conference". The "10'th Annual Computer Networking Conference", sponsored by the ARRL and CRRL, will be held in London, Ontario, Canada on Sept. 22. I hope to hear more about these drivers and other neat things there. -- Greg A. Woods woods@{eci386,gate,robohack,ontmoh,tmsoft}.UUCP +1-416-443-1734 [h] +1-416-595-5425 [w] VE3-TCP Toronto, Ontario CANADA
lyndon@cs.athabascau.ca (Lyndon Nerenberg) (09/12/90)
woods@eci386.uucp (Greg A. Woods) writes: >I would guess that there is at least one (commercial) implementation >of SLIP available. It would be in the WIN/3B products, if anywhere, >available from AT&T. Sorry. No such luck. -- Lyndon Nerenberg VE6BBM / Computing Services / Athabasca University {alberta,cbmvax,mips}!atha!lyndon || lyndon@cs.athabascau.ca The only thing open about OSF is their mouth. --Chuck Musciano
fmcgee@cuuxb.ATT.COM (~XT6561110~Frank McGee~C23~L25~6326~) (09/14/90)
In article <1990Sep7.164810.9259@eci386.uucp> woods@eci386.UUCP (Greg A. Woods) writes: >In article <1035@ncis.tis.llnl.gov> guerra@lance.tis.llnl.gov (Frank Guerra) writes: >I would guess that there is at least one (commercial) implementation >of SLIP available. It would be in the WIN/3B products, if anywhere, >available from AT&T. I know atleast for the 386 UNIX products Wollongong has SLIP for their 3.x version of TCP/IP (AT&T TCP/IP version 3.0 is essentially the same as the product from Wollongong). They probably also have a version for the 3B's as well. If you call them directly, they'll let you know. It does cost $$, but I don't know how much. You can reach the Wollongong Group at 1-800-872-8649. Note that on 386 UNIX, there are two ways to do TCP/IP; one is with the TCP/IP Interface for UNIX and the other is with the 386 WIN (Wollongong Integrated Networking) and a StarLAN 10 Mb NAU. The TCP/IP Interface for UNIX includes both hardware and software, and has a coax interface. For the other solution, you have to purchase both the WIN product and a 10 Mb StarLAN NAU (they are separate products). The important thing to keep in mind is that the two solutions are considerably different, and you can't run WIN on the TCP/IP Interface for UNIX hardware. But that only applies to the 6386 family of products. Hope this helps you out, -- Frank McGee, AT&T Entry Level Systems Support attmail!fmcgee (preferred) att!cuuxb!fmcgee (those that can't reach attmail)