That's what the thread between me and Paul right
now is about. And
Paul have this fixed in his code now. Next version should have it fixed.
Johnny
On 2023-04-11 02:54, Thomas DeBellis wrote:
I don't have an informed opinion yet, as I
only just started
looking. The code is kind of odd in that it is half Tops-10 and half
Tops-20, but not in a GLXLIB sort of way.
That being said, what you've pointed out strikes me as correct. Now,
if I just look at the show node /xxx/status, I was wondering about
something:
NCP>*tell a2rtr:: shoW noDE twenex:: statUS *
Remote Node = 31.29 (TWENEX)
Circuit = DMC-31
Next Node = 31.3 (PYRTR)
NCP>*telL pyrtr:: shoW noDE twenex:: statUS *
Remote Node = 31.29 (TWENEX)
State = Reachable
Delay = 1
Cost = 24
Hops = 2
Circuit = MUL-31-32
Isn't pyrtr:: supposed to be telling me what the next node is?
Maybe that's why netpth is asking about circuits?
On 4/10/23 8:42 PM, Johnny Billquist wrote:
Obviously, there is no good reason to ask for the
circuit
information. You already got all you needed from the show node xx
status, right?
Johnny
On 2023-04-11 02:37, Thomas DeBellis wrote:
It sits in a loop doing the following:
show node xxx:: status
From that it picks out the appropriate circuit and does a
show circuit xxx status
So, to show the path from venti2:: to twenex::, the first few
commands would be
NCP>*shoW noDE twenex:: statUS *
Remote Node = 31.29 (TWENEX)
Active Links = 0
Delay = 1
Circuit = NI-0-0
Next Node = 2.1023 (A2RTR)
NCP>*shoW cirCUIT ni-0-0 staTUS *
Circuit State Loopback Adjacent Block
Name Node Size
NI-0-0 On 2.1023 (A2RTR) 591
Designated Router = 2.1023 (A2RTR)
NI-0-0 2.520 (TOMMYT) 1476
NCP>*tell a2rtr:: shoW noDE twenex:: statUS *
Remote Node = 31.29 (TWENEX)
Circuit = DMC-31
Next Node = 31.3 (PYRTR)
NCP>*tell a2rtr:: shoW cirCUIT dmc-31 stATUS *
Circuit = DMC-31
State = On
Adjacent Node = 31.3 (PYRTR)
Block Size = 576
NCP>*telL pyrtr:: shoW noDE twenex:: statUS *
Remote Node = 31.29 (TWENEX)
State = Reachable
Delay = 1
Cost = 24
Hops = 2
Circuit = MUL-31-32
NCP>*telL pyrtr:: shoW cirCUIT mul-31-32 statUS **
*
Circuit = MUL-31-32
Adjacent Node = 31.32 (PIPY)
Block Size = 576
State = On
NCP>*telL pipy:: shOW noDE twenex:: statUS **
*
Remote Node = 31.29 (TWENEX)
State = Reachable
Type = Nonrouting IV
Cost = 4
Hops = 1
Circuit = VDE-31
NCP>*tell pipy:: shoW cirCUIT vde-31 staTUS*
Circuit = VDE-31
Adjacent Node = 31.1022 (AHIMSA)
Block Size = 591
State = On
Adjacent Node = 31.1020 (MOKSHA)
Block Size = 591
Adjacent Node = 31.13 (FEDACH)
Block Size = 1498
Adjacent Node = 31.19 (MACOS9)
Block Size = 1498
Adjacent Node = 31.14 (FOMFOR)
Block Size = 1498
Adjacent Node = 31.26 (W2000S)
Block Size = 1498
Adjacent Node = 31.18 (RAPTOR)
Block Size = 1498
Adjacent Node = 31.21 (WXPEE2)
Block Size = 1498
Adjacent Node = 31.22 (TRU64)
Block Size = 1490
Adjacent Node = 31.20 (WFW311)
Block Size = 1498
Adjacent Node = 31.16 (WEXPEE)
Block Size = 1498
Adjacent Node = 31.11 (CLOUDY)
Block Size = 1498
Adjacent Node = 31.10 (QCOCAL)
Block Size = 1498
Adjacent Node = 31.12 (JUICHI)
Block Size = 576
Adjacent Node = 31.23 (XLVII)
Block Size = 1498
Adjacent Node = 31.24 (TSTVAX)
Block Size = 1498
Adjacent Node = 31.28 (RST101)
Block Size = 598
Adjacent Node = 31.31 (XLIV)
Block Size = 1498
Adjacent Node = 31.33 (XL)
Block Size = 1498
Adjacent Node = 31.34 (NANAJU)
Block Size = 576
Adjacent Node = 31.35 (NJEVX1)
Block Size = 1498
Adjacent Node = 31.36 (NJEVX2)
Block Size = 1498
Adjacent Node = 31.41 (KDJ11E)
Block Size = 576
Adjacent Node = 31.44 (XLVI)
Block Size = 1498
Adjacent Node = 31.39 (ROUT20)
Block Size = 1498
Adjacent Node = 31.38 (LV)
Block Size = 1498
Adjacent Node = 31.15 (OSTARA)
Block Size = 1498
Adjacent Node = 31.30 (VAXSTN)
Block Size = 1498
Adjacent Node = 31.42 (XXXV)
Block Size = 1498
Adjacent Node = 31.1021 (PYDNET)
Block Size = 591
Adjacent Node = 31.27 (MACOS7)
Block Size = 1498
/Adjacent Node = 31.29 (//TWENEX//)//
// Block Size = 576/
------------------------------------------------------------------------
On 4/10/23 6:30 PM, Johnny Billquist wrote:
> Could you tell in detail which NICE messages you are generating?
>
> In general, if I were to do such a tool, I would normally do the
> NICE message that generates the same request as NCP SHO NOD do.
>
> To give an example from JOCKE to A2RTR:
>
> .ncp sho nod a2rtr
>
> Node summary as of 11-APR-23 00:26:52
>
> Remote Active Next
> Node State Links Delay Circuit Node
>
> 2.1023 (A2RTR) 1.15 (PONDUS)
>
> .ncp tell pondus sho nod a2rtr
>
> Node summary as of 11-APR-23 00:27:05
>
> Remote Active Next
> Node State Links Delay Circuit Node
>
> 2.1023 (A2RTR) 1.13 (MIM)
>
> .ncp tell mim sho nod a2rtr
>
> Node summary as of 11-APR-23 00:27:21
>
> Remote Active Next
> Node State Links Delay Circuit Node
>
> 2.1023 (A2RTR) 31.3 (PYRTR)
>
> .ncp tell pyrtr sho nod a2rtr
>
> Node summary as of 11-APR-23 00:27:30
>
> Remote Active Next
> Node State Links Delay Circuit Node
>
> 2.1023 (A2RTR)
>
>
>
> Sadly PYRTR did not actually tell what the next node is here. Not
> sure if it's just an old version of PYRTR, or if there is
> something for Paul to improve. But you should get the idea...
>
> Also, note that this will give the forward path, which in DECnet
> most certainly might be different than the return path...
>
> Johnny
>
>
> On 2023-04-10 23:58, Thomas DeBellis wrote:
>> Now that I'm done with Kermit-20, I wanted to get back to
>> finishing up some other work that I had been doing. FAL, DAP and
>> NFT are in good enough shape for me to leave them alone for the
>> moment, so that's another rabbit hole I've gotten myself out of.
>>
>> I'm now looking fix an error that I somehow introduced into
>> MMAILR (SMTP over DECnet). Fixing this required modifying DDT,
>> whichIhad to do to fix another issue I had introduced into
>> Kermit. I wanted to have a quick look at what Tops-20 hosts
>> might be up on HECnet and wrote up a little batch job to use
>> NETPTH to test connectivity.
>>
>> NETPTH is a nifty utility to find paths between DECnet nodes. It
>> builds a connection the NCU's of various nodes to determine the
>> path that a message might take to get there. Think of it like
>> traceroute or ping -R (RECORD_ROUTE option).
>>
>> It almost never works...
>>
>> Before I roll up my sleeves and jump into this I was wondering if
>> anybody had any observations about the errors I'm seeing?
>>
>> ------------------------------------------------------------------------
>>
>>
>>
*TINA*::*PAMINA*::*KLIO*::*TWLGHT*::*RARITY*::*FLUSHY*::*RBDASH*::*APPLEJ*::*PINKIE*::*DISCRD*::*TWENEX*::
>>
>>
>> From Via Back Thru Cost Hops
>> VENTI2 (2.522) =>NI-0-0 /BRG-0 <= A2RTR (2.1023)
>> -1 -1
>> A2RTR (2.1023) =>DMC-31 /
>> ?NETCFO Can't find Output Circuit parameter
>>
>> *SAMT20*::
>> ?NETURN Unreachable node
>>
>> *TOMMYT*::
>>
>> From Via Back Thru Cost Hops
>> VENTI2 (2.522) =>NI-0-0 /NI-0-0 <= TOMMYT (2.520)
>> 1 1
>>
>> *BITXT2*::*BITXT0*::*MINDY*::*FALLON*::*JOSHUA*::*OLAF*::
>>
>> From Via Back Thru Cost Hops
>> VENTI2 (2.522) =>NI-0-0 /BRG-0 <= A2RTR (2.1023)
>> -1 -1
>> A2RTR (2.1023) =>
>> ?NETCFO Can't find Output Circuit parameter
>>
>> *WALACH*::
>>
>> From Via Back Thru Cost Hops
>> VENTI2 (2.522) =>NI-0-0 /BRG-0 <= A2RTR (2.1023)
>> -1 -1
>> A2RTR (2.1023) =>DMC-29-206 /
>> ?NETCFO Can't find Output Circuit parameter
>>
>> *SOL*::
>>
>> From Via Back Thru Cost Hops
>> VENTI2 (2.522) =>NI-0-0 /BRG-0 <= A2RTR (2.1023)
>> -1 -1
>> A2RTR (2.1023) =>MUL-59-1016 / DMC-1 <= STORTR (59.1016)
>> -1 -1
>> STORTR (59.1016) =>GRE-16 /
>> ?NETCFO Can't find Output Circuit parameter
>>
>> *FENCER*::
>>
>> From Via Back Thru Cost Hops
>> VENTI2 (2.522) =>NI-0-0 /BRG-0 <= A2RTR (2.1023)
>> -1 -1
>> A2RTR (2.1023) =>MUL-59-1016 / DMC-1 <= STORTR (59.1016)
>> -1 -1
>> STORTR (59.1016) =>GRE-16 /
>> ?NETPTH NTMAN failed, reason:
>> Parameter missing
>> $
>>
>>
>> _______________________________________________
>> 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 to hecnet-leave(a)lists.dfupdate.se
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se