How to setup a Mutli-Node Mystic BBS?

[terry.l...@gmail.com]

I'm assuming adding additional nodes doesn't require additional hardware (Like the old days)? After running mystic -cfg, I see under Server -> Server Options -> Max BBS Nodes = 3. My guess would be 3 instances or processes of Mystic are running for users to interact with?

However, this doesn't appear to be automatic? In the Mystic documentation (Mystic BBS Sysop Documentation - By James Coyle), it mentions under the section "Installing Multiple Nodes of Mystic BBS", "Load EACH node you wish to setup in local mode" (Example mystic -N2 -L).

Is anyone doing this? For those who with 4 or 5 nodes, I'm assuming they have a startup script created to perform this operation? Anyone care to share?

There is a lot of old documentation out there and I'm just trying to figure out what is current (For version 1.12a36 or newer).

Thanks,
Terry

[Static]

On 12/20/17, terry.l...@gmail.com said the following...

te> However, this doesn't appear to be automatic? In the Mystic documentation
te> (Mystic BBS Sysop Documentation - By James Coyle), it mentions under the
te> section "Installing Multiple Nodes of Mystic BBS", "Load EACH node you
te> wish to setup in local mode" (
te> Example mystic -N2 -L).

You can just set the number of nodes you want in the server. It will spawn
them and create any necessary temp files as people connect.

[g00r00]

te> However, this doesn't appear to be automatic? In the Mystic documentation
te> (Mystic BBS Sysop Documentation - By James Coyle), it mentions under the
te> section "Installing Multiple Nodes of Mystic BBS", "Load EACH node you
te> wish to setup in local mode" (
te> Example mystic -N2 -L).

If you see that then you are reading the documentation from the DOS version
from the mid 1990s.

For documentation the wiki and YouTube (search MysticGuy) are good places to
go as well as asking here of course. fsxNet is where most of the action is
regarding Mystic discussion these days but there are people all over who will
try to help you.

Here is some informatino from the Wiki:

Q: How do I configure the number of nodes Mystic will accept?
A: The first step is to set the "Max BBS Nodes" in your System Configuration >
Servers > General Options section in the configuration. This defines the
max number of nodes you will allow at one time. However, there is slightly
more to consider.

BBS Nodes can be spawned by any number of built in Mystic servers, or also
from external sources for things such as dial-up modems, local logins from
the console, etc. The max BBS nodes is a limit to the sum of all possible
ways Mystic can accept BBS node connections.

In the Servers > Configure servers configuration you will see options to
modify or create TELNET, RLogin, and SSH servers. You can create any number
of these servers on any ports, and each one can have a limit of the number of
connections they will accept. If you want to have 20 nodes but 3 of them
available by SSH and 17 by Telnet, you would configure a Telnet server for
17 max connections and a SSH server for 3 max connections and set your Max
BBS nodes to 20 or more.

The settings do not have to add up to Max BBS nodes. If all BBS nodes are
busy when a user connects, the user will simply be displayed a message
informing them that all nodes are busy. This means you can setup a 20 node
BBS and then set up 3 different Telnet server and a SSH server all of which
each allow 20 connections, and Mystic will allow any combination to fill up
the BBS nodes.

[Terry Rankin]

Thank you! The documentation I was referring to was written in 2014 and comes with the latest Mystic download 1.12a36 (/mystic/docs/ folder). So just to clarify, I don't need to execute/load mystic for each node (i.e. mystic -N2 -l) as cut/shown in the section below:

"How to setup Mystic BBS to run Multi-node:

(1) Load Mystic BBS and enter "System Configuration". From there
select "General Settings". Set the "Max # of Nodes" option
to the maximum number of incoming nodes that you plan on
loading. Exit Mystic BBS.

(2) Load EACH node you wish to setup in local mode. This can be
done by running Mystic BBS with the -Nx and -L command lines.
For example, the command line for loading node 2 in local mode
would be: "-N2 -L".

Enter "System Configuration" and select "Modem/Node Settings".
You will need to setup each node so it finds the correct modem.

You're done! That's it. The only difference in your setup will be
that you MUST specify the node number now when loading your BBS. This
is done with the "-N" command line option.

So loading your BBS would work something like this:

(1) Create new DOS task.
(2) Load Mystic BBS with -Nx option.
(3) Repeat for each node."

Thanks again,
Terry

[g00r00]

TR> Thank you! The documentation I was referring to was written in 2014 and
TR> comes with the latest Mystic download 1.12a36 (/mystic/docs/ folder). So

That document starts off with telling you it was more than 10 years old when
1.10 was released (several years ago), which dates it back to the late
90s/early 2000s or so. :)

The majority of things are documented with videos on YouTube (MysticGuy) or
the Wiki at mysticbbs.com. There is still a lot that isn't recent because of
the speed that things tend to change in Mystic, but a few of us are working
on it when we can.

fsxNet has the largest Mystic community so it is a great resources as well
for asking questions.

[Terry Rankin]

Thank you so much for your help! Absolutely will be checking out fsxNet.

[amigaco...@gmail.com]

Well I have a problem now while didn't had in the past.
I run it on an RPi0 with 15 nodes.
The problem is that every new user gets an error message that he can't login than one node at a time.
When I log I see my self twice in there :-/

[Phil Taylor]

On 30 Sep 2019, amigaco...@gmail.com said the following...

am> Well I have a problem now while didn't had in the past.
am> I run it on an RPi0 with 15 nodes.
am> The problem is that every new user gets an error message that he can't
am> login than one node at a time.
am> When I log I see my self twice in there :-/
am>
am> --- SoupGate-Win32 v1.05
am> * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway

Check your telnet server settings.