11 Apr
2023
11 Apr
'23
2:58 a.m.
On 2023-04-11 02:47, Paul Koning wrote:
Not sure you would be able to tell. Type says if it's an endnode, L1 or
L2 router. Nothing else, as far as I've ever seen.
Looking at KRYLBO::
.ncp tell krylbo sho adj nod stat
Adjacent nodes status as of 11-APR-23 02:52:29
Remote Active
Node State Links Delay Type Cost Hops
Circuit
1.13 (MIM) 1 5 Area 10 1 IP-0-0
59.1016 (STORTR) Area 9 2 QNA-0
59.1017 (HOBBY2) Area 4 1 QNA-0
59.1018 (HOBBYH) Area 4 1 QNA-0
MIM is obviously RSX.
STORTR and HOBBYH are PyDECnet, but I believe that HOBBY2 might be a
Cisco box. Anyway, it's clearly up and running, but not responding to NICE.
Hmm. I just noticed that STORTR is actually coming through HOBBYH, so
apparently type can be reported for non-adjacent nodes sometimes.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On Apr 10, 2023, at 8:41 PM, Johnny Billquist
<bqt(a)softjar.se> wrote:
On 2023-04-11 02:19, Paul Koning wrote:
Yes. And also to know the type of nodes that don't accept NICE connections. ...
RSTS is L1 only, but my point is that you'd see it if you happen to have a RSTS node
in your path. For HECnet, not all that likely. According to my notes, one RSTS bug is
that it reports node type even if the node isn't adjacent (no idea what it is
reporting in that case) and in addition it encodes that value incorrectly. The mapper
would like to use that data but given that bug it doesn't currently.
Hmm. Yeah, not sure I know of any RSTS/E acting as any kind of router. Maybe someone else
knows of one?
As for node type, right. Checked RSX now, and it only reports this for adjacent nodes.
Empty field for others.
But not sure how the mapper would use it. The mapper is talking to each node anyway,
right? And getting type from there.
Or would you use this to not even go talking to endnodes?