8 Jun
2019
8 Jun
'19
4:35 a.m.
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
8 Jun
8 Jun
5:58 a.m.
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 
11:32 a.m.
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
--
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
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
1:36 p.m.
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
--
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
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
2:13 p.m.
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
2:34 p.m.
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
--
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
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
--
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 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
5:04 p.m.
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:
--
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
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
6:25 p.m.
Kurt,
You are getting close. You have a -26. (File not found) Error on the file
LB:{5,54]IP.STB
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]
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
--
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 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
6:35 p.m.
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
--
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
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
9:12 p.m.
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:
--
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
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
9:31 p.m.
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
3:11 p.m.
He has definitely said that more than once. I just wasn't getting it.
Sorry about that Johnny.
Kurt
On Sat, Jun 8, 2019, 8:14 AM Mark Matlock <mark at matlockfamily.com> 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
--
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 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
4:32 p.m.
Mark,
1) How does one get a copy of the ?FRODO distribution??
2) if possible, I would like a redundant MULTINET TCP connection to your area from IMPVAX
which can be a server or a client.
Best,
Supratim
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
On Jun 8, 2019, at 9:11 AM, Kurt Hamm <kurt at
hamm.me> wrote:
He has definitely said that more than once. I just wasn't getting it.
Sorry about that Johnny.
Kurt
> On Sat, Jun 8, 2019, 8:14 AM Mark Matlock <mark at matlockfamily.com> 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
>
6:17 p.m.
Supratim,
#1 is easy:
wget http://rsx11m.com/PiDP11_DU0.zip
This is a RSX11M+ V4.6 sysgened for the PiDP-11/70 with most all the common programming
languages including APL, DTR, BP2 V2.7, F77, etc.
wget http://rsx11m.com/PiDP11_DU1.zip
This is a 1.5 GB disk when upzipped that has all the RSX Sig tapes that are available as
.dsk files that can be accessed with VCP.
On #2, my current home ethernet connection is dynamic and has some outages at times. My
vacation / retirement home in Texas where I?ll be moving to in ~ September has gigabit
fiber-optic internet on a static IP. That is where it would make sense to set up a
redundant multinet TCP connection. I?ll probably be there around the 4th of July and
perhaps we could set something up there then?
Best,
Mark
On Jun 8, 2019, at 9:32 AM, Supratim Sanyal
<supratim at riseup.net> wrote:
Mark,
1) How does one get a copy of the ?FRODO distribution??
2) if possible, I would like a redundant MULTINET TCP connection to your area from IMPVAX
which can be a server or a client.
Best,
Supratim
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
On Jun 8, 2019, at 9:11 AM, Kurt Hamm <kurt at hamm.me> wrote:
> He has definitely said that more than once. I just wasn't getting it.
>
> Sorry about that Johnny.
>
> Kurt
>
> On Sat, Jun 8, 2019, 8:14 AM Mark Matlock <mark at matlockfamily.com> 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
>
6:58 p.m.
Mark,
#1) awesome - will explore ASAP!
#2) absolutely - will revisit this end of July after we are back from a trip
Thanks much.
/s.
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
On Jun 8, 2019, at 12:17 PM, Mark Matlock <mark at
matlockfamily.com> wrote:
Supratim,
#1 is easy:
wget http://rsx11m.com/PiDP11_DU0.zip
This is a RSX11M+ V4.6 sysgened for the PiDP-11/70 with most all the common programming
languages including APL, DTR, BP2 V2.7, F77, etc.
wget http://rsx11m.com/PiDP11_DU1.zip
This is a 1.5 GB disk when upzipped that has all the RSX Sig tapes that are available as
.dsk files that can be accessed with VCP.
On #2, my current home ethernet connection is dynamic and has some outages at times. My
vacation / retirement home in Texas where I?ll be moving to in ~ September has gigabit
fiber-optic internet on a static IP. That is where it would make sense to set up a
redundant multinet TCP connection. I?ll probably be there around the 4th of July and
perhaps we could set something up there then?
Best,
Mark
On Jun 8, 2019, at 9:32 AM, Supratim Sanyal
<supratim at riseup.net> wrote:
Mark,
1) How does one get a copy of the ?FRODO distribution??
2) if possible, I would like a redundant MULTINET TCP connection to your area from IMPVAX
which can be a server or a client.
Best,
Supratim
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
> On Jun 8, 2019, at 9:11 AM, Kurt Hamm <kurt at hamm.me> wrote:
>
> He has definitely said that more than once. I just wasn't getting it.
>
> Sorry about that Johnny.
>
> Kurt
>
> On Sat, Jun 8, 2019, 8:14 AM Mark Matlock <mark at matlockfamily.com> 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
>
10:07 p.m.
This walkthrough was great.
I do have a question about this the section listed below:
My answers:
01.00 CURLY
02.00 31.132
03:00 Do I really want a routing node?
04:00 Do I really want a routing node?
.
.
07.00 Remote node name [<RET>=Done] Larry
08:00 Remote Node Address: 31.130
I thought the Remote Node address setting would just route decnet through
Larry. I don't really want the pdp-11 (CURLY) doing any routing.
Thanks!
Kurt
;
=====================================================================
; DEC - Section 1 - Define the target and remote nodes
; =====================================================================
;
* 01.00 What is the target node name [S R:0-6]: RSX11M
* 02.00 What is the target node address [S R:0.-8.]: 30.12
* 03.00 Target node ID [D=None] [S R:0.-32.]: PiDP-11/70 HECnet
* 04.00 Do you want to generate a routing node [D=N]? [Y/N]: Y
* 04.01 Do you want to generate a level 2 routing node [D=N]? [Y/N]: Y
* 05.00 Highest node number in this area [D R:12.-1023. D:12.]: 15.
* 05.01 Highest area number in network [D R:30.-63. D:30.]: 63.
;y
; Extended network support for network command terminals and products
; layered on DECnet, will be included.
; [S R:0-6]:
* 07.00 Remote node name [<RET>=Done]
On Sat, Jun 8, 2019 at 8:14 AM Mark Matlock <mark at matlockfamily.com> 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
--
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 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
10:25 p.m.
Kurt,
If you want two circuits like UNA-0 and IP-0-0 I think you have to be a routing node
(but not an area router).
Also, you should define all the nodes you want to talk to with NCP in one of the startup
files or do it with CFE but I prefer startup so it?s simple to change.
Best,
Mark
Sent from my iPhone
On Jun 8, 2019, at 3:07 PM, Kurt Hamm <kurt at
hamm.me> wrote:
This walkthrough was great.
I do have a question about this the section listed below:
My answers:
01.00 CURLY
02.00 31.132
03:00 Do I really want a routing node?
04:00 Do I really want a routing node?
.
.
07.00 Remote node name [<RET>=Done] Larry
08:00 Remote Node Address: 31.130
I thought the Remote Node address setting would just route decnet through Larry. I
don't really want the pdp-11 (CURLY) doing any routing.
Thanks!
Kurt
;
=====================================================================
; DEC - Section 1 - Define the target and remote nodes
; =====================================================================
;
* 01.00 What is the target node name [S R:0-6]: RSX11M
* 02.00 What is the target node address [S R:0.-8.]: 30.12
* 03.00 Target node ID [D=None] [S R:0.-32.]: PiDP-11/70 HECnet
* 04.00 Do you want to generate a routing node [D=N]? [Y/N]: Y
* 04.01 Do you want to generate a level 2 routing node [D=N]? [Y/N]: Y
* 05.00 Highest node number in this area [D R:12.-1023. D:12.]: 15.
* 05.01 Highest area number in network [D R:30.-63. D:30.]: 63.
;y
; Extended network support for network command terminals and products
; layered on DECnet, will be included.
; [S R:0-6]:
* 07.00 Remote node name [<RET>=Done]
> On Sat, Jun 8, 2019 at 8:14 AM Mark Matlock <mark at matlockfamily.com> 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
>
9 Jun
9 Jun
12:12 a.m.
Apparently, the PDP-11 is advertising successfully as a DECNet router. My
VAX node MOE seems to be using it instead of the VAX Router LARRY. Which
is a problem because I can't route through the PDP-11 to MIM.
Well, that is basic understanding. If I turn off PDP-11, the routing from
the VAX node only Moe works fine and it routes through LARRY.
I am looking to see if I can raise the route cost of the PDP-11 to make
LARRY win the routing contest every time. Othewise, I will re-run netgen
on the PDP-11 and say no to being a router (Level 1 and Level 2).
Kurt
Kurt
On Sat, Jun 8, 2019 at 4:26 PM Mark Matlock <mark at matlockfamily.com> wrote:
Kurt,
If you want two circuits like UNA-0 and IP-0-0 I think you have to be a
routing node (but not an area router).
Also, you should define all the nodes you want to talk to with NCP in one
of the startup files or do it with CFE but I prefer startup so it?s simple
to change.
Best,
Mark
Sent from my iPhone
On Jun 8, 2019, at 3:07 PM, Kurt Hamm <kurt at hamm.me> wrote:
This walkthrough was great.
I do have a question about this the section listed below:
My answers:
01.00 CURLY
02.00 31.132
03:00 Do I really want a routing node?
04:00 Do I really want a routing node?
.
.
07.00 Remote node name [<RET>=Done] Larry
08:00 Remote Node Address: 31.130
I thought the Remote Node address setting would just route decnet through
Larry. I don't really want the pdp-11 (CURLY) doing any routing.
Thanks!
Kurt
;
=====================================================================
; DEC - Section 1 - Define the target and remote nodes
; =====================================================================
;
* 01.00 What is the target node name [S R:0-6]: RSX11M
* 02.00 What is the target node address [S R:0.-8.]: 30.12
* 03.00 Target node ID [D=None] [S R:0.-32.]: PiDP-11/70 HECnet
* 04.00 Do you want to generate a routing node [D=N]? [Y/N]: Y
* 04.01 Do you want to generate a level 2 routing node [D=N]? [Y/N]: Y
* 05.00 Highest node number in this area [D R:12.-1023. D:12.]: 15.
* 05.01 Highest area number in network [D R:30.-63. D:30.]: 63.
;y
; Extended network support for network command terminals and products
; layered on DECnet, will be included.
; [S R:0-6]:
* 07.00 Remote node name [<RET>=Done]
On Sat, Jun 8, 2019 at 8:14 AM Mark Matlock <mark at matlockfamily.com>
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
>
>
12:42 a.m.
Ok, a quick rundown on some of the more esoteric details about lines and
circuits might be useful here.
First of all, Kurt, you might want to redo the NETGEN and not set the
system up for DECnet routing. It takes a lot of resources, and if you
don't really want it, you are much better off with a system not even
generated for it.
The question about remote nodes are just for an initial population of
your local nodename database. All you need there is really to define MIM
(1.13). You can then copy the whole nodename database from MIM over to
your machine that way instead. Let me know if you want some details on
that step.
On 2019-06-08 22:25, Mark Matlock wrote:
Kurt,
? ?If you want two circuits like UNA-0 and IP-0-0 I think you have to
be a routing node (but not an area router).
Not really, but maybe. If you define multiple circuits, and are an
end-node, only one circuit will be active. But others can exist, and the
system will fall back to some other circuit if the active one goes down.
So it can be used as a back connection.
However, even as an end-node, you can have several *lines* on and active
at the same time. And this is a trick to use if you want DECnet-over-IP,
but want to be an endnode. You need ethernet for TCP/IP to work, but you
do not want DECnet to use the ethernet circuit.
But you configure one IP line as well, and that is the one DECnet will
be using. Meanwhile, TCP/IP is using the ethernet line.
It might sound a little confusing, but think about it for a second, and
I hope it becomes clear. Otherwise, just ask, and I'll try to explain it
better.
Also, you should define all the nodes you want to talk
to with NCP in
one of the startup files or do it with CFE but I prefer startup so it?s
simple to change.
I would actually say that you wouldn't. Of course, there is nothing
wrong in doing this, but if you want the full HECnet nodename database,
it contains 700 nodes. That will take a while to type in.
However, you can copy the nodename database from another DECnet node,
and then use this.
But you need at least the nodename of someone where you will be copying
from to start with, which is why I suggested adding MIM at the start.
After that, there is [5,54]NNC which is the nodename collector task. Run
it, collect names from another node, and build a new database with this.
Then stop and restart the node name server, and you have all the nodes
defined.
(The node name server is managed by the command SCP.
So, SCP STOP followed by SCP START will do it.)
Johnny
--
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
12:45 a.m.
Yes, that last part is what I am missing on the PDP-11. I could use more
details about that.
Supratim showed me the following commands that worked on the MV3900. The
second command gave be an error on the PDP-11.
$ mc ncp set node mim address 1.13
$ mc ncp copy known nodes from mim to both
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se> wrote:
Ok, a quick rundown on some of the more esoteric
details about lines and
circuits might be useful here.
First of all, Kurt, you might want to redo the NETGEN and not set the
system up for DECnet routing. It takes a lot of resources, and if you
don't really want it, you are much better off with a system not even
generated for it.
The question about remote nodes are just for an initial population of
your local nodename database. All you need there is really to define MIM
(1.13). You can then copy the whole nodename database from MIM over to
your machine that way instead. Let me know if you want some details on
that step.
On 2019-06-08 22:25, Mark Matlock wrote:
Kurt,
If you want two circuits like UNA-0 and IP-0-0 I think you have to
be a routing node (but not an area router).
Not really, but maybe. If you define multiple circuits, and are an
end-node, only one circuit will be active. But others can exist, and the
system will fall back to some other circuit if the active one goes down.
So it can be used as a back connection.
However, even as an end-node, you can have several *lines* on and active
at the same time. And this is a trick to use if you want DECnet-over-IP,
but want to be an endnode. You need ethernet for TCP/IP to work, but you
do not want DECnet to use the ethernet circuit.
But you configure one IP line as well, and that is the one DECnet will
be using. Meanwhile, TCP/IP is using the ethernet line.
It might sound a little confusing, but think about it for a second, and
I hope it becomes clear. Otherwise, just ask, and I'll try to explain it
better.
Also, you should define all the nodes you want to
talk to with NCP in
one of the startup files or do it with CFE but I prefer startup so it?s
simple to change.
I would actually say that you wouldn't. Of course, there is nothing
wrong in doing this, but if you want the full HECnet nodename database,
it contains 700 nodes. That will take a while to type in.
However, you can copy the nodename database from another DECnet node,
and then use this.
But you need at least the nodename of someone where you will be copying
from to start with, which is why I suggested adding MIM at the start.
After that, there is [5,54]NNC which is the nodename collector task. Run
it, collect names from another node, and build a new database with this.
Then stop and restart the node name server, and you have all the nodes
defined.
(The node name server is managed by the command SCP.
So, SCP STOP followed by SCP START will do it.)
Johnny
--
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
12:48 a.m.
Sorry. I am bad with in-line comments. I have read the rest of your email
and will look at the collector.
Thanks!
Kurt
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se> wrote:
Ok, a quick rundown on some of the more esoteric
details about lines and
circuits might be useful here.
First of all, Kurt, you might want to redo the NETGEN and not set the
system up for DECnet routing. It takes a lot of resources, and if you
don't really want it, you are much better off with a system not even
generated for it.
The question about remote nodes are just for an initial population of
your local nodename database. All you need there is really to define MIM
(1.13). You can then copy the whole nodename database from MIM over to
your machine that way instead. Let me know if you want some details on
that step.
On 2019-06-08 22:25, Mark Matlock wrote:
Kurt,
If you want two circuits like UNA-0 and IP-0-0 I think you have to
be a routing node (but not an area router).
Not really, but maybe. If you define multiple circuits, and are an
end-node, only one circuit will be active. But others can exist, and the
system will fall back to some other circuit if the active one goes down.
So it can be used as a back connection.
However, even as an end-node, you can have several *lines* on and active
at the same time. And this is a trick to use if you want DECnet-over-IP,
but want to be an endnode. You need ethernet for TCP/IP to work, but you
do not want DECnet to use the ethernet circuit.
But you configure one IP line as well, and that is the one DECnet will
be using. Meanwhile, TCP/IP is using the ethernet line.
It might sound a little confusing, but think about it for a second, and
I hope it becomes clear. Otherwise, just ask, and I'll try to explain it
better.
Also, you should define all the nodes you want to
talk to with NCP in
one of the startup files or do it with CFE but I prefer startup so it?s
simple to change.
I would actually say that you wouldn't. Of course, there is nothing
wrong in doing this, but if you want the full HECnet nodename database,
it contains 700 nodes. That will take a while to type in.
However, you can copy the nodename database from another DECnet node,
and then use this.
But you need at least the nodename of someone where you will be copying
from to start with, which is why I suggested adding MIM at the start.
After that, there is [5,54]NNC which is the nodename collector task. Run
it, collect names from another node, and build a new database with this.
Then stop and restart the node name server, and you have all the nodes
defined.
(The node name server is managed by the command SCP.
So, SCP STOP followed by SCP START will do it.)
Johnny
--
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
1:21 a.m.
Hmmm, I don't see that task in the [5,54] directory.
This is what I have:
NTINIT.TSK;1 19. C 25-JAN-1999 15:47
NTL.TSK;1 231. C 25-JAN-1999 15:47
NCPFSL.TSK;1 265. C 25-JAN-1999 15:47
NMDRV.TSK;1 4. C 06-JUN-2019 18:24
NMDRV.STB;1 1. 06-JUN-2019 18:24
NMVACP.TSK;1 210. C 25-JAN-1999 15:47
NMVACP.STB;1 7. 25-JAN-1999 15:47
NDA.TSK;1 296. C 25-JAN-1999 15:48
NETACP.TSK;1 25. C 06-JUN-2019 18:25
NETACP.STB;1 9. 06-JUN-2019 18:25
NICE.TSK;1 16. C 25-JAN-1999 15:45
NTD.TSK;1 50. C 25-JAN-1999 15:45
NTDEMO.TSK;1 18. C 25-JAN-1999 15:45
NVPFSL.TSK;1 19. C 25-JAN-1999 15:45
NNCFSL.TSK;1 82. C 25-JAN-1999 15:46
NNDRV.TSK;1 3. C 25-JAN-1999 15:46
NNDRV.STB;1 1. C 25-JAN-1999 15:46
NNS.TSK;1 99. C 25-JAN-1999 15:46
NNS.DAT;11 19. 25-JAN-1999 15:46
NNS.TMP;151 10. 09-JUN-2019 00:03
NFTFSL.TSK;1 132. C 06-JUN-2019 18:26
NCT.TSK;1 8. C 06-JUN-2019 18:29
NCT.STB;1 3. 06-JUN-2019 18:29
NCT1.TSK;1 14. C 06-JUN-2019 18:29
NCT1.STB;1 3. 06-JUN-2019 18:29
NCTCTL.TSK;1 27. C 06-JUN-2019 18:29
NCT.DAT;10 4. 25-JAN-1999 15:45
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se> wrote:
Ok, a quick rundown on some of the more esoteric
details about lines and
circuits might be useful here.
First of all, Kurt, you might want to redo the NETGEN and not set the
system up for DECnet routing. It takes a lot of resources, and if you
don't really want it, you are much better off with a system not even
generated for it.
The question about remote nodes are just for an initial population of
your local nodename database. All you need there is really to define MIM
(1.13). You can then copy the whole nodename database from MIM over to
your machine that way instead. Let me know if you want some details on
that step.
On 2019-06-08 22:25, Mark Matlock wrote:
Kurt,
If you want two circuits like UNA-0 and IP-0-0 I think you have to
be a routing node (but not an area router).
Not really, but maybe. If you define multiple circuits, and are an
end-node, only one circuit will be active. But others can exist, and the
system will fall back to some other circuit if the active one goes down.
So it can be used as a back connection.
However, even as an end-node, you can have several *lines* on and active
at the same time. And this is a trick to use if you want DECnet-over-IP,
but want to be an endnode. You need ethernet for TCP/IP to work, but you
do not want DECnet to use the ethernet circuit.
But you configure one IP line as well, and that is the one DECnet will
be using. Meanwhile, TCP/IP is using the ethernet line.
It might sound a little confusing, but think about it for a second, and
I hope it becomes clear. Otherwise, just ask, and I'll try to explain it
better.
Also, you should define all the nodes you want to
talk to with NCP in
one of the startup files or do it with CFE but I prefer startup so it?s
simple to change.
I would actually say that you wouldn't. Of course, there is nothing
wrong in doing this, but if you want the full HECnet nodename database,
it contains 700 nodes. That will take a while to type in.
However, you can copy the nodename database from another DECnet node,
and then use this.
But you need at least the nodename of someone where you will be copying
from to start with, which is why I suggested adding MIM at the start.
After that, there is [5,54]NNC which is the nodename collector task. Run
it, collect names from another node, and build a new database with this.
Then stop and restart the node name server, and you have all the nodes
defined.
(The node name server is managed by the command SCP.
So, SCP STOP followed by SCP START will do it.)
Johnny
--
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
1:56 a.m.
I guess this also takes a few seconds of explanations. :-)
So, in RSX there are a lot of tasks that are sometimes built in a couple
of different variants, to be used depending on what hardware support
exist on the system.
Such tasks then exists with several "suffixes". For example, under
[3,54] you can see both PIP.TSK, PIPRES.TSK and PIPFSL.TSK.
So the "suffixes" are RES and FSL.
RES is the task built against a shared, resident library. Such tasks are
beneficial to use if you expect several copies to run at the same time,
since they share parts of their memory space, which only needs one copy
on physical memory then. However, it can have some drawback that the
virtual memory space available for the task is reduced, since memory
blocks have to be rounded to the page size of the PDP-11.
FSL is the task build against a shared, resident, supervisor mode
library. In additional to the benefits of the RES version, this variant
takes much less virtual address space, since the resident library is not
in the user virtual address space at all. However, not all hardware
supports supervisor mode.
And, as you can see, in your case, there is an NNCFSL.TSK, which is what
you want here.
Johnny
On 2019-06-09 01:21, Kurt Hamm wrote:
Hmmm, I don't see that task in the [5,54]
directory.
This is what I have:
NTINIT.TSK;1 ? ? ? ?19. ? ? C ?25-JAN-1999 15:47
NTL.TSK;1 ? ? ? ? ? 231. ? ?C ?25-JAN-1999 15:47
NCPFSL.TSK;1 ? ? ? ?265. ? ?C ?25-JAN-1999 15:47
NMDRV.TSK;1 ? ? ? ? 4. ? ? ?C ?06-JUN-2019 18:24
NMDRV.STB;1 ? ? ? ? 1. ? ? ? ? 06-JUN-2019 18:24
NMVACP.TSK;1 ? ? ? ?210. ? ?C ?25-JAN-1999 15:47
NMVACP.STB;1 ? ? ? ?7. ? ? ? ? 25-JAN-1999 15:47
NDA.TSK;1 ? ? ? ? ? 296. ? ?C ?25-JAN-1999 15:48
NETACP.TSK;1 ? ? ? ?25. ? ? C ?06-JUN-2019 18:25
NETACP.STB;1 ? ? ? ?9. ? ? ? ? 06-JUN-2019 18:25
NICE.TSK;1 ? ? ? ? ?16. ? ? C ?25-JAN-1999 15:45
NTD.TSK;1 ? ? ? ? ? 50. ? ? C ?25-JAN-1999 15:45
NTDEMO.TSK;1 ? ? ? ?18. ? ? C ?25-JAN-1999 15:45
NVPFSL.TSK;1 ? ? ? ?19. ? ? C ?25-JAN-1999 15:45
NNCFSL.TSK;1 ? ? ? ?82. ? ? C ?25-JAN-1999 15:46
NNDRV.TSK;1 ? ? ? ? 3. ? ? ?C ?25-JAN-1999 15:46
NNDRV.STB;1 ? ? ? ? 1. ? ? ?C ?25-JAN-1999 15:46
NNS.TSK;1 ? ? ? ? ? 99. ? ? C ?25-JAN-1999 15:46
NNS.DAT;11 ? ? ? ? ?19. ? ? ? ?25-JAN-1999 15:46
NNS.TMP;151 ? ? ? ? 10. ? ? ? ?09-JUN-2019 00:03
NFTFSL.TSK;1 ? ? ? ?132. ? ?C ?06-JUN-2019 18:26
NCT.TSK;1 ? ? ? ? ? 8. ? ? ?C ?06-JUN-2019 18:29
NCT.STB;1 ? ? ? ? ? 3. ? ? ? ? 06-JUN-2019 18:29
NCT1.TSK;1 ? ? ? ? ?14. ? ? C ?06-JUN-2019 18:29
NCT1.STB;1 ? ? ? ? ?3. ? ? ? ? 06-JUN-2019 18:29
NCTCTL.TSK;1 ? ? ? ?27. ? ? C ?06-JUN-2019 18:29
NCT.DAT;10 ? ? ? ? ?4. ? ? ? ? 25-JAN-1999 15:45
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
Ok, a quick rundown on some of the more esoteric details about lines
and
circuits might be useful here.
First of all, Kurt, you might want to redo the NETGEN and not set the
system up for DECnet routing. It takes a lot of resources, and if you
don't really want it, you are much better off with a system not even
generated for it.
The question about remote nodes are just for an initial population of
your local nodename database. All you need there is really to define
MIM
(1.13). You can then copy the whole nodename database from MIM over to
your machine that way instead. Let me know if you want some details on
that step.
On 2019-06-08 22:25, Mark Matlock wrote:
--
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
Kurt,
? ? ?If you want two circuits like UNA-0 and IP-0-0 I think you
have to
be a routing node (but not an area router).
Not really, but maybe. If you define multiple circuits, and are an
end-node, only one circuit will be active. But others can exist, and
the
system will fall back to some other circuit if the active one goes
down.
So it can be used as a back connection.
However, even as an end-node, you can have several *lines* on and
active
at the same time. And this is a trick to use if you want
DECnet-over-IP,
but want to be an endnode. You need ethernet for TCP/IP to work, but
you
do not want DECnet to use the ethernet circuit.
But you configure one IP line as well, and that is the one DECnet will
be using. Meanwhile, TCP/IP is using the ethernet line.
It might sound a little confusing, but think about it for a second, and
I hope it becomes clear. Otherwise, just ask, and I'll try to
explain it
better.
Also, you should define all the nodes you want to
talk to with
NCP in
one of the startup files or do it with CFE but I
prefer startup
so it?s
simple to change.
I would actually say that you wouldn't. Of course, there is nothing
wrong in doing this, but if you want the full HECnet nodename database,
it contains 700 nodes. That will take a while to type in.
However, you can copy the nodename database from another DECnet node,
and then use this.
But you need at least the nodename of someone where you will be copying
from to start with, which is why I suggested adding MIM at the start.
After that, there is [5,54]NNC which is the nodename collector task.
Run
it, collect names from another node, and build a new database with
this.
Then stop and restart the node name server, and you have all the nodes
defined.
(The node name server is managed by the command SCP.
So, SCP STOP followed by SCP START will do it.)
? ?Johnny
--
Johnny Billquist? ? ? ? ? ? ? ? ? || "I'm on a bus
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?||? on a psychedelic trip
email: bqt at softjar.se <mailto:bqt at softjar.se>? ? ? ? ? ? ?||
Reading murder books
pdp is alive!? ? ? ? ? ? ? ? ? ? ?||? tryin' to stay hip" - B. Idol
2:20 a.m.
That's it! Everything works great. I have the node list and can access
reachable nodes from the PDP-11.
This is just really wonderful.
As a thank you, I will leave the mailing list alone for a while. ha!
Kurt
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se> wrote:
Ok, a quick rundown on some of the more esoteric
details about lines and
circuits might be useful here.
First of all, Kurt, you might want to redo the NETGEN and not set the
system up for DECnet routing. It takes a lot of resources, and if you
don't really want it, you are much better off with a system not even
generated for it.
The question about remote nodes are just for an initial population of
your local nodename database. All you need there is really to define MIM
(1.13). You can then copy the whole nodename database from MIM over to
your machine that way instead. Let me know if you want some details on
that step.
On 2019-06-08 22:25, Mark Matlock wrote:
Kurt,
If you want two circuits like UNA-0 and IP-0-0 I think you have to
be a routing node (but not an area router).
Not really, but maybe. If you define multiple circuits, and are an
end-node, only one circuit will be active. But others can exist, and the
system will fall back to some other circuit if the active one goes down.
So it can be used as a back connection.
However, even as an end-node, you can have several *lines* on and active
at the same time. And this is a trick to use if you want DECnet-over-IP,
but want to be an endnode. You need ethernet for TCP/IP to work, but you
do not want DECnet to use the ethernet circuit.
But you configure one IP line as well, and that is the one DECnet will
be using. Meanwhile, TCP/IP is using the ethernet line.
It might sound a little confusing, but think about it for a second, and
I hope it becomes clear. Otherwise, just ask, and I'll try to explain it
better.
Also, you should define all the nodes you want to
talk to with NCP in
one of the startup files or do it with CFE but I prefer startup so it?s
simple to change.
I would actually say that you wouldn't. Of course, there is nothing
wrong in doing this, but if you want the full HECnet nodename database,
it contains 700 nodes. That will take a while to type in.
However, you can copy the nodename database from another DECnet node,
and then use this.
But you need at least the nodename of someone where you will be copying
from to start with, which is why I suggested adding MIM at the start.
After that, there is [5,54]NNC which is the nodename collector task. Run
it, collect names from another node, and build a new database with this.
Then stop and restart the node name server, and you have all the nodes
defined.
(The node name server is managed by the command SCP.
So, SCP STOP followed by SCP START will do it.)
Johnny
--
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
2:36 a.m.
Well, just taking a peek at CURLY, I can also tell that you have not
managed to get the multinet links up and running, but are communicating
with DECnet over ethernet. :-)
Johnny
On 2019-06-09 02:20, Kurt Hamm wrote:
That's it!? Everything works great.? I have the
node list and can access
reachable nodes from the PDP-11.
This is just really wonderful.
As a thank you, I will leave the mailing list alone for a while.? ha!
Kurt
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
Ok, a quick rundown on some of the more esoteric details about lines
and
circuits might be useful here.
First of all, Kurt, you might want to redo the NETGEN and not set the
system up for DECnet routing. It takes a lot of resources, and if you
don't really want it, you are much better off with a system not even
generated for it.
The question about remote nodes are just for an initial population of
your local nodename database. All you need there is really to define
MIM
(1.13). You can then copy the whole nodename database from MIM over to
your machine that way instead. Let me know if you want some details on
that step.
On 2019-06-08 22:25, Mark Matlock wrote:
--
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
Kurt,
? ? ?If you want two circuits like UNA-0 and IP-0-0 I think you
have to
be a routing node (but not an area router).
Not really, but maybe. If you define multiple circuits, and are an
end-node, only one circuit will be active. But others can exist, and
the
system will fall back to some other circuit if the active one goes
down.
So it can be used as a back connection.
However, even as an end-node, you can have several *lines* on and
active
at the same time. And this is a trick to use if you want
DECnet-over-IP,
but want to be an endnode. You need ethernet for TCP/IP to work, but
you
do not want DECnet to use the ethernet circuit.
But you configure one IP line as well, and that is the one DECnet will
be using. Meanwhile, TCP/IP is using the ethernet line.
It might sound a little confusing, but think about it for a second, and
I hope it becomes clear. Otherwise, just ask, and I'll try to
explain it
better.
Also, you should define all the nodes you want to
talk to with
NCP in
one of the startup files or do it with CFE but I
prefer startup
so it?s
simple to change.
I would actually say that you wouldn't. Of course, there is nothing
wrong in doing this, but if you want the full HECnet nodename database,
it contains 700 nodes. That will take a while to type in.
However, you can copy the nodename database from another DECnet node,
and then use this.
But you need at least the nodename of someone where you will be copying
from to start with, which is why I suggested adding MIM at the start.
After that, there is [5,54]NNC which is the nodename collector task.
Run
it, collect names from another node, and build a new database with
this.
Then stop and restart the node name server, and you have all the nodes
defined.
(The node name server is managed by the command SCP.
So, SCP STOP followed by SCP START will do it.)
? ?Johnny
--
Johnny Billquist? ? ? ? ? ? ? ? ? || "I'm on a bus
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?||? on a psychedelic trip
email: bqt at softjar.se <mailto:bqt at softjar.se>? ? ? ? ? ? ?||
Reading murder books
pdp is alive!? ? ? ? ? ? ? ? ? ? ?||? tryin' to stay hip" - B. Idol
2:36 a.m.
Ugh. Back to work.
I did see some errors....
Kurt
On Sat, Jun 8, 2019, 8:35 PM Johnny Billquist <bqt at softjar.se> wrote:
Well, just taking a peek at CURLY, I can also tell
that you have not
managed to get the multinet links up and running, but are communicating
with DECnet over ethernet. :-)
Johnny
On 2019-06-09 02:20, Kurt Hamm wrote:
That's it! Everything works great. I have
the node list and can access
reachable nodes from the PDP-11.
This is just really wonderful.
As a thank you, I will leave the mailing list alone for a while. ha!
Kurt
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
Ok, a quick rundown on some of the more esoteric details about lines
and
circuits might be useful here.
First of all, Kurt, you might want to redo the NETGEN and not set the
system up for DECnet routing. It takes a lot of resources, and if you
don't really want it, you are much better off with a system not even
generated for it.
The question about remote nodes are just for an initial population of
your local nodename database. All you need there is really to define
MIM
(1.13). You can then copy the whole nodename database from MIM over
to
your machine that way instead. Let me know if
you want some details
on
that step.
On 2019-06-08 22:25, Mark Matlock wrote:
will
Kurt,
If you want two circuits like UNA-0 and IP-0-0 I think you
have to
be a routing node (but not an area router).
Not really, but maybe. If you define multiple circuits, and are an
end-node, only one circuit will be active. But others can exist, and
the
system will fall back to some other circuit if the active one goes
down.
So it can be used as a back connection.
However, even as an end-node, you can have several *lines* on and
active
at the same time. And this is a trick to use if you want
DECnet-over-IP,
but want to be an endnode. You need ethernet for TCP/IP to work, but
you
do not want DECnet to use the ethernet circuit.
But you configure one IP line as well, and that is the one DECnet be using. Meanwhile, TCP/IP is using the
ethernet line.
It might sound a little confusing, but think about it for a second,
and
I hope it becomes clear. Otherwise, just ask,
and I'll try to
explain it
better.
database,
Also, you should define all the nodes you want to
talk to with
NCP in
one of the startup files or do it with CFE but I
prefer startup
so it?s
simple to change.
I would actually say that you wouldn't. Of course, there is nothing
wrong in doing this, but if you want the full HECnet nodename it contains 700 nodes. That will take a while
to type in.
However, you can copy the nodename database from another DECnet node,
and then use this.
But you need at least the nodename of someone where you will be
copying
from to start with, which is why I suggested
adding MIM at the start.
After that, there is [5,54]NNC which is the nodename collector task.
Run
it, collect names from another node, and build a new database with
this.
Then stop and restart the node name server, and you have all the
nodes
defined.
(The node name server is managed by the command SCP.
So, SCP STOP followed by SCP START will do it.)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se <mailto: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
2:45 a.m.
Maybe not much comfort, but MOE isn't using the multinet link to LARRY
either, but is also talking over ethernet.
Johnny
On 2019-06-09 02:36, Kurt Hamm wrote:
Ugh.? Back to work.
I did see some errors....
Kurt
On Sat, Jun 8, 2019, 8:35 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
Well, just taking a peek at CURLY, I can also tell that you have not
managed to get the multinet links up and running, but are communicating
with DECnet over ethernet. :-)
? ?Johnny
On 2019-06-09 02:20, Kurt Hamm wrote:
--
Johnny Billquist? ? ? ? ? ? ? ? ? || "I'm on a bus
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?||? on a psychedelic trip
email: bqt at softjar.se <mailto: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
That's it!? Everything works great.? I have
the node list and can
access
reachable nodes from the PDP-11.
This is just really wonderful.
As a thank you, I will leave the mailing list alone for a while.? ha!
Kurt
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto:bqt at
softjar.se>>> wrote:
? ? ?Ok, a quick rundown on some of the more esoteric details
about lines
? ? ?and
? ? ?circuits might be useful here.
? ? ?First of all, Kurt, you might want to redo the NETGEN and not
set the
? ? ?system up for DECnet routing. It takes a lot
of resources,
and if you
? ? ?don't really want it, you are much better
off with a system
not even
? ? ?generated for it.
? ? ?The question about remote nodes are just for an initial
population of
? ? ?your local nodename database. All you need
there is really to
define
? ? ?MIM
? ? ?(1.13). You can then copy the whole nodename database from
MIM over to
? ? ?your machine that way instead. Let me know if
you want some
details on
? ? ?that step.
? ? ?On 2019-06-08 22:25, Mark Matlock wrote:
? ? ? > Kurt,
? ? ? >? ? ?If you want two circuits like UNA-0 and IP-0-0 I think you
? ? ?have to
? ? ? > be a routing node (but not an area router).
? ? ?Not really, but maybe. If you define multiple circuits, and
are an
? ? ?end-node, only one circuit will be active.
But others can
exist, and
? ? ?the
? ? ?system will fall back to some other circuit if the active one
goes
? ? ?down.
? ? ?So it can be used as a back connection.
? ? ?However, even as an end-node, you can have several *lines* on and
? ? ?active
? ? ?at the same time. And this is a trick to use if you want
? ? ?DECnet-over-IP,
? ? ?but want to be an endnode. You need ethernet for TCP/IP to
work, but
? ? ?you
? ? ?do not want DECnet to use the ethernet circuit.
? ? ?But you configure one IP line as well, and that is the one
DECnet will
? ? ?be using. Meanwhile, TCP/IP is using the
ethernet line.
? ? ?It might sound a little confusing, but think about it for a
second, and
? ? ?I hope it becomes clear. Otherwise, just ask,
and I'll try to
? ? ?explain it
? ? ?better.
? ? ? > Also, you should define all the nodes you want to talk to with
? ? ?NCP in
? ? ? > one of the startup files or do it with CFE but I prefer
startup
? ? ?so it?s
? ? ? > simple to change.
? ? ?I would actually say that you wouldn't. Of course, there is
nothing
? ? ?wrong in doing this, but if you want the full
HECnet nodename
database,
? ? ?it contains 700 nodes. That will take a while
to type in.
? ? ?However, you can copy the nodename database from another
DECnet node,
? ? ?and then use this.
? ? ?But you need at least the nodename of someone where you will
be copying
? ? ?from to start with, which is why I suggested
adding MIM at
the start.
? ? ?After that, there is [5,54]NNC which is the nodename
collector task.
? ? ?Run
? ? ?it, collect names from another node, and build a new database
with
? ? ?this.
? ? ?Then stop and restart the node name server, and you have all
the nodes
? ? ?defined.
? ? ?(The node name server is managed by the command SCP.
? ? ?So, SCP STOP followed by SCP START will do it.)
? ? ? ? ?Johnny
? ? ?--
? ? ?Johnny Billquist? ? ? ? ? ? ? ? ? || "I'm on a bus
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?||? on a psychedelic trip
? ? ?email: bqt at softjar.se <mailto:bqt at softjar.se>
<mailto:bqt
at softjar.se <mailto:bqt at softjar.se>>? ? ? ? ? ? ?||
? ? ?Reading murder books
? ? ?pdp is alive!? ? ? ? ? ? ? ? ? ? ?||? tryin' to stay hip" -
B.
Idol
2:47 a.m.
Oh, and by the way... Do you have two physical, separate ethernets?
Because otherwise you might be in even more trouble, as you have two
ethernet interfaces defined on MOE, and they both see LARRY. If you
actually have two ethernet networks between the two machines, then
everything is fine. Otherwise you are actually very messed up.
Johnny
On 2019-06-09 02:45, Johnny Billquist wrote:
Maybe not much comfort, but MOE isn't using the
multinet link to LARRY
either, but is also talking over ethernet.
? Johnny
On 2019-06-09 02:36, Kurt Hamm wrote:
--
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
Ugh.? Back to work.
I did see some errors....
Kurt
On Sat, Jun 8, 2019, 8:35 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
??? Well, just taking a peek at CURLY, I can also tell that you have not
??? managed to get the multinet links up and running, but are
communicating
??? with DECnet over ethernet. :-)
???? ? ?Johnny
??? On 2019-06-09 02:20, Kurt Hamm wrote:
???? > That's it!? Everything works great.? I have the node list and can
??? access
???? > reachable nodes from the PDP-11.
???? >
???? > This is just really wonderful.
???? >
???? > As a thank you, I will leave the mailing list alone for a
while.? ha!
???? >
???? > Kurt
???? >
???? > On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se
??? <mailto:bqt at softjar.se>
???? > <mailto:bqt at softjar.se <mailto:bqt at softjar.se>>> wrote:
???? >
???? >? ? ?Ok, a quick rundown on some of the more esoteric details
??? about lines
???? >? ? ?and
???? >? ? ?circuits might be useful here.
???? >
???? >? ? ?First of all, Kurt, you might want to redo the NETGEN and not
??? set the
???? >? ? ?system up for DECnet routing. It takes a lot of resources,
??? and if you
???? >? ? ?don't really want it, you are much better off with a system
??? not even
???? >? ? ?generated for it.
???? >
???? >? ? ?The question about remote nodes are just for an initial
??? population of
???? >? ? ?your local nodename database. All you need there is really to
??? define
???? >? ? ?MIM
???? >? ? ?(1.13). You can then copy the whole nodename database from
??? MIM over to
???? >? ? ?your machine that way instead. Let me know if you want some
??? details on
???? >? ? ?that step.
???? >
???? >
???? >? ? ?On 2019-06-08 22:25, Mark Matlock wrote:
???? >? ? ? > Kurt,
???? >? ? ? >? ? ?If you want two circuits like UNA-0 and IP-0-0 I
think you
???? >? ? ?have to
???? >? ? ? > be a routing node (but not an area router).
???? >
???? >? ? ?Not really, but maybe. If you define multiple circuits, and
??? are an
???? >? ? ?end-node, only one circuit will be active. But others can
??? exist, and
???? >? ? ?the
???? >? ? ?system will fall back to some other circuit if the active one
??? goes
???? >? ? ?down.
???? >? ? ?So it can be used as a back connection.
???? >
???? >? ? ?However, even as an end-node, you can have several *lines*
on and
???? >? ? ?active
???? >? ? ?at the same time. And this is a trick to use if you want
???? >? ? ?DECnet-over-IP,
???? >? ? ?but want to be an endnode. You need ethernet for TCP/IP to
??? work, but
???? >? ? ?you
???? >? ? ?do not want DECnet to use the ethernet circuit.
???? >
???? >? ? ?But you configure one IP line as well, and that is the one
??? DECnet will
???? >? ? ?be using. Meanwhile, TCP/IP is using the ethernet line.
???? >
???? >? ? ?It might sound a little confusing, but think about it for a
??? second, and
???? >? ? ?I hope it becomes clear. Otherwise, just ask, and I'll try to
???? >? ? ?explain it
???? >? ? ?better.
???? >
???? >? ? ? > Also, you should define all the nodes you want to talk
to with
???? >? ? ?NCP in
???? >? ? ? > one of the startup files or do it with CFE but I prefer
??? startup
???? >? ? ?so it?s
???? >? ? ? > simple to change.
???? >
???? >? ? ?I would actually say that you wouldn't. Of course, there is
??? nothing
???? >? ? ?wrong in doing this, but if you want the full HECnet nodename
??? database,
???? >? ? ?it contains 700 nodes. That will take a while to type in.
???? >
???? >? ? ?However, you can copy the nodename database from another
??? DECnet node,
???? >? ? ?and then use this.
???? >
???? >? ? ?But you need at least the nodename of someone where you will
??? be copying
???? >? ? ?from to start with, which is why I suggested adding MIM at
??? the start.
???? >
???? >? ? ?After that, there is [5,54]NNC which is the nodename
??? collector task.
???? >? ? ?Run
???? >? ? ?it, collect names from another node, and build a new database
??? with
???? >? ? ?this.
???? >? ? ?Then stop and restart the node name server, and you have all
??? the nodes
???? >? ? ?defined.
???? >
???? >? ? ?(The node name server is managed by the command SCP.
???? >? ? ?So, SCP STOP followed by SCP START will do it.)
???? >
???? >? ? ? ? ?Johnny
???? >
???? >? ? ?--
???? >? ? ?Johnny Billquist? ? ? ? ? ? ? ? ? || "I'm on a bus
???? >? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?||? on a psychedelic trip
???? >? ? ?email: bqt at softjar.se <mailto:bqt at softjar.se>
??? <mailto:bqt at softjar.se <mailto: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 <mailto:bqt at softjar.se>? ? ? ? ? ? ?||
Reading murder books
??? pdp is alive!? ? ? ? ? ? ? ? ? ? ?||? tryin' to stay hip" - B. Idol
3:08 a.m.
OK. I did have two ethernet adapters configured for each server. I
disabled the second one. But, worse, in the simh ini file, both servers
had the same MAC addresses associated with their ethernet adapters. I am
not sure how this ever worked.
I am still checking things and will start working on that PDP-11 default
thing shortly.
Kurt
On Sat, Jun 8, 2019 at 8:47 PM Johnny Billquist <bqt at softjar.se> wrote:
Oh, and by the way... Do you have two physical,
separate ethernets?
Because otherwise you might be in even more trouble, as you have two
ethernet interfaces defined on MOE, and they both see LARRY. If you
actually have two ethernet networks between the two machines, then
everything is fine. Otherwise you are actually very messed up.
Johnny
On 2019-06-09 02:45, Johnny Billquist wrote:
Maybe not much comfort, but MOE isn't using
the multinet link to LARRY
either, but is also talking over ethernet.
Johnny
On 2019-06-09 02:36, Kurt Hamm wrote:
--
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
Ugh. Back to work.
I did see some errors....
Kurt
On Sat, Jun 8, 2019, 8:35 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
Well, just taking a peek at CURLY, I can also tell that you have not
managed to get the multinet links up and running, but are
communicating
with DECnet over ethernet. :-)
Johnny
On 2019-06-09 02:20, Kurt Hamm wrote:
-- Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se <mailto:bqt at softjar.se> ||
Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
That's it! Everything works great. I have
the node list and can
access
reachable nodes from the PDP-11.
This is just really wonderful.
As a thank you, I will leave the mailing list alone for a
while. ha!
Kurt
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto:bqt at
softjar.se>>> wrote:
Ok, a quick rundown on some of the more esoteric details
about lines
and
circuits might be useful here.
First of all, Kurt, you might want to redo the NETGEN and not
set the
system up for DECnet routing. It takes a lot
of resources,
and if you
don't really want it, you are much better
off with a system
not even
generated for it.
The question about remote nodes are just for an initial
population of
your local nodename database. All you need
there is really to
define
MIM
(1.13). You can then copy the whole nodename database from
MIM over to
your machine that way instead. Let me know if
you want some
details on
that step.
On 2019-06-08 22:25, Mark Matlock wrote:
> Kurt,
> If you want two circuits like UNA-0 and IP-0-0 I
think you
have to
> be a routing node (but not an area router).
Not really, but maybe. If you define multiple circuits, and
are an
end-node, only one circuit will be active.
But others can
exist, and
the
system will fall back to some other circuit if the active one
goes
down.
So it can be used as a back connection.
However, even as an end-node, you can have several *lines*
on and
active
at the same time. And this is a trick to use if you want
DECnet-over-IP,
but want to be an endnode. You need ethernet for TCP/IP to
work, but
you
do not want DECnet to use the ethernet circuit.
But you configure one IP line as well, and that is the one
DECnet will
be using. Meanwhile, TCP/IP is using the
ethernet line.
It might sound a little confusing, but think about it for a
second, and
I hope it becomes clear. Otherwise, just ask,
and I'll try to
explain it
better.
> Also, you should define all the nodes you want to talk
to with
NCP in
> one of the startup files or do it with CFE but I prefer
startup
so it?s
> simple to change.
I would actually say that you wouldn't. Of course, there is
nothing
wrong in doing this, but if you want the full
HECnet nodename
database,
it contains 700 nodes. That will take a while
to type in.
However, you can copy the nodename database from another
DECnet node,
and then use this.
But you need at least the nodename of someone where you will
be copying
from to start with, which is why I suggested
adding MIM at
the start.
After that, there is [5,54]NNC which is the nodename
collector task.
Run
it, collect names from another node, and build a new database
with
this.
Then stop and restart the node name server, and you have all
the nodes
defined.
(The node name server is managed by the command SCP.
So, SCP STOP followed by SCP START will do it.)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se <mailto:bqt at softjar.se>
<mailto:bqt
at softjar.se <mailto:bqt at softjar.se>> ||
Reading murder books
pdp is alive! || tryin' to stay hip" -
B.
Idol
3:13 a.m.
Since DECnet decides what MAC address you are supposed to have, they
*have* to have the same MAC address in simh, which is why I was pointing
out that if you actually had them on the same ethernet segment, you are
messed up. :-)
They have to have the same address because it is derived from the DECnet
address, and your machine only ever have one DECnet address. DECnet do
not have an address per interface, like IP do.
Johnny
On 2019-06-09 03:08, Kurt Hamm wrote:
OK.? I did have two ethernet adapters configured for
each server.? I
disabled the second one.? But, worse, in the simh ini file, both servers
had the same MAC addresses associated with their ethernet adapters.? I
am not sure how this ever worked.
I am still checking things and will start working on that PDP-11
default? thing shortly.
Kurt
On Sat, Jun 8, 2019 at 8:47 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
Oh, and by the way... Do you have two physical, separate ethernets?
Because otherwise you might be in even more trouble, as you have two
ethernet interfaces defined on MOE, and they both see LARRY. If you
actually have two ethernet networks between the two machines, then
everything is fine. Otherwise you are actually very messed up.
? ?Johnny
On 2019-06-09 02:45, Johnny Billquist wrote:
--
Johnny Billquist? ? ? ? ? ? ? ? ? || "I'm on a bus
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?||? on a psychedelic trip
email: bqt at softjar.se <mailto: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
Maybe not much comfort, but MOE isn't using
the multinet link to
LARRY
either, but is also talking over ethernet.
? ? Johnny
On 2019-06-09 02:36, Kurt Hamm wrote:
> Ugh.? Back to work.
>
> I did see some errors....
>
> Kurt
>
> On Sat, Jun 8, 2019, 8:35 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>
> <mailto:bqt at softjar.se <mailto:bqt
at softjar.se>>> wrote:
>
> ??? Well, just taking a peek at CURLY, I can also tell that you
have not
> ??? managed to get the multinet links up and
running, but are
> communicating
> ??? with DECnet over ethernet. :-)
>
> ???? ? ?Johnny
>
> ??? On 2019-06-09 02:20, Kurt Hamm wrote:
> ???? > That's it!? Everything works great.? I have the node list
and can
> ??? access
> ???? > reachable nodes from the PDP-11.
> ???? >
> ???? > This is just really wonderful.
> ???? >
> ???? > As a thank you, I will leave the mailing list alone for a
> while.? ha!
> ???? >
> ???? > Kurt
> ???? >
> ???? > On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist
<bqt at
softjar.se <mailto:bqt at softjar.se>
> ??? <mailto:bqt at softjar.se
<mailto:bqt at softjar.se>>
> ???? > <mailto:bqt at softjar.se <mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto:bqt at softjar.se>>>> wrote:
> ???? >
> ???? >? ? ?Ok, a quick rundown on some of the more esoteric details
> ??? about lines
> ???? >? ? ?and
> ???? >? ? ?circuits might be useful here.
> ???? >
> ???? >? ? ?First of all, Kurt, you might want to redo the NETGEN
and
not
> ??? set the
> ???? >? ? ?system up for DECnet routing. It takes a lot of
resources,
> ??? and if you
> ???? >? ? ?don't really want it, you are much better off with a
system
> ??? not even
> ???? >? ? ?generated for it.
> ???? >
> ???? >? ? ?The question about remote nodes are just for an initial
> ??? population of
> ???? >? ? ?your local nodename database. All you need there is
really
to
> ??? define
> ???? >? ? ?MIM
> ???? >? ? ?(1.13). You can then copy the whole nodename database
from
> ??? MIM over to
> ???? >? ? ?your machine that way instead. Let me know if you
want some
> ??? details on
> ???? >? ? ?that step.
> ???? >
> ???? >
> ???? >? ? ?On 2019-06-08 22:25, Mark Matlock wrote:
> ???? >? ? ? > Kurt,
> ???? >? ? ? >? ? ?If you want two circuits like UNA-0 and IP-0-0 I
> think you
> ???? >? ? ?have to
> ???? >? ? ? > be a routing node (but not an area router).
> ???? >
> ???? >? ? ?Not really, but maybe. If you define multiple
circuits, and
> ??? are an
> ???? >? ? ?end-node, only one circuit will be active. But others can
> ??? exist, and
> ???? >? ? ?the
> ???? >? ? ?system will fall back to some other circuit if the
active
one
> ??? goes
> ???? >? ? ?down.
> ???? >? ? ?So it can be used as a back connection.
> ???? >
> ???? >? ? ?However, even as an end-node, you can have several
*lines*
> on and
> ???? >? ? ?active
> ???? >? ? ?at the same time. And this is a trick to use if you want
> ???? >? ? ?DECnet-over-IP,
> ???? >? ? ?but want to be an endnode. You need ethernet for
TCP/IP to
> ??? work, but
> ???? >? ? ?you
> ???? >? ? ?do not want DECnet to use the ethernet circuit.
> ???? >
> ???? >? ? ?But you configure one IP line as well, and that is
the one
> ??? DECnet will
> ???? >? ? ?be using. Meanwhile, TCP/IP is using the ethernet line.
> ???? >
> ???? >? ? ?It might sound a little confusing, but think about it
for a
> ??? second, and
> ???? >? ? ?I hope it becomes clear. Otherwise, just ask, and
I'll
try to
> ???? >? ? ?explain it
> ???? >? ? ?better.
> ???? >
> ???? >? ? ? > Also, you should define all the nodes you want to
talk
> to with
> ???? >? ? ?NCP in
> ???? >? ? ? > one of the startup files or do it with CFE but I
prefer
> ??? startup
> ???? >? ? ?so it?s
> ???? >? ? ? > simple to change.
> ???? >
> ???? >? ? ?I would actually say that you wouldn't. Of course,
there
is
> ??? nothing
> ???? >? ? ?wrong in doing this, but if you want the full HECnet
nodename
> ??? database,
> ???? >? ? ?it contains 700 nodes. That will take a while to type in.
> ???? >
> ???? >? ? ?However, you can copy the nodename database from another
> ??? DECnet node,
> ???? >? ? ?and then use this.
> ???? >
> ???? >? ? ?But you need at least the nodename of someone where
you
will
> ??? be copying
> ???? >? ? ?from to start with, which is why I suggested adding
MIM at
> ??? the start.
> ???? >
> ???? >? ? ?After that, there is [5,54]NNC which is the nodename
> ??? collector task.
> ???? >? ? ?Run
> ???? >? ? ?it, collect names from another node, and build a new
database
> ??? with
> ???? >? ? ?this.
> ???? >? ? ?Then stop and restart the node name server, and you
have
all
> ??? the nodes
> ???? >? ? ?defined.
> ???? >
> ???? >? ? ?(The node name server is managed by the command SCP.
> ???? >? ? ?So, SCP STOP followed by SCP START will do it.)
> ???? >
> ???? >? ? ? ? ?Johnny
> ???? >
> ???? >? ? ?--
> ???? >? ? ?Johnny Billquist? ? ? ? ? ? ? ? ? || "I'm on a bus
> ???? >? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?||? on a
psychedelic
trip
> ???? >? ? ?email: bqt at softjar.se
<mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto:bqt at
softjar.se>>
> ??? <mailto:bqt at softjar.se
<mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto: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 <mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto:bqt at softjar.se>>? ? ? ? ? ? ?||
> Reading murder books
> ??? pdp is alive!? ? ? ? ? ? ? ? ? ? ?||? tryin' to stay hip" -
B. Idol
3:37 a.m.
Yes, IP on both PDP-11 and Moe show IP-starting. I am looking at the MAC
addresses
NCP>SHOW KNOWN CIRCUITS
Known circuits summary as of 8-JUN-2019 21:34:59
Circuit = UNA-0
State = Off
Circuit = IP-0-0
State = On-starting
Circuit = IP-0-1
State = Off
On Sat, Jun 8, 2019 at 9:12 PM Johnny Billquist <bqt at softjar.se> wrote:
Since DECnet decides what MAC address you are supposed
to have, they
*have* to have the same MAC address in simh, which is why I was pointing
out that if you actually had them on the same ethernet segment, you are
messed up. :-)
They have to have the same address because it is derived from the DECnet
address, and your machine only ever have one DECnet address. DECnet do
not have an address per interface, like IP do.
Johnny
On 2019-06-09 03:08, Kurt Hamm wrote:
initial
I
can
want
line.
in.
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se <mailto: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
OK. I did have two ethernet adapters configured
for each server. I
disabled the second one. But, worse, in the simh ini file, both servers
had the same MAC addresses associated with their ethernet adapters. I
am not sure how this ever worked.
I am still checking things and will start working on that PDP-11
default thing shortly.
Kurt
On Sat, Jun 8, 2019 at 8:47 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
Oh, and by the way... Do you have two physical, separate ethernets?
Because otherwise you might be in even more trouble, as you have two
ethernet interfaces defined on MOE, and they both see LARRY. If you
actually have two ethernet networks between the two machines, then
everything is fine. Otherwise you are actually very messed up.
Johnny
On 2019-06-09 02:45, Johnny Billquist wrote:
details
Maybe not much comfort, but MOE isn't using
the multinet link to
LARRY
either, but is also talking over ethernet.
Johnny
On 2019-06-09 02:36, Kurt Hamm wrote:
> Ugh. Back to work.
>
> I did see some errors....
>
> Kurt
>
> On Sat, Jun 8, 2019, 8:35 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>
> <mailto:bqt at softjar.se <mailto:bqt
at softjar.se>>> wrote:
>
> Well, just taking a peek at CURLY, I can also tell that you
have not
> managed to get the multinet links up and
running, but are
> communicating
> with DECnet over ethernet. :-)
>
> Johnny
>
> On 2019-06-09 02:20, Kurt Hamm wrote:
> > That's it! Everything works great. I have the node list
and can
> access
> > reachable nodes from the PDP-11.
> >
> > This is just really wonderful.
> >
> > As a thank you, I will leave the mailing list alone for a
> while. ha!
> >
> > Kurt
> >
> > On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist
<bqt at
softjar.se <mailto:bqt at softjar.se>
> <mailto:bqt at softjar.se
<mailto:bqt at softjar.se>>
> > <mailto:bqt at softjar.se <mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto:bqt at softjar.se>>>> wrote:
>> >
>> > Ok, a quick rundown on some of the more esoteric >
about lines
> > and
> > circuits might be useful here.
> >
> > First of all, Kurt, you might want to redo the NETGEN
and
not
> set the
> > system up for DECnet routing. It takes a lot of
resources,
> and if you
> > don't really want it, you are much better off with a
system
>> not even
>> > generated for it.
>> >
>> > The question about remote nodes are just for an >
population of
> > your local nodename database. All you need there is
really
to
> define
> > MIM
> > (1.13). You can then copy the whole nodename database
from
> MIM over to
> > your machine that way instead. Let me know if you
want some
>> details on
>> > that step.
>> >
>> >
>> > On 2019-06-08 22:25, Mark Matlock wrote:
>> > > Kurt,
>> > > If you want two circuits like UNA-0 and IP-0-0
> think
you
> > have to
> > > be a routing node (but not an area router).
> >
> > Not really, but maybe. If you define multiple
circuits, and
>> are an
>> > end-node, only one circuit will be active. But others >
exist, and
> > the
> > system will fall back to some other circuit if the
active
one
> goes
> > down.
> > So it can be used as a back connection.
> >
> > However, even as an end-node, you can have several
*lines*
>> on and
>> > active
>> > at the same time. And this is a trick to use if you >
> DECnet-over-IP,
> > but want to be an endnode. You need ethernet for
TCP/IP to
> work, but
> > you
> > do not want DECnet to use the ethernet circuit.
> >
> > But you configure one IP line as well, and that is
the one
>> DECnet will
>> > be using. Meanwhile, TCP/IP is using the ethernet >
>
> > It might sound a little confusing, but think about it
for a
> second, and
> > I hope it becomes clear. Otherwise, just ask, and
I'll
try to
> > explain it
> > better.
> >
> > > Also, you should define all the nodes you want to
talk
> to with
> > NCP in
> > > one of the startup files or do it with CFE but I
prefer
> startup
> > so it?s
> > > simple to change.
> >
> > I would actually say that you wouldn't. Of course,
there
is
> nothing
> > wrong in doing this, but if you want the full HECnet
nodename
>> database,
>> > it contains 700 nodes. That will take a while to type >> >
>> > However, you can copy the nodename database from
another
>
DECnet node,
> > and then use this.
> >
> > But you need at least the nodename of someone where
you
will
> be copying
> > from to start with, which is why I suggested adding
MIM at
> the start.
> >
> > After that, there is [5,54]NNC which is the nodename
> collector task.
> > Run
> > it, collect names from another node, and build a new
database
> with
> > this.
> > Then stop and restart the node name server, and you
have
all
> the nodes
> > defined.
> >
> > (The node name server is managed by the command SCP.
> > So, SCP STOP followed by SCP START will do it.)
> >
> > Johnny
> >
> > --
> > Johnny Billquist || "I'm on a bus
> > || on a
psychedelic
trip
> > email: bqt at softjar.se
<mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto:bqt at
softjar.se>>
> <mailto:bqt at softjar.se
<mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto: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 <mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto:bqt at softjar.se>> ||
> Reading murder books
> pdp is alive! || tryin' to stay hip" -
B. Idol
2:47 a.m.
The last command in INS.CMD is failing:
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 LIN IP-0-* ALL
MNC SHO VER
Initialize common
MLTCFG version X0.5
MNC SET CIR IP-0-0 TCA HOST 192.168.1.49:7705 PORT 0
NCP SET CIR IP-0-0 STA ON
NCP -- Set failed, component in wrong state, Circuit
INS.CMD (Content)
---------------------------------------------------------------
DU0:[1,2]INS.CMD;255 08-JUN-19;9 10:55:28
.IFNINS MLTCOM INS LB:[IPNET]MLTCOM/UIC=[1,54]/PRO=[RW,RW,,]
.IFNINS MLTNET INS LB:[IPNET]MLTNET
.IFNINS ...MNC INS LB:[IPNET]MLTCFG
NCP SET PROC IP TOP
NCP SET LIN IP-0-* ALL
MNC SHO VER
.;
.; Repeat the following two lines for each connection wanted.
.; For TCP connections, use TCP or TCA, depending on passive or
.; active. Also, you should set a local port for passive TCP.
.; (PORT n)
.;
.; For the remote host, you can give host:port, if you
.; want. For active TCP connections, you can use local port 0,
.; to get a random source port.
.; For passive TCP connetions, you can set host and/or remote
.; port to 0, to accept conncetions from any.
.;
.; At Johnny's end: IP-0-10
.; Mark Matlock (area 30) - 147 ms
.; mnc set cir ip-0-10 tcp host 0.0.0.0:0 port
.; ncp set cir ip-0-10 sta
.;
.;mnc set cir ip-0-0 udp host <host> port <n>
.;ncp set cir ip-0-0 sta on
.;
MNC SET CIR IP-0-0 TCA HOST 192.168.1.49:7705 PORT 0
NCP SET CIR IP-0-0 STA ON
On Sat, Jun 8, 2019 at 8:35 PM Johnny Billquist <bqt at softjar.se> wrote:
Well, just taking a peek at CURLY, I can also tell
that you have not
managed to get the multinet links up and running, but are communicating
with DECnet over ethernet. :-)
Johnny
On 2019-06-09 02:20, Kurt Hamm wrote:
That's it! Everything works great. I have
the node list and can access
reachable nodes from the PDP-11.
This is just really wonderful.
As a thank you, I will leave the mailing list alone for a while. ha!
Kurt
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
Ok, a quick rundown on some of the more esoteric details about lines
and
circuits might be useful here.
First of all, Kurt, you might want to redo the NETGEN and not set the
system up for DECnet routing. It takes a lot of resources, and if you
don't really want it, you are much better off with a system not even
generated for it.
The question about remote nodes are just for an initial population of
your local nodename database. All you need there is really to define
MIM
(1.13). You can then copy the whole nodename database from MIM over
to
your machine that way instead. Let me know if
you want some details
on
that step.
On 2019-06-08 22:25, Mark Matlock wrote:
will
Kurt,
If you want two circuits like UNA-0 and IP-0-0 I think you
have to
be a routing node (but not an area router).
Not really, but maybe. If you define multiple circuits, and are an
end-node, only one circuit will be active. But others can exist, and
the
system will fall back to some other circuit if the active one goes
down.
So it can be used as a back connection.
However, even as an end-node, you can have several *lines* on and
active
at the same time. And this is a trick to use if you want
DECnet-over-IP,
but want to be an endnode. You need ethernet for TCP/IP to work, but
you
do not want DECnet to use the ethernet circuit.
But you configure one IP line as well, and that is the one DECnet be using. Meanwhile, TCP/IP is using the
ethernet line.
It might sound a little confusing, but think about it for a second,
and
I hope it becomes clear. Otherwise, just ask,
and I'll try to
explain it
better.
database,
Also, you should define all the nodes you want to
talk to with
NCP in
one of the startup files or do it with CFE but I
prefer startup
so it?s
simple to change.
I would actually say that you wouldn't. Of course, there is nothing
wrong in doing this, but if you want the full HECnet nodename it contains 700 nodes. That will take a while
to type in.
However, you can copy the nodename database from another DECnet node,
and then use this.
But you need at least the nodename of someone where you will be
copying
from to start with, which is why I suggested
adding MIM at the start.
After that, there is [5,54]NNC which is the nodename collector task.
Run
it, collect names from another node, and build a new database with
this.
Then stop and restart the node name server, and you have all the
nodes
defined.
(The node name server is managed by the command SCP.
So, SCP STOP followed by SCP START will do it.)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se <mailto: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
2:56 a.m.
Most likely because CURLY is an endnode, and you already have an
ethernet circuit up and running. As I said before, you can only have one
circuit active at a time.
I sortof have a recollection that you can have multiple circuits
enabled, but I might be misremembering some details.
Anyway, I suspect that you really need to turn the ethernet circuit off
here before NCP allows you to turn the IP-0-0 circuit on.
Johnny
On 2019-06-09 02:47, Kurt Hamm wrote:
The last command in INS.CMD is failing:
--
Johnny Billquist? ? ? ? ? ? ? ? ? || "I'm on a bus
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?||? on a psychedelic trip
email: bqt at softjar.se <mailto: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
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 LIN IP-0-* ALL
MNC SHO VER
Initialize common
MLTCFG version X0.5
MNC SET CIR IP-0-0 TCA HOST 192.168.1.49:7705
<http://192.168.1.49:7705> PORT 0
NCP SET CIR IP-0-0 STA ON
NCP -- Set
failed, component in wrong state, Circuit
INS.CMD (Content)
---------------------------------------------------------------
DU0:[1,2]INS.CMD;255 ? 08-JUN-19;9 10:55:28
.IFNINS MLTCOM INS LB:[IPNET]MLTCOM/UIC=[1,54]/PRO=[RW,RW,,]
.IFNINS MLTNET INS LB:[IPNET]MLTNET
.IFNINS ...MNC INS LB:[IPNET]MLTCFG
NCP SET PROC IP TOP
NCP SET LIN IP-0-* ALL
MNC SHO VER
.;
.; Repeat the following two lines for each connection wanted.
.; For TCP connections, use TCP or TCA, depending on passive or
.; active. Also, you should set a local port for passive TCP.
.; (PORT n)
.;
.; For the remote host, you can give host:port, if you
.; want. For active TCP connections, you can use local port 0,
.; to get a random source port.
.; For passive TCP connetions, you can set host and/or remote
.; port to 0, to accept conncetions from any.
.;
.; At Johnny's end: IP-0-10
.; Mark Matlock (area 30) - 147 ms
.; mnc set cir ip-0-10 tcp host 0.0.0.0:0 <http://0.0.0.0:0> port
.; ncp set cir ip-0-10 sta
.;
.;mnc set cir ip-0-0 udp host <host> port <n>
.;ncp set cir ip-0-0 sta on
.;
MNC SET CIR IP-0-0 TCA HOST 192.168.1.49:7705 <http://192.168.1.49:7705>
PORT 0
NCP SET CIR IP-0-0 STA ON
On Sat, Jun 8, 2019 at 8:35 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
Well, just taking a peek at CURLY, I can also tell that you have not
managed to get the multinet links up and running, but are communicating
with DECnet over ethernet. :-)
? ?Johnny
On 2019-06-09 02:20, Kurt Hamm wrote:
That's it!? Everything works great.? I have
the node list and can
access
reachable nodes from the PDP-11.
This is just really wonderful.
As a thank you, I will leave the mailing list alone for a while.? ha!
Kurt
On Sat, Jun 8, 2019 at 6:42 PM Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>
<mailto:bqt at softjar.se <mailto:bqt at
softjar.se>>> wrote:
? ? ?Ok, a quick rundown on some of the more esoteric details
about lines
? ? ?and
? ? ?circuits might be useful here.
? ? ?First of all, Kurt, you might want to redo the NETGEN and not
set the
? ? ?system up for DECnet routing. It takes a lot
of resources,
and if you
? ? ?don't really want it, you are much better
off with a system
not even
? ? ?generated for it.
? ? ?The question about remote nodes are just for an initial
population of
? ? ?your local nodename database. All you need
there is really to
define
? ? ?MIM
? ? ?(1.13). You can then copy the whole nodename database from
MIM over to
? ? ?your machine that way instead. Let me know if
you want some
details on
? ? ?that step.
? ? ?On 2019-06-08 22:25, Mark Matlock wrote:
? ? ? > Kurt,
? ? ? >? ? ?If you want two circuits like UNA-0 and IP-0-0 I think you
? ? ?have to
? ? ? > be a routing node (but not an area router).
? ? ?Not really, but maybe. If you define multiple circuits, and
are an
? ? ?end-node, only one circuit will be active.
But others can
exist, and
? ? ?the
? ? ?system will fall back to some other circuit if the active one
goes
? ? ?down.
? ? ?So it can be used as a back connection.
? ? ?However, even as an end-node, you can have several *lines* on and
? ? ?active
? ? ?at the same time. And this is a trick to use if you want
? ? ?DECnet-over-IP,
? ? ?but want to be an endnode. You need ethernet for TCP/IP to
work, but
? ? ?you
? ? ?do not want DECnet to use the ethernet circuit.
? ? ?But you configure one IP line as well, and that is the one
DECnet will
? ? ?be using. Meanwhile, TCP/IP is using the
ethernet line.
? ? ?It might sound a little confusing, but think about it for a
second, and
? ? ?I hope it becomes clear. Otherwise, just ask,
and I'll try to
? ? ?explain it
? ? ?better.
? ? ? > Also, you should define all the nodes you want to talk to with
? ? ?NCP in
? ? ? > one of the startup files or do it with CFE but I prefer
startup
? ? ?so it?s
? ? ? > simple to change.
? ? ?I would actually say that you wouldn't. Of course, there is
nothing
? ? ?wrong in doing this, but if you want the full
HECnet nodename
database,
? ? ?it contains 700 nodes. That will take a while
to type in.
? ? ?However, you can copy the nodename database from another
DECnet node,
? ? ?and then use this.
? ? ?But you need at least the nodename of someone where you will
be copying
? ? ?from to start with, which is why I suggested
adding MIM at
the start.
? ? ?After that, there is [5,54]NNC which is the nodename
collector task.
? ? ?Run
? ? ?it, collect names from another node, and build a new database
with
? ? ?this.
? ? ?Then stop and restart the node name server, and you have all
the nodes
? ? ?defined.
? ? ?(The node name server is managed by the command SCP.
? ? ?So, SCP STOP followed by SCP START will do it.)
? ? ? ? ?Johnny
? ? ?--
? ? ?Johnny Billquist? ? ? ? ? ? ? ? ? || "I'm on a bus
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?||? on a psychedelic trip
? ? ?email: bqt at softjar.se <mailto:bqt at softjar.se>
<mailto:bqt
at softjar.se <mailto:bqt at softjar.se>>? ? ? ? ? ? ?||
? ? ?Reading murder books
? ? ?pdp is alive!? ? ? ? ? ? ? ? ? ? ?||? tryin' to stay hip" -
B.
Idol
1792
days inactive
1793
days old
32 comments
4 participants
participants (4)
-
bqt＠softjar.se -
kurt＠hamm.me -
mark＠matlockfamily.com -
supratim＠riseup.net