26 Oct
2022
26 Oct
'22
2:09 a.m.
At this point, the V3.5 node 31.42 (XXXV) continues to happily speak
Phase-IV on UNA-0 and Phase-II on DMC-0. I have added guest accounts on
both 31.42 (XXXV) and 43 (XX) with password welcome123. So, to log into
VAX/VMS 2.0 from any HECnet node that supports RTERM, 31.42 (XXXV) can
be used as a jumpbox. Per Paul, if DECnet/VAX v3.0 running on VMSv3.5
implemented intercept, it would have been a great router.
I also wonder how V3.5 and V2.0 seem to be fine with current clock times.
Anyway, from an ovms7.3 node, for example, here is logging into VAX/VMS
v2.0 with DECnet/VAX v1.5.
$
$ set host/appl=rterm 31.42
%REM-I-CONNECTION, connection made using RTERM protocol
---snip---
Username: GUEST
Password:
Welcome to XXXV (31.42), a DEC VAX-11/780 running VAX/VMS 3.5
You can login over DECnet using:
$ MCR NCP SET NODE XXXV ADDR 31.42
$ SET HOST/APPLICATION_PROTOCOL=RTERM XXXV
Admin contact: https://goo.gl/FqzyBW
Have fun!
$
$ set host xx
Username: GUEST
Password:
Welcome to VAX/VMS Version V2.0 on node _XX::
$
$ show time
26-OCT-2022 00:02:44
$
$ show net
Node Address Line State
XX 43 LOCAL ON
PIPY 32 XMA0 ON
XXXV 42 XMB0 ON
$
$ lo
GUEST logged out at 26-OCT-2022 00:03:13.87
%REM-S-END, control returned to node _XXXV::
$
$ show time
26-OCT-2022 00:03:14
$
$ lo
GUEST logged out at 26-OCT-2022 00:03:17.43
%REM-S-END, control returned to node QCOCAL::
On 10/20/22 7:08 AM, Supratim Sanyal wrote:
On 10/20/22 7:02 AM, Steve Davidson wrote:
--
If pydecnet implements PMR (Poor Man’s Routing)
and allows connection
between any 2 DECnet phases you might be able to make something work.
It would look something like:
set host <PyDECnet-node>::<destination-node>
ah yes ... it was worth a try. thanks.
$ set host pipy::xx
%SYSTEM-F-LINKEXIT, network partner exited
-Steve
SF:IP2
--
_______________________________________________
HECnet mailing list --hecnet(a)lists.dfupdate.se
To unsubscribe send an email tohecnet-leave(a)lists.dfupdate.se On Oct 20, 2022, at 06:43, Supratim Sanyal
<supratim(a)riseup.net> wrote:
On 10/20/22 5:10 AM, Trevor Warwick wrote:
_______________________________________________
HECnet mailing list --hecnet(a)lists.dfupdate.se
To unsubscribe send an email tohecnet-leave(a)lists.dfupdate.se
Should later VMS be able to talk to it ? It doesn't seem to work
for me (VMS 5.4):
I haven't been able to talk to it from VMS later than 3.5 either.
CTERM and RTERM don't seem to find what they look for.
PRRSI$ set host 31787
%SYSTEM-F-CONNECFAIL, connect to network object timed-out or failed
If I try from VMS 7.3
KRAKAR$ set host /app=rterm 31787
%SYSTEM-F-LINKABORT, network partner aborted logical link
KRAKAR$ set host /app=cterm 31787
%SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node
On Tue, 18 Oct 2022 at 22:40, Supratim Sanyal <supratim(a)riseup.net>
wrote:
On 10/18/22 11:07 AM, Johnny Billquist wrote:
> Well, outbound to RSX also don't seem to work.
>
> Maybe you could do another trace when trying to connect from
RSX to
> VMS? That might help me some more.
tcpdump attached (31.12=RSX, 31.43=VMS2.0, 31.32=pydecnet);
here's what
RSX says - it tries "RMT" and fails. TOPS-10 uses "NRT" and
succeeds.
>ncp
NCP>show node xx
Node summary as of 18-OCT-22 21:32:12
Remote Active Next
Node State Links Delay Circuit Node
31.43 (XX) 0 30 31.32 (PIPY)
NCP>exit
>set host xx
NCT -- CTERM is not available on host
NCT -- Using RMT
RMT -- Network access failure
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
_______________________________________________
HECnet mailing list --hecnet(a)lists.dfupdate.se
To unsubscribe send an email tohecnet-leave(a)lists.dfupdate.se
--
SANYALNET-LABS-QR-CODE.png
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se 