26 Sep
2022
26 Sep
'22
3:10 p.m.
On Sep 26, 2022, at 8:52 AM, Supratim Sanyal
<supratim(a)riseup.net> wrote:
Paul - a bit more information:
- Pydecnet is reporting this: Remote node name XX does not match ours: 31.43
- Pydecnet ini has this:
node 43 XX --inbound-verification HELLOVAX --outbound-verification HELLOVAX
circuit DDCMP-31-43 DDCMP tcp:31431:172.31.31.31:31430 --t3=15 --cost=4 --verify
I don't know why that was accepted. On Phase IV nodes, which your PyDECnet node is,
node config lines should have an area number included. So try 31.43 instead of plain
43.
Could you set up TRACE level logging and send the result of the trace? And also, can you
use "tcpdump -w somefile.pcap -B 1500 tcp port 31431" to get a wire trace of the
protocol exchanges? Those might help me get a better understanding of who does what.
paul
- DECnet/VAX 1.3 on VMS 2.0 has this:
$ MCR NCP
NCP>LIST LOCAL
CONFIGURATION DATABASE LOCAL NODE
LOCAL NODE NAME: XX
LOCAL NODE NUMBER: 43
MAXIMUM NUMBER OF LOGICAL LINKS: 8
MAXIMUM NUMBER OF REMOTE NODES: 10
NCP>
Opcom, 12:50:49.17, NETACP Accnt=
Opcom, DECnet line XMA0: INIT message protocol error from address: 32, name:
PIPY
NCP>LIST KNOWN REMOTES
CONFIGURATION DATABASE NODE XX
NODE NUMBER: 43
PASSWORD REMOTE RECEIVES DURING INITIALIZATION: HELLOVAX
PASSWORD REMOTE SENDS DURING INITIALIZATION: HELLOVAX
SECONDARY LOADER FILE:
TERTIARY LOADER FILE:
DOWNLINE LOAD FILE:
DEFAULT NON-PRIVILEGED USERID: GUEST
DEFAULT NON-PRIVILEGED ACCOUNT NAME:
DEFAULT PRIVILEGED USERID: SYSTEM
DEFAULT PRIVILEGED ACCOUNT NAME:
NSP CONNECT TIMEOUT CONSTANT 0 SECONDS
REMOTES SERVER NODE:
SERVERS LINE TO REMOTE:
REMOTES HOST NODE:
CONFIGURATION DATABASE NODE PIPY
NODE NUMBER: 32
PASSWORD REMOTE RECEIVES DURING INITIALIZATION: HELLOVAX
PASSWORD REMOTE SENDS DURING INITIALIZATION: HELLOVAX
SECONDARY LOADER FILE:
TERTIARY LOADER FILE:
DOWNLINE LOAD FILE:
DEFAULT NON-PRIVILEGED USERID: GUEST
DEFAULT NON-PRIVILEGED ACCOUNT NAME:
DEFAULT PRIVILEGED USERID: SYSTEM
DEFAULT PRIVILEGED ACCOUNT NAME:
NSP CONNECT TIMEOUT CONSTANT 0 SECONDS
REMOTES SERVER NODE:
SERVERS LINE TO REMOTE:
REMOTES HOST NODE:
NCP>EX
Opcom, 12:50:56.23, NETACP Accnt=
Opcom, DECnet line XMA0: INIT message protocol error from address: 32, name:
PIPY
NCP>EXIT
$
Opcom, 12:51:01.25, NETACP Accnt=
Opcom, DECnet line XMA0: INIT message protocol error from address: 32, name:
PIPY
$
Opcom, 12:51:06.27, NETACP Accnt=
Opcom, DECnet line XMA0: INIT message protocol error from address: 32, name:
PIPY
On 9/25/22 11:20 PM, Supratim Sanyal wrote:
Hi Paul,
I made some progress and need help with the next step - connecting to pydecnet.
Current status is DECnet 1.3 is up on VAX/VMS 2.0, I can SET HOST to self, and have DMC11
XMA0 device up and a link to DECnet/Python configured.
There is no way to avoid a receive password that I can figure out, so I am using HELLOVAX
as both receive and transmit pw:
CONFIGURATION DATABASE NODE PIPY
NODE NUMBER: 32
PASSWORD REMOTE RECEIVES DURING INITIALIZATION: HELLOVAX
PASSWORD REMOTE SENDS DURING INITIALIZATION: HELLOVAX
SECONDARY LOADER FILE:
TERTIARY LOADER FILE:
DOWNLINE LOAD FILE:
DEFAULT NON-PRIVILEGED USERID: GUEST
DEFAULT NON-PRIVILEGED ACCOUNT NAME:
DEFAULT PRIVILEGED USERID: SYSTEM
DEFAULT PRIVILEGED ACCOUNT NAME:
NSP CONNECT TIMEOUT CONSTANT 0 SECONDS
REMOTES SERVER NODE:
SERVERS LINE TO REMOTE:
REMOTES HOST NODE:
CONFIGURATION DATABASE LINE XMA0
DEVICE TYPE: DMC11
CONTROLLER NUMBER: 0
LINE NUMBER:0
LINE ADDRESS:0
ASSOCIATED NODE: PIPY
ASSOCIATED BUFFER SIZE: 192
NUMBER OF BUFFERS TO ALLOCATE: 6
CHARACTERISTICS: FULLDUPLEX
MOP TIMEOUT CONSTANT: 10 SECONDS
pydecnet .ini has:
circuit DDCMP-31-43 DDCMP tcp:31431:172.31.31.31:31430 --t3=15 --cost=4
node 31.43 XX --inbound-verification HELLOVAX --outbound-verification HELLOVAX
and I keep getting OPCOM messages on the VAX saying:
Opcom, 03:17:09.56, NETACP Accnt=
Opcom, DECnet line XMA0: INIT message protocol error from address: 32, name:
PIPY
I must be very close to getting 31.43 (XX) in if Phase II is supported like you indicated
...
Anyway, advice for me please?
Best regards
Supratim
STATUS OF LINE, AS OF 26-SEP-2022 03:13:57.44
LINE-ID STATE REMOTE
DMC11_0 OFF PIPY
On 9/25/22 12:51 PM, Johnny Billquist wrote:
--
<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 On 2022-09-25 18:41, Paul Koning wrote:
--
<SANYALNET-LABS-QR-CODE.png>
> On Sep 25, 2022, at 8:03 AM, Johnny Billquist <bqt(a)softjar.se
<mailto:bqt@softjar.se>> wrote:
>
> On 2022-09-25 13:54, Supratim Sanyal wrote:
>>> On Sep 25, 2022, at 5:44 AM, Johnny Billquist <bqt(a)softjar.se
<mailto:bqt@softjar.se>> wrote:
>>>
>>> Uh... Do you have Phase V installed?
>> Hehe - It’s VAX VMS 2.0 running DECnet 1.3 which I think is phase II based on the
gunkies post
athttps://gunkies.org/wiki/Installing,_Configuring,_and_Testing_DECnet_V1.3…
<https://gunkies.org/wiki/Installing,_Configuring,_and_Testing_DECnet_V1.3_on_VMS_V2.0><https://gunkies.org/wiki/Installing,_Configuring,_and_Testing_DECnet_V1.3_on_VMS_V2.0
<https://gunkies.org/wiki/Installing,_Configuring,_and_Testing_DECnet_V1.3_on_VMS_V2.0>>
>
> Oh! Wow. Other end of spectrum. I don't remember ever touching that. Earliest VMS
I ever played with was 3.7, if I remember right. Also never used Phase II. Earliest was
Phase III. Did Phase II even support more than 43 nodes? I guess I should check some. :-)
43? The spec says Phase II node numbers are in the range 2 to 240, but they aren't
actuallly used for anything. So, in a sense, Phase II can handle any size network. But
it doesn't do routing except the limited "intercept" stuff.
Still, with PyDECnet intercept, a TOPS-20 V4 node can talk to any HECnet node.
43 since that was the node number Supriatim was trying to set.
According to Wikipedia, phase II only supported 32 nodes. But as I've never used it,
I don't really know what to think.
Johnny