Hello Deon!

Your nodelist entries for 21:3/0 and 21:3/100 are showing an (incomplete) hostname of n3.z21 ... It should be n3.z21.fsxnet.nz methinks...

Andrew

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Phoenix BBS * phoenix.bnbbbs.net (21:4/105)

Re: Correction needed to the FsxNet nodelist
By: Andrew Leary to Deon George on Thu Mar 13 2025 06:17 am

Howdy,

Your nodelist entries for 21:3/0 and 21:3/100 are showing an (incomplete) hostname of n3.z21 ... It should be n3.z21.fsxnet.nz methinks...

Hmm... that is odd. I've obviously messed something up in clrghouz.

Thanks for letting me know.


...ëîåï
--- SBBSecho 3.23-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Correction needed to the FsxNet nodelist
By: deon to Andrew Leary on Fri Mar 14 2025 07:22 pm

Howdy,

Your nodelist entries for 21:3/0 and 21:3/100 are showing an (incomplete) hostname of n3.z21 ... It should be n3.z21.fsxnet.nz methinks...

Hmm... that is odd. I've obviously messed something up in clrghouz.

So I found this one and fixed it - the next segment sent to Paul for the nodelist should now include the complete hostname.

I also allowed for the segment submission to have a custom name (for othernets that want their own specific named makenl segment), so that should be there now too. If they dont specicify a custom name, then the segments will be named z<ZONE_ID>n<ROLE_ID>.ddd, where ZONE_ID is the zone number, ROLE_ID is their region or net number.


...ëîåï
--- SBBSecho 3.23-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)