Subj : Re: Weekly nodelist report on noteworthy changes (335)
To   : All
From : Wilfred van Velzen
Date : Fri Dec 29 2023 13:01:05

Hi All,

On 2023-12-22 13:10:28, I wrote to you:

 WvV> Current status of net 128:

 WvV> 1:128/0 cscnet1.net:24554       47.49.255.5     Ok.
 WvV> 1:128/1 cscnet1.net:24554       47.49.255.5     Ok.
 WvV> 1:128/73        opinsane.noip.me:24554  102.129.145.77  Error: Connection
 WvV> refused
 WvV> 1:128/187       cscnet1.net:24554       47.49.255.5     Ok.
 WvV> 1:128/252       bbs.lamersfam.com:24554 70.171.253.181  Error: Connection
 WvV> timed out
 WvV> 1:128/253       barlows1.net:24554      47.49.255.2     Error: Connection
 WvV> timed out
 WvV> 1:128/255       sb-discovery.com:24554  47.49.255.9     Error: Connection
 WvV> refused
 WvV> 1:128/256       cscnetgw.net:24554      47.49.255.16    No such AKA.
 WvV> 1:128/257       bbs.castlerockbbs.com:24554     72.24.172.12    Error: No
 WvV> route to host
 WvV> 1:128/258       idomain.synchro.net:24554       142.171.158.145 Ok.
 WvV> 1:128/261       vintagebbsing.com:24554 47.49.255.14    Ok.
 WvV> 1:128/262       beta.sb-discovery.com:24554     47.49.255.12    Error:
 WvV> Connection timed out

There is one improvement in net 128 this week:

1:128/73  opinsane.noip.me:24554  207.225.26.65 Ok.

 WvV> Nodes 260 and 263 aren't tested by the script because of the nodelist
 WvV> errors, but checking the binkp port by hand with telnet reveals that 260 is
 WvV> up and 263 is down.

The nodelist errors aren't fixed, but a manual check shows node 263 is now also online, with Mystic/1.12A46. But presents the wrong AKA: 1:305/2@fidonet


Bye, Wilfred.

--- FMail-lnx64 2.2.1.0
 * Origin: NPC Station (2:280/464)

.