Kurt,
To reach from one DECnet node to another without explicitly supplying account/password
info you need Proxy enabled in & out on each system and the proxy defined. RSX has a
proxy task in [5,54] that defines those.
With out proxy you can do this
Dir ALDIR?Account password?::
Or
DIr ALDIR/Account/password::
Have fun,
Mark
Sent from my iPhone
On Jun 8, 2019, at 2:12 PM, Kurt Hamm <kurt at
hamm.me> wrote:
Well, I think it is done. I can set host to the pdp-11 from my local vax3900. The
pdp-11 doesn't seem to know the other nodes. I also can't get a shared directory
(dir aldur::).
I will keep reading.
Kurt
> On Sat, Jun 8, 2019 at 12:35 PM Johnny Billquist <bqt at softjar.se> wrote:
> Mark...
>
> On 2019-06-08 18:25, Mark Matlock wrote:
> > Kurt,
> > You are getting close. You have a -26. (File not found) Error on the file
LB:{5,54]IP.STB
>
> Indeed.
>
> > The IPGEN process should copy three files IP.STB IP.TSK and IP.TSK into
LB:[5,54] but
> > Since they are not there, you can copy them from [IPNET] to [5,54]
>
> They are only copied if you answer YES to the related question when
> running IPGEN.
>
> There are actually a couple of more files installed. I can't remember
> now if any might be optional, but anyway:
>
> PIP [5,54]/NV=[IPNET]*.DAT,IP.TSK,IP.STB
> PIP [5,24]/NV=[IPNET]IP.OBJ
> LBR [130,10]NETLIB.MLB/RP=[IPNET]IPDF.MAC
>
> You should then run the NETGEN procedure after these files have been
> copied, and then NETGEN should run fine, and then you run
> [IPNET]IPNEY.CMD after NETGEN have completed. Then you can try starting
> DECnet, and once DECnet is started, you can try bringing up the DECnet
> over IP lines.
>
> Johnny
>
> >
> > Best,
> > Mark
> >
> >
> >> On Jun 8, 2019, at 10:04 AM, Kurt Hamm <kurt at hamm.me> wrote:
> >>
> >> Well, this was really good information. Mark, the walk-through was
extremely helpful. I feel like I am almost there.
> >>
> >> There is something I am missing related to the final step. I added this line
to the end of startup.cmd: @LB:[IPNET]INS.CMD. Not sure if that is the correct way to
call that CMD file.
> >>
> >> I am not exactly sure about the content changes especially the ports:
> >> MNC SET CIR IP-0-0 TCA HOST 192.168.1.49:7705 PORT 0
> >> NCP SET CIR IP-0-0 STA ON
> >>
> >> When I run [ipnet]ins.cmd:
> >>> @LB:[IPNET]INS.CMD
> >>> INS LB:[IPNET]MLTCOM/UIC=[1,54]/PRO=[RW,RW,,]
> >>> INS LB:[IPNET]MLTNET
> >>> INS LB:[IPNET]MLTCFG
> >>> NCP SET PROC IP TOP
> >> NTL -- IP Symbol Table File -- Open Failure (-26.)
> >> NTL -- LB:[5,54]IP.STB
> >> NCP -- Set failed, operation failure
> >> Network Loader function failed
> >>> NCP SET LIN IP-0-* ALL
> >> NTL -- IP Symbol Table File -- Open Failure (-26.)
> >> NTL -- LB:[5,54]IP.STB
> >> NCP -- Line IP-0-0, Set failed, operation failure
> >> Network Loader function failed
> >> NTL -- IP Symbol Table File -- Open Failure (-26.)
> >> NTL -- LB:[5,54]IP.STB
> >> NCP -- Line IP-0-1, Set failed, operation failure
> >> Network Loader function failed
> >>> MNC SHO VER
> >> Initialize common
> >> NT.IP not loaded. Please load before running this tool.
> >>> MNC SET CIR IP-0-0 TCA HOST 192.168.1.49:7705 PORT 0
> >> Initialize common
> >> NT.IP not loaded. Please load before running this tool.
> >>> NCP SET CIR IP-0-0 STA ON
> >> NCP -- Set failed, component in wrong state, Line
> >>> @ <EOF>
> >>
> >>
> >>
> >> On Sat, Jun 8, 2019 at 8:34 AM Johnny Billquist <bqt at softjar.se>
wrote:
> >> In addition to the information and transcript Mark provided, do not
> >> forget to run the post-processing script from IPNET after completing the
> >> NETGEN procedure. It will modify the DECnet configuration somewhat to
> >> more correctly handle the IP lines.
> >>
> >> And no, Kurt is not connecting directly to Mim, but possibly just
> >> between his own machines, and otherwise being hooked up to area 31.
> >>
> >> Johnny
> >>
> >> On 2019-06-08 14:13, Mark Matlock wrote:
> >>> Kurt,
> >>> As Johnny says you should read chapter 10 of [IP]README.DOC and run
a NETGEN to add the IP HECnet device. I?ve attached a walk-through of a NETGEN that can
help guide you but you should understand the information in chapter 10.
> >>>
> >>> You should have a unique DECnet node address for your system (from
Johnny) to use instead of the one I supplied in the walk-through.
> >>>
> >>> Later when bringing up IP-0-0 in the [IPNET]INS.CMD I think you
need a port # for attachment to MIM if that is where you are connecting to?
> >>>
> >>> Best,
> >>> Mark
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>> On Jun 8, 2019, at 6:36 AM, Kurt Hamm <kurt at hamm.me>
wrote:
> >>>>
> >>>> Thanks Johnny and thanks Mark. For some reason I thought that this
was already done since IP was working.
> >>>>
> >>>> This is just what I needed to know to finish this thing off. I
really appreciate the assistance.
> >>>>
> >>>> Kurt
> >>>>
> >>>> On Sat, Jun 8, 2019, 5:32 AM Johnny Billquist <bqt at
softjar.se> wrote:
> >>>> Kurt, Mark is absolutely right.
> >>>>
> >>>> You do not have the IP line driver generated into DECnet.
> >>>>
> >>>> This is what I suspect quite a few mails back between us, and tried
to
> >>>> point out.
> >>>>
> >>>> And do not try to just edit CEMAC.MAC to add those lines Mark
mention.
> >>>> That will not work. You need to run through the DECnet generation
> >>>> process, and then the IPNET postprocessing step. It's all in the
TCP/IP
> >>>> manual, if you read it.
> >>>>
> >>>> Johnny
> >>>>
> >>>> On 2019-06-08 05:58, Mark Matlock wrote:
> >>>>> Kurt,
> >>>>> I think you need to have the ?IP" network device
NETGENed into DECnet.
> >>>>>
> >>>>> The fact that you first error occurs at the NCP SET PROC IP
TOP makes me think that DECnet does not have a driver for the IP device loaded. When I
made the ?Frodo? distribution available, I did a new SYSGEN for an 11/70 and also a
NETGEN. In the NETGEN for the Unibus system a ?UNA? was the ethernet device and on a Qbus
system (the actual Frodo 30.1) a QNA device is used.
> >>>>>
> >>>>> It would be helpful if you typed out LB:[5,54]CETAB.MAC as
it could confirm if the IP device has been NETGENed in or not. In CETAB.MAC the 3rd actual
line of code should look like:
> >>>>>
> >>>>> PDV$DF
<AUX,EVL,ECL,XPT,NCT,RTH,LAT,DLX>,<EPM>,<UNA,IP>
> >>>>>
> >>>>> Three lines below that should be:
> >>>>>
> >>>>> SLT$DF IP,IP,XPT,LF.TIM,0,0,,0.,0.,15.
> >>>>>
> >>>>> It?s been a while since I added the IP-0-0 LIN and
Circuits to my system, but I try to do that to one of my PiDP-11s and post the walk
through for it.
> >>>>>
> >>>>> Below I?ve put some information of the sequence of startup
command files that may help you understand the files involved.
> >>>>>
> >>>>> In the LB:[1,2]STARTUP.CMD of the Frodo distribution RSX
and DECnet are started as is normal for any RSX. It then chains to LB:[1,2]INSPROG.CMD
which brings up the DU1: disk that you either download from
RSX11M.COM or the Simh
boot.ini will make a blank one.
> >>>>>
> >>>>> At the end of the INSPROG.CMD two questions are asked with
timeouts. The first will load LAT and the second loads Johnny?s TCP/IP. It loads the
TCP/IP by chaining to LB:[IP]IPINS.CMD which will load TCP/IP and either DHCP an IP
address or set a static IP address. At the end of that file then LB:[IP]IPAPPL.CMD is
executed which sets up FTP, TELNET, NTP and other applications.
> >>>>>
> >>>>> Now, in the Frodo distribution IPAPPL.CMD, there is a line
that was either commented or deleted that chains to LB:[IPNET]INSHECNET.CMD which is used
to link the actual node Frodo (HECnet 30.1) to MIM
> >>>>>
> >>>>> Your [IPNET]INS.CMD looks identical to the INSHECNET.CMD on
Frodo including the host port # which may be something we need to change?
> >>>>>
> >>>>> Do you have a HECnet address from Johnny? Also, where are
you planning to connect to HECnet?
> >>>>>
> >>>>> There is a [IPNET]INS.NEW which is the template that Johnny
provides and it does not have a port specified on MIM. I don?t remember the exact
mechanics on MIM That accepts connections but that may be a function of that port # Frodo
connects to MIM on IP-0-10 but that is not specified on Frodo but on MIM.
> >>>>>
> >>>>> Best,
> >>>>> Mark
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On Jun 7, 2019, at 9:35 PM, Kurt Hamm <kurt at
hamm.me> wrote:
> >>>>>>
> >>>>>> So, I added this command to the startup.cmd:
@LB:[IPNET]INS.CMD.
> >>>>>>
> >>>>>> I didn't modify the file yet. I wanted to see what it
would do
> >>>>>>
> >>>>>> The result after rebooting was this:
> >>>>>>> INS LB:[IPNET]MLTCOM/UIC=[1,54]/PRO=[RW,RW,,]
> >>>>>>> INS LB:[IPNET]MLTNET
> >>>>>>> INS LB:[IPNET]MLTCFG
> >>>>>>> NCP SET PROC IP TOP
> >>>>>> NCP -- Set failed, unrecognized component, Process
> >>>>>>> NCP SET LIN IP-0-* ALL
> >>>>>> NCP -- Set failed, invalid identification format, Line
> >>>>>>> MNC SHO VER
> >>>>>> Initialize common
> >>>>>> NT.IP not found. Exiting...
> >>>>>>> MNC SET CIR IP-0-0 TCA HOST MIM.UPDATE.UU.SE:7705 PORT
0
> >>>>>> Initialize common
> >>>>>> NT.IP not found. Exiting...
> >>>>>>> NCP SET CIR IP-0-0 STA ON
> >>>>>> NCP -- Set failed, invalid identification format, Circuit
> >>>>>>
> >>>>>> There are lots of errors, so I am not sure where to start.
> >>>>>>
> >>>>>> Any advice would be appreciated.
> >>>>>>
> >>>>>> Kurt
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Johnny Billquist || "I'm on a bus
> >>>> || on a psychedelic trip
> >>>> email: bqt at softjar.se || Reading murder books
> >>>> pdp is alive! || tryin' to stay hip" -
B. Idol
> >>>
> >>
> >>
> >> --
> >> Johnny Billquist || "I'm on a bus
> >> || on a psychedelic trip
> >> email: bqt at softjar.se || Reading murder books
> >> pdp is alive! || tryin' to stay hip" - B.
Idol
> >
>
> --
> Johnny Billquist || "I'm on a bus
> || on a psychedelic trip
> email: bqt at softjar.se || Reading murder books
> pdp is alive! || tryin' to stay hip" - B. Idol