From: SMTP%"CMU-OpenVMS-IP@DRYCAS.CLUB.CC.CMU.EDU" 11-OCT-1994 09:42:35.56 To: EVERHART CC: Subj: RE: ip over decnet config Date: 10 Oct 94 21:58:34 -0700 From: Vanya J. Cooper (Vanya Cooper) Subject: RE: ip over decnet config To: CMU-OpenVMS-IP@DRYCAS.CLUB.CC.CMU.EDU Errors-To: CMU-OpenVMS-IP-Request@DRYCAS.CLUB.CC.CMU.EDU Reply-To: CMU-OpenVMS-IP@DRYCAS.CLUB.CC.CMU.EDU Message-Id: <1994Oct10.215834.10515@pimacc.pima.edu> X-Newsgroups: vmsnet.networks.tcp-ip.cmu-tek Lines: 49 X-Gateway-Source-Info: USENET (Sorry I missed the original post so I don't know who I'm talking to.) >> I have 2 machines across town from each other running a 56kb decnet link >> between them. I would like to also add tcp/ip without buying a router >> to allow access to some sun's via a remote x-window over tcp/ip. >> >> Looking though the cmu-tek doc I see that it supports ip over decnet. >> Both machines are in a cluster and I would like to keep the ip over >> the ethernet up on both machines. One of the machines directly connected >> to the modem is running multinet so I'm not sure this will even work. >> >> The first question is - do both machines have to be directly connected to >> the modem, or just in contact via decnet? > > They have to be in contact just via DECnet. It has to be CMU to CMU; CMU >to Multinet won't work. I believe the remainder of the post was correct, but I'm afraid I'll have to disagree with the CMU/Multinet part. I'm connected right now over a CMU to Multinet IP over async DECnet (dial-up over LAT, but you don't want to know that) connection. I THINK all I had to do was to change the 4th parameter on the CMU side to IP_destination-node to match the task name Multinet was looking for. I found this out by looking at the TASK objects on both sides while they were trying to connect. There could have been something else minor I had to change that seemed obvious at the time and I am not remembering, but it definitely does work. I'm running Multinet V3.2 Rev and CMUIP V6.6-5, here is the configuration: Multinet side (DECnet node YETI, IP addr:144.90.128.15): se0 (Shared VMS Ethernet/FDDI) -NONE- -NONE- -NONE- [TCP/IP: 144.90.128.5, IP-SubNet: 255.255.255.0] [VMS Device: ESA0, Link Level: Ethernet] dn0 (IP over DECnet link) -NONE- -NONE- -NONE- [TCP/IP: 144.90.128.15==>144.90.128.42, IP-SubNet: 255.255.255.0] [DECnet-Peer: VJCVS2] and on the the CMU side (DECnet node VJCVS2, IP addr: 144.90.128.42): Device_Init:DNDRV:YETI:IP_VJCVS2:144.90.128.42:255.255.255.0 Good luck ..Vanya Vanya Jonathan Cooper (VJC) Pima Community College vcooper@pimacc.pima.edu District Computer Services (602) 748-4809 4903 East Broadway Blvd Tucson, Arizona 85709-1280 USA