Subj : Node list issue.
To   : All
From : claw
Date : Fri Apr 29 2022 02:54 pm

I haven't had time to address this issue I discovered with the node list and really don't want to trouble Avon anymore.  He has been awesome and since he has bigger fish to fry, I'm hoping I can get some ideas here.  When I allow my BBS to pull the node list in to search it will only ready and access nodes as they are in the list.  The thing I noticed is that the setting in Mystic -cfg shows the nodes as not active once this runs.  Then all the data comes from the node list.  I get why this would be the thing to do allows the network admin to control changes without the need to setup the BBS each time. Pretty genius actually. Since the node list has a different address than the one assigned to me it prevents me from polling afterwards.  Anyone come across this before and have a solution so I can have the node list yet keep the settings in Mystic -cfg going?  

|23|04Dr|16|12Claw
|16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04)
|10Standard Ports for SSH/Telnet Web/HTTP://|14Noverdu.com:808
|22|01fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
 * Origin: Noverdu BBS (21:1/210)

.