Subj : Weekly nodelist report on noteworthy changes (069)
To   : Wilfred van Velzen
From : Michiel van der Vlist
Date : Fri Mar 10 2023 11:30:06

Hello Wilfred,

On Friday March 10 2023 09:46, you wrote to All:

 WV> New node in net 229:
 WV> ,110,The_Outworld_BBS,Winnipeg_MB,Lloyd_Hannesson,-Unpublished-,300,CM
 WV> ,INA:outworldbbs.com,IBN outworldbbs.com: Name or service not known

Ditto.

 WV> In net 275:
 WV> ,98,twixed,Fairfax_VA,Anton_Mikhaylov,-Unpublished-,300,XX,INA:bbs.twi
 WV> xed.net,IBN:24544 The IBN port number was added. On this port I get a
 WV> connection refused. On the default binkp port Mystic/1.12A42 answers.

My guess is that the 24544 is a typo and that 24554 was meant. Either way it is a failure of the NC275. They has not checked connectivity on port 24544 or they entered the default port 24554 that should not be there.

The entry for 275/100:

,100,Shenks_Express,Virginia_Beach_VA,Carol_Shenkenberger,-Unpublished-,
300,XX,CM,INA:shenks.synchro.net,IBN:shenks.dyndns.org,ITN:24

is also wrong. From FTS-5001:

   INA           This flag sets a default server address used
                 for any Internet Protocol Flag that does not
                 specify its own.


The INA flag does not apply to binkp because the IBN flags specifies its own server address. There are no other protocol flags, so the INA flag has no target. If the objective was to specify an alternative host name for the binkp protocol, using a second IBN flag is the right way:

...300,XX,CM,IBN:shenks.synchro.net,IBN:shenks.dyndns.org,ITN:24

Same error for 275/0.

Sidenote: the NC275 is an FTSC candidate. :(

 WV> And a new node:
 WV> ,103,Westwood_bbs,King_George_VA,Mike_Newkirk,-Unpublished-,300,XX,CM,
 WV> INA:westwoodbbs.net,IBN Connect with binkd/1.1a-115/Linux

Check.

 WV> Node 2:5058/0 /104 has the IFC flag added. Connect with qico v0.59.1
 WV> on the IFC default port.

Not checked.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: Nodelist Police Station (2:280/5555)

.