Sometime overnight the chat service #USWCH:WA3WLH-14 on the US West regional chat hub #USWST:WA3WLH-15 dropped the chat link with my home chat service WLHCHT:WA3WLH-11 on node WLHNOD:WA3WLH-7. This is not unexpected given random weirdness on the internet and is typically the result of some secondary or child chat link hanging on to NETROM info for way too long. It is easy to confirm by reviewing the chat log for the dreaded "Refusing link from WA3WLH-14 to WA3WLH-11 to prevent a loop.". I assumed the drop last night was due to this sort of loop prevention so I never bothered to verify since the condition typically clears within 12 hours or so.
Now that it is well late in the afternoon I see that while there is a good AXUDP link between these nodes the chat services remain disconnected so I had a look in the chat log. I can see a chat service connect from my home node to the west hub followed almost immediately by a disconnect from the west hub but where there used to be the loop prevention message there is no obvious reason that I can see. Here is what I see in actual chat log file:
250418 20:30:11 |#USWCH??? Connecting to Chat Node #USWCH
250418 20:30:11 <#USWCH??? *** CONNECTED
250418 20:30:11 >#USWCH??? C WA3WLH-14
250418 20:30:12 <#USWCH??? WLHNOD:WA3WLH-7} Connected to #USWCH:WA3WLH-14
250418 20:30:13 <#USWCH??? [BPQChatServer-6.0.24.69]
250418 20:30:13 >#USWCH??? *RTL
250418 20:30:13 >#USWCH??? KWA3WLH-11 WA3WLH-14 6.0.24.69
250418 20:30:25 |#USWCH??? Chat Node WA3WLH-14 Disconnected
I had a QTT monitor on the AXUDP port running at the time so here is the corresponding monitor:
20:30:12R WA3WLH-7>WA3WLH-15 Port=1 <I C P S7 R3> NET/ROM
? WA3WLH-11 to WA3WLH-14 ttl 25 cct=0402 <CON REQ> w=4 WA3WLH-11 at WA3WLH-11 t/o 60
20:30:12T WA3WLH-15>WA3WLH-7 Port=1 <RR R F R0>
20:30:12T WA3WLH-15>WA3WLH-7 Port=1 <I C P S3 R0> NET/ROM
? WA3WLH-14 to WA3WLH-11 ttl 25 cct=0402? <CON ACK> w=153 my cct=058A
20:30:12R WA3WLH-7>WA3WLH-15 Port=1 <RR R F R4>
20:30:12T WA3WLH-15>WA3WLH-7 Port=1 <I C P S4 R0> NET/ROM
? WA3WLH-15 to WA3WLH-11 ttl 25 cct=0402? <INFO S0 R0>:
[BPQChatServer-6.0.24.69]
20:30:13R WA3WLH-7>WA3WLH-15 Port=1 <RR R F R5>
20:30:13R WA3WLH-7>WA3WLH-15 Port=1 <I C P S0 R5> NET/ROM
? WA3WLH-11 to WA3WLH-14 ttl 25 cct=058A? <INFO S0 R1>:
*RTL
KWA3WLH-11 WA3WLH-14 6.0.24.69
20:30:13T WA3WLH-15>WA3WLH-7 Port=1 <RR R F R1>
20:30:14T WA3WLH-15>WA3WLH-7 Port=1 <I C P S5 R1> NET/ROM
? WA3WLH-15 to WA3WLH-11 ttl 25 cct=0402? <INFO S1 R1>C:
xZJM+-NLKWHILKVH+JOUw4wqP54T(IsL@"T2T<D||=.np
20:30:14R WA3WLH-7>WA3WLH-15 Port=1 <RR R F R6>
20:30:24R WA3WLH-7>WA3WLH-15 Port=1 <I C P S1 R6> NET/ROM
? WA3WLH-11 to WA3WLH-14 ttl 25 cct=058A? <INFO ACK R2>
20:30:24T WA3WLH-15>WA3WLH-7 Port=1 <RR R F R2>
20:30:25T WA3WLH-15>WA3WLH-7 Port=1 <I C P S6 R2> NET/ROM
? WA3WLH-15 to WA3WLH-11 ttl 25 cct=0402? <DISC REQ>
20:30:25R WA3WLH-7>WA3WLH-15 Port=1 <RR R F R7>
20:30:25R WA3WLH-7>WA3WLH-15 Port=1 <I C P S2 R7> NET/ROM
? WA3WLH-11 to WA3WLH-15 ttl 25 cct=058A? <DISC ACK>
20:30:25T WA3WLH-15>WA3WLH-7 Port=1 <RR R F R3>
Any clue why the DISC REQ from the hub?
73 de Rich WA3WLH
