Subj : Re: Weekly nodelist report on noteworthy changes (148)
To   : Michiel van der Vlist
From : Nodelist Police Commissioner
Date : Sun May 30 2021 11:40:19

Hello Michiel,

On 2021-05-30 09:20:48, you wrote to me:

 NC>> New node in net 341:
 NC>> ,234,cyberiada,Sant_Joan_d'Alacant,Carlos_Navarro,-Unpublished-,300,M
 NC>> O ,TVO,PING,IBN:fido.cyberiada.org Connect with binkd/1.0.4/Win32.
 NC>> Pong arrives fast.

 MvdV> Hij was active as a point before and PINGed already as a point.

That doesn't automatically mean his new node would also PING. Hence the test... ;)

 NC>> More BEER flags :-(
 NC>> Host,5003,Komi_Net,Vorkuta,Den_Gusev,-Unpublished-,300,CM,BEER:or_not_
 NC>> 2_beer,IBN,INA:fido.vorkuta.net ,17,Virtual_Node,Vorkuta,Den_Gusev,-Un
 NC>> published-,300,CM,BEER:Kozel_Dark,IBN,INA:fido.vorkuta.net

 MvdV> To be expected. Is here an exit strategy for this nonsense?

I'm afraid we'll see more, and they will remain for years, unless the ZC doesn't allow them anymore...

 NC>> Changed to none default BINKP port:
 NC>> Host,371,NC-Hungary,Budapest_HU,Daniel_Path,-Unpublished-,300,CM,XA,IB
 NC>> N:24555,ITN:1212,INA:bbs.studio64.hu Connect with binkd/1.1a-99/Linux.
 NC>> On the default port nothing respondes... So why? And the INA should be
 NC>> in front of the IBN and ITN flags.

 MvdV> I can confirm the change of port. No idea why.

He told me his regular node is on that port. (But his node has hardware problems, so is often offline)

 NC>> The typo in the hostname for node 4:920/69 has been fixed. The node
 NC>> is still on Hold waiting for a static IP number which has been
 NC>> requested at the ISP.

 MvdV> A static IP is not needed for Fidonet, so I wonder why.

I don't know what his current problem is (maybe CGNAT). But the static IP would fix it...

Regards, NPC.

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

.