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)

Hello claw!

On 29 Apr 2022, claw said the following...

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

I haven't come across this, but you might want to check if the Configuration --> Message Base Settings --> Force NL Match setting makes a difference (I have mine set to No).

Best regards
Zip

--- Mystic BBS v1.12 A48 2022/04/03 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

I haven't come across this, but you might want to check if the

Message Base Settings --> Force NL Match setting makes a difference (I mine set to No).

Configuration

Its set to no. :(. I might just have to manually put the node lists in each time and make sure it doesn't turn the setting to inactive. I'll have to see if I can post in arkanet to g00r00 as a bug which I'm sure technically isn't a bug but he might have a way to prevent it from turning off each time so the node list can be part of nightly maint.

If anyone else has any suggestions let me know. Strange how its only me with this problem.

|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)

On 4/30/2022 11:18 AM, Claw wrote to Zip:

Its set to no. :(. I might just have to manually put the node lists in each time and make sure it doesn't turn the setting to inactive. I'll have to see if
I can post in arkanet to g00r00 as a bug which I'm sure technically isn't a bug
but he might have a way to prevent it from turning off each time so the node list can be part of nightly maint.

If anyone else has any suggestions let me know. Strange how its only me with
this problem.

Take a look at your mergenodes.ini located in your mystic root directory The section for
the nodelists looks like this on mine:

nodefile=c:\nodelist\hobbynet\HOBBYNET
nodefile=c:\nodelist\fido\NODELIST
nodefile=c:\nodelist\fsxnet\FSXNET
nodefile=c:\nodelist\bluesnet\bluesnet

Then, just make sure that your current nodelists goes into each of the folders that you
define.

Hope this helps.

Mike Dippel

--- Platinum Xpress/Win/WINServer v7.0
* Origin: The Hobby Line! Internet - hobbylinebbs.com (21:4/176)

Take a look at your mergenodes.ini located in your mystic root directory The section for
the nodelists looks like this on mine:

nodefile=c:\nodelist\hobbynet\HOBBYNET
nodefile=c:\nodelist\fido\NODELIST
nodefile=c:\nodelist\fsxnet\FSXNET
nodefile=c:\nodelist\bluesnet\bluesnet

This issue isn't that it can't find it. The issue is that once it does and loads it (which it does correctly) then it ticks the active status of the node to inactive and start using the info from the node list. The issue is that I'm setup to connect to 21:1/100 at agency.bbs.nz and in the node list that address goes to fsx1.network.something or other. Either way its not the right address. Avon has assured me its the same computer but once its starting to pull from there it can't authenticate.

|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)

Hello claw!

On 30 Apr 2022, claw said the following...

The issue is that I'm setup to connect to 21:1/100 at agency.bbs.nz and
in the node list that address goes to fsx1.network.something or other. Either way its not the right address. Avon has assured me its the same computer but once its starting to pull from there it can't authenticate.

Maybe it tries to use STARTTLS to secure the connection, and doesn't like the certificate from Avon's system (self-signed with CN "localhost" when I check with openssl s_client, at least for ports 24553 and 24556, although these are not STARTTLS but "direct" SSL/TLS), and decides to deactivate the node because of that?

What is "Server Type" set to for 21:1/100 in the Mystic config?

Best regards
Zip

--- Mystic BBS v1.12 A48 2022/04/03 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Maybe it tries to use STARTTLS to secure the connection, and doesn't
like the certificate from Avon's system (self-signed with CN "localhost" when I check with openssl s_client, at least for ports 24553 and 24556, although these are not STARTTLS but "direct" SSL/TLS), and decides to deactivate the node because of that?

blinkp . thats defiantly an interesting take. any way to test this theory?

|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)

Hello claw!

On 02 May 2022, claw said the following...

blinkp . thats defiantly an interesting take. any way to test this theory?

Check to see if there is some setting for not using SSL/TLS/STARTTLS -- hopefully that could do the trick. =)

Best regards
Zip

--- Mystic BBS v1.12 A48 2022/04/03 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Check to see if there is some setting for not using SSL/TLS/STARTTLS -- hopefully that could do the trick. =)

checked out the setting in the config and do not see anything for SSL/TLS/STARTTLS. The weird thing about it is Avon says they both point to the same system. If the same system has more than one address for the same network, can that cause issues? Is it possible this could be fixed by having the node list report the addresses correctly? I don't know much about fido technology so I'm actually asking these questions to learn about it. I opend one up and looked at it. Not human readable without a key.

|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)

Hello claw!

On 02 May 2022, claw said the following...

SSL/TLS/STARTTLS. The weird thing about it is Avon says they both point to the same system. If the same system has more than one address for
the same network, can that cause issues? Is it possible this could be fixed by having the node list report the addresses correctly? I don't

The details in the echomail node config will (AFAIK) be those that are used during polling/sending. The nodelist contents will be used for lookups when composing mail (or when launching the nodelist browser to search for systems). But Mystic appears to be doing something more than that for some reason. I guess the only one who really knows whould be g00r00...

You might want to try to get hold of him in the MYSTIC FidoNet echo, however he hasn't written there for a while (and I haven't received any replies to my recent netmails either), so he might be busy with other things at the moment.

Best regards
Zip

--- Mystic BBS v1.12 A48 2022/04/03 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

The details in the echomail node config will (AFAIK) be those that are used during polling/sending. The nodelist contents will be used for lookups when composing mail (or when launching the nodelist browser to search for systems). But Mystic appears to be doing something more than that for some reason. I guess the only one who really knows whould be g00r00...

Understood. I really appreciate your assistance. I have seen him respond on zer0net not too long ago I will try there.

|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)