home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!ADMIN.HUMBERC.ON.CA!PETCH
- Message-ID: <IBM-MAIN%92091414405697@VM1.CC.UAKRON.EDU>
- Newsgroups: bit.listserv.ibm-main
- Date: Mon, 14 Sep 1992 14:27:43 EDT
- Sender: IBM Mainframe Discussion list <IBM-MAIN@RICEVM1.BITNET>
- From: "Paul R. Petch" <PETCH@ADMIN.HUMBERC.ON.CA>
- Subject: Re: Bitnet vs Internet
- Comments: To: IBM Mainframe Discussion List <IBM-MAIN@VM1.CC.UAKRON.EDU>
- In-Reply-To: Message of Mon,
- 14 Sep 1992 12:19:44 EDT from
- <STAN%VM.TEMPLE.EDU@VM1.CC.UAKRON.EDU>
- Lines: 16
-
- This is from Humber College in Ontario, Canada. We continue to have a
- Bitnet address but only run an Internet (in our case ONet) line. The
- trick is to continue with your Bitnet ADDRESS but to use the so-called
- Bitnet II approach. At your site you run a VMNET machine which takes
- the encapsulated RSCS traffic from TCPIP and puts it through a VCTCA
- to RSCS. RSCS goes ahead and routes all traffic to the outside world
- through this link. Now, what you also need is some kind soul who
- continues to have both and Internet and a Bitnet service who ALSO
- runs VMNET. Individual streams come from the two nets to that
- site and then get combined (i.e. RSCS is encapsulated) and it gets
- passed along to you. Our CMS users continue to use all features
- of Bitnet and RSCS, we continue to run a LISTSERV and the good old
- CMS commands like TELL and MSG and SENDFILE continue to work through
- RSCS just as before.
-
- Hope this is of some help.
-