[HECnet] DECnet-VAX V3.0, VMS V3.5 (Was Re: Oldest VAX/VMS for VAX-11/730 on HECNET)

[Paul Koning]

> On Dec 15, 2021, at 7:00 PM, Supratim Sanyal <supratim at riseup.net> wrote:
> 
> OK, so I fired up a VAX/VMS 3.5 node and gave it the address 42 (just a coincidence, not an answer to any question). I demoted it to an end-node on a dedicated virtual ethernet adapter for the circuit with DECnet/Python. No adjacency is established. A tshark indicates DECnet-VAX V3.0 is appearing as 1.42 on the wire. Since there is no way to ask DECnet-VAX V3.0 to pretend it is 31.42, I am not sure what the next step, if any, might be to hook this up to my area on HECnet.
> 
> tshark dump is at https://www.dropbox.com/s/40hvr4x6iq3esl8/tshark-31.12-31.42-DECnet-VAX-V3.0.tar.bz2?dl=0 <https://www.dropbox.com/s/40hvr4x6iq3esl8/tshark-31.12-31.42-DECnet-VAX-V3.0.tar.bz2?dl=0> . Maybe Paul has some advice?
> 
> Note: When DECnet-VAX V3.0 was configured as a L1 router, it oscillated between "circuit up" and "line fault" every few seconds.
> 
> $ mc ncp show exec char
> Node Volatile Characteristics as of 14-DEC-1984 23:46:34
> 
> Executor node = 42 (XXXV)

So I see that "max areas" does not appear in the help you showed.  What happens if you attempt to set it anyway?  Is it rejected?

What happens if you attempt to set the executor address to 31.42?

The fact it doesn't even show an area number is an amazing bug.  I wonder what the VMS people thought they were doing.

	paul


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.sonic.net/mailman/private/hecnet-list/attachments/20211216/d2b8cae0/attachment.htm>