Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA Path: utzoo!watmath!clyde!cbosgd!ulysses!ucbvax!columbia.edu!OC.GARLAND%CU20B From: OC.GARLAND%CU20B@COLUMBIA.EDU (Richard Garland) Newsgroups: fa.info-vax Subject: Re: jnet/DECnet question Message-ID: <8509072149.AA26309@UCB-VAX.ARPA> Date: Sat, 7-Sep-85 10:17:02 EDT Article-I.D.: UCB-VAX.8509072149.AA26309 Posted: Sat Sep 7 10:17:02 1985 Date-Received: Mon, 9-Sep-85 02:51:26 EDT References: Sender: daemon@ucbvax.ARPA Reply-To: info-vax@ucb-vax.berkeley.edu Organization: The ARPA Internet Lines: 25 jnet/DECnet question: You can do 2 things: 1) get a proper license and run jnet on B and run a logical jnet link from A to B over DECnet. This is supported in the announced and soon to be released version of jnet (talk to the vendor: Joiner Associates). We have been beta testing this type of linkage for a long time and it works fine. We have 1 link to an IBM host (using a DUP-11) and 3 links to other VAXes using logical links over DECnet circuits. They all look the same to the user level, and the remote hosts coming in over DECnet see the rest of BITnet just as they would as if we were an IBM host (heaven forbid). 2) Run some gateway software which will relay mail from BITnet to DECnet hosts (those hosts would run no special software). There is an unsupported gateway package which we have which you *may* be able to get from the supplier of jnet. Note: I have no connection with Joiner Associates other than as a beta test site and speak only from my own opinions and experience. Nothing said here should (or can) be construed as a commitment by them for any software. Rg -------