11 Apr
2023
11 Apr
'23
4:19 p.m.
On 2023-04-11 14:31, Paul Koning wrote:
Good catch. Indeed, KRYLBO do also have a direct link with STORTR, but
that one have a cost of 10.
Didn't consider that possibility. :-)
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:58 PM, Johnny Billquist
<bqt(a)softjar.se> 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.
It's possible for a node to be adjacent but routed via two hops -- if the circuit
cost is greater than the path cost of that two-hop path. Not common but it can happen.
If so, the node type would be known from the circuit state. That's presumably the
case here, with NCP picking up the list of adjacent nodes from the circuit state and then
doing read node status for each node it found. ...
Or would you use this to not even go talking to endnodes?
Yes. And also to know
the type of nodes that don't accept NICE connections.