[Simh] DECnet for TOPS-10

Timothe Litt litt at ieee.org
Fri Apr 19 21:08:30 EDT 2013


You need the DECnet tape that goes with the monitor version you're running.

http://pdp-10.trailing-edge.com/ is probably a better source, in that 
you can browse the tape contents.

TOPS-10 7.04 needs the 7.04 DECnet tape.
TOPS-20 4.1 needs the 4.1 DECnet tape.

You don't need DECnet Source tape (that's for the MCB - DN20 code for 
the KL).
The tapes with TSU in the description are autopatch tapes; you don't 
need them (at least to get started with.)

This communication may not represent my employer's views,
if any, on the matters discussed.

On 19-Apr-13 13:12, Rob Jarratt wrote:
> Is there any particular software distribution tape you would recommend out
> of these:
> http://bitsavers.informatik.uni-stuttgart.de/bits/DEC/pdp10/magtape/dec_dist
> ribs/decnet/
>
> Thanks
>
> Rob
>
>> -----Original Message-----
>> From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-
>> edge.com] On Behalf Of Timothe Litt
>> Sent: 19 April 2013 03:27
>> To: 'Johnny Eriksson'
>> Cc: simh at trailing-edge.com
>> Subject: Re: [Simh] DECnet for TOPS-10
>>
>>> how can I check in TOPS-20 to see if the device is visible and then
>>> install DECnet?
>> You need to install DECnet first.  It's pretty easy.
>>     See
>> http://ia801607.us.archive.org/21/items/bitsavers_decpdp10TOTMTOPS20D
>> ECnet20ProgrammersGuideJan80_10120529/AA-5091B-TM_TOPS-
>> 20_DECnet-20_Programmers_Guide_Jan80.pdf
>>
>> ps:<system>4-1-config.cmd
>> add 1 line:
>> NODE name number (e.g. NODE HAPPY 7.3)
>>
>> ps:<system>sysjob.run
>> Look for last job.  If FAL or NETCON is missing, add as follows at end of
> file:
>> JOB <n+1> \LOG OPERATOR XX OPERATOR
>> ENA
>> RUN SYS:FAL
>> \
>> JOB <n+2> \LOG OPERATOR XX OPERATOR
>> ENA
>> RUN SYS:NETCON
>> \
>>
>> (n.b. XX is literal - NOT the operator password.)
>>
>> Reboot
>>
>> $opr
>> opr> enter ncp
>> ncp> show known lines
>> ncp> show known circuits
>> ncp> exit
>> opr> exit
>>
>> (Add char, stat, or count to the show commands as desired.  ? will give
> in-
>> line help.)
>>
>> inf decnet for quick node status.
>>
>> For TOPS-10:
>> MONGEN will prompt for the DECnet node name/number, etc.  Build & boot
>> the monitor.
>>
>> .resources should (I think) show KDP, and you should see KDPLDR run at
>> startup
>>
>> .r opr
>> (same)
>>
>> or
>> .network /anf
>> .network /decnet
>>
>> .node <name> for reachability of a node
>>
>> Enjoy.
>>
>> This communication may not represent my employer's views, if any, on the
>> matters discussed.
>>
>> On 18-Apr-13 14:58, Rob Jarratt wrote:
>>>> -----Original Message-----
>>>> From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-
>>>> edge.com] On Behalf Of Johnny Eriksson
>>>> Sent: 14 April 2013 21:10
>>>> To: simh at trailing-edge.com
>>>> Subject: Re: [Simh] DECnet for TOPS-10
>>>>
>>>> <r.jarratt at computer.org> wrote:
>>>>
>>>>> That has got to be worth integrating into the latest SIMH. Does that
>>>>> mean we can get DECnet running on TOPS-10 on SIMH? I would love to
>>>>> know how you actually install and set it up on TOPS-10.
>>>>>
>>>>> I will try to find some time to get the KMC/DUP into the latest SIMH.
>>>> You are welcome.  A number of random points:
>>> I have compiled something very basic into PDP10, the network code is
>>> actually stubbed out at the moment as I have to replace it with
>>> current SIMH code (going to look at TMXR).
>>>
>>> In the meantime, how can I check in TOPS-20 to see if the device is
>>> visible and then install DECnet? I remember finding some docs but I
>>> can't find them again now.
>>>
>>>
>>>
>>>> * My code sends the DDCMP frames out as UDP datagrams, and receives
>>>>     frames the same way.  You simply specify src/dst ports, and possibly
>>>>     an address (defaulting to 127.0.0.1).  This means that there is no
>>>>     need to do elaborate (blocking) setups of TCP connections etc. from
>>>>     inside the simulator.  This also makes it trivial to connect two
>>>>     simulators running on the same machine, or on the same (trusted)
> LAN.
>>>> * A side effect of this is that you can have a helper process on your
>>>>     machine that does the TCP magic and also encrypts the traffic out
>>>>     on the evil internet.  My normal (at the moment defunct) setup is
>>>>     done that way.  One such program is on the site, named "stuk2.c"
>>>>     (don't ask...)
>>>>
>>>> * You can in theory write a helper process to talk to some real
>>>>     piece of hardware.  I have not tested, but it should work to send
>>>>     the frames to a serial port and connect it to a real machine
>>>>     running async DECnet on a terminal line...
>>>>
>>>> * The current crypto in stuk2 is weak.  Not the algorithm itself,
>>>>     RC4 (tm) is used, but some random padding etc. should be applied
>>>>     on the data stream, since it normally consists of 6-byte idle
>>>>     frames, with mostly known bits...
>>> Not sure what you are referring to here.
>>>
>>> Thanks
>>>
>>> Rob
>>>
>>>> * The actual KS10 supports one KDP with 2 DUPs.  There are several
>>>>     reasons for this, like unibus load, unibus space and speed.  This
>>>>     places some limits in case one wants to build a network of emulators
>>>>     and want to run both ANF and DECnet.  The KMC itself supports 16
>>>>     if I remember correctly.  We should have at least 6-8, and allow
>>>>     for a fairly simple mod to Tops10 to handle them.
>>>>
>>>> * I am willing to help out, but I have very limited time until after
>>>>     the CuG conference, mid May.
>>>>
>>>>> Regards
>>>>>
>>>>> Rob
>>>> --Johnny
>>>> _______________________________________________
>>>> Simh mailing list
>>>> Simh at trailing-edge.com
>>>> http://mailman.trailing-edge.com/mailman/listinfo/simh
>>> _______________________________________________
>>> Simh mailing list
>>> Simh at trailing-edge.com
>>> http://mailman.trailing-edge.com/mailman/listinfo/simh


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5159 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20130419/984fccf8/attachment-0002.bin>


More information about the Simh mailing list