Subj : Weekly nodelist report on noteworthy changes (337)
To   : All
From : Nodelist Police Commissioner
Date : Fri Dec 03 2021 22:10:08


Hi All,

In net 240, a new hub sysop:
Hub,4000,Temp_Nordnetz_Hub,Hamburg,Torsten_Bamberg,49-40-98670308,9600,CM,XA,V34,VFC,H16,IBN,INA:datenbahn.dd-dns.de,U,ENC,CDP
? 03 Dec 13:28:22 [9874] called 2:240/4000@fidonet, but remote has no such AKA

The 4 nodes of Olav_Rogall who were on Pvt before under this hub, are now on Hold.
The other 3 nodes under this Hub:
,4030,HOLO-BBS_I,Hohenlockstedt,Kuno_Kunhardt,49-4826-3941,9600,CM,XA,MO,V34,IBN,INA:holo-bbs.dd-dns.de
,4031,HOLO-BBS_II_*ISDN*,Hohenlockstedt,Kuno_Kunhardt,49-4826-850123,300,CM,XA,MO,V110H,X75,IBN,INA:holo-bbs.dd-dns.de
,4032,HOLO-BBS_III_*ISDN*,Hohenlockstedt,Kuno_Kunhardt,49-4826-850122,300,CM,XA,MO,V110H,X75,IBN,INA:holo-bbs.dd-dns.de
Have the IBN and INA flag added, but I get a "No route to host" response when trying to connect.

New node in net 218:
,602,The_Wastelands_II_BBS,Copperopolis_CA,Donald_Price,-Unpublished-,300,CM,XX,INA:wastelands-bbs.net,IVN
2nd Node of this sysop. IVN is not a defined flag. On the IBN port only the first nodes AKA is presented. On the IVM (not N) port, a BBS answers. But I don't
know how to verify the Vmodem protocol...

New node in net 640:
,1114,Insane_Asylum,Racine_WI,Jim_Kulwicki,-Unpublished-,300,CM,INA:asylum.erb.pw,IBN,ITN
Connect with Mystic/1.12A47.

Regards, NPC

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)

.