Subj : Weekly nodelist report on noteworthy changes (328)
To   : All
From : Wilfred van Velzen
Date : Fri Nov 24 2023 12:24:53


Hi All,

New node in net 396:
,22,Efectolinux,Converse_TX,Antonio_Rivera,-Unpublished-,300,CM,XA,INA:bbs.efectolinux.com,ITN,IBN
Connect with BinkIT/2.41,JSBinkP/4,sbbs3.20a/Linux
On the ITN/telnet port there is a synchronet bbs, I don't know about a mailer.

In net 343 the host lost the CM IFT and INA:net2343.fidonet.cat flags, and gained the MO IFC U,Tce,NC flags.
On the old INA host name and binkp port there is a BBBS/Li6 v4.10 responding with these aka's: 2:343/107 2:343/0 2:343/100 2:343/200 2:343/300 2:343/400. Only nodes 0 and 107 are in the nodelist, and removing the INA must be a mistake?
On the IFC port 60179 there is a connection refused. On the ITN port there is a login prompt for a bbs.

Node 107 also has the MO flag added, and the IFT flag changed to IFC. It's the same system as /0, so no further testing is done.

Node 120 has it's host name changed to: bbs.eona.cat. There is a timeout on the resolved IPv6 address. There is a connect with Mystic/1.12A49 on the IPv4 address.

Node 136 by the same sysop as node 120 is new:
,136,EONA_BBS,Barcelona,Noemi_Abril,-Unpublished-,300,CM,IBN:24556,IFC,ITN,INA:bbs.eona.cat
2:343/136       bbs.eona.cat:24556      2a0c:5a87:6009:eb00::1  Error: Connection timed out
2:343/136       bbs.eona.cat:24556      86.127.242.201  Ok.
On the IFC and ITN ports there is a timeout for both IPv6 and IPv4.


Regards, Wilfred

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

.