Got a question for the knowing.. I am running 3 different BBS' here at my house.. I want to form a inhouse message network between all 3 BBS'to share some message bases and file bases.. What all is entailed in that?? I assume I need a nodelist, then just set up like we do any other net?? Where can I find
a nodelist creator that works? Does it matter what zone numbers I use etc? Thanks..

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

Got a question for the knowing.. I am running 3 different BBS' here at my B>house.. I want to form a inhouse message network between all 3 BBS'to share B>some message bases and file bases.. What all is entailed in that?? I assume I B>need a nodelist, then just set up like we do any other net?? Where can I find B>a nodelist creator that works? Does it matter what zone numbers I use etc?

Any application that will let you edit an ASCII text file will work as
that is all node list files are. Personally, under Windows I use the
built in editor that comes with the Windows version of FileCommander and
under OS/2 I sometimes use the built in editor that comes with the OS/2
version of FileCommander or I just use QEdit/2.

---
þ OLXWin 1.00b þ 'Stupidity, if left untreated, is self-correcting' RAH.
* Origin: fsxNet: Omicron Theta * Southaven, MS * winserver.org (21:2/136)

On 08/23/18, Robert Wolfe said the following...

Any application that will let you edit an ASCII text file will work as that is all node list files are. Personally, under Windows I use the built in editor that comes with the Windows version of FileCommander and under OS/2 I sometimes use the built in editor that comes with the OS/2 version of FileCommander or I just use QEdit/2.

Cool thanks for the info.. :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

On 08/23/18, Bucko said the following...

I assume I need a nodelist, then just set up like we do any other net?? Where can I find a nodelist creator that works? Does it matter what zone numbers I use etc? Thanks..

You shouldn't even need a nodelist if you set them up as a host with a couple of points and just crash any new mail to them.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

On 08/23/18, Bucko said the following...

house.. I want to form a inhouse message network between all 3 BBS'to share some message bases and file bases.. What all is entailed in that??

I'm playing with the same setup now - if anything so that I can understand
how it all works (again).

It seems pretty easy - I was working on a plan of having 1 BBS that is the "hub" to the outside world (my .0) and then the others to be points off of
it. I might play with having my own FDN as well - just because I can.

I've just dockerised Mystic for a Pi - so now I can deploy and play with Mystic's settings on another BBS without affecting my main BBS... I plan on sharing that container with instructions so that others can spawn a Pi MysticBBS by simply "docker run ..." ;)

...deon

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Chinwag (21:2/116)

On 08-23-18 11:00, Bucko wrote to All <=-

Got a question for the knowing.. I am running 3 different BBS' here at
my house.. I want to form a inhouse message network between all 3
BBS'to share some message bases and file bases.. What all is entailed
in that?? I assume I need a nodelist, then just set up like we do any other net?? Where can I find a nodelist creator that works? Does it
matter what zone numbers I use etc? Thanks..

Basically, it's just like setting up an "othernet", except you're not making it public. Choose an unused zone number, a 4 digit one would be good. You shouldn't need to create a nodelist, simply configure each link in your mailers, so the BBSs know how to contact each other.

So in summary:

1. Choose a zone number and FTN domain (e.g. Zone 1234@localnet)
2. Assign BBS addresses (say 1234:1/1, 1234:1/2, 1234:1/3)
3. Configure links in your mailers.
4. Setup file and message echoes.

Should work a treat. :)

If you _want_ to use a nodelist (again, I see no need for your situation), you can use MakeNL, which is available for all platforms. I run it on both Windows and Pi. It's waaaaaaaaaaaay overkill for your application (and mine!), but I can help you use it for your simple case, which is the same as VKRadio, except you only have 3 nodes, instead of my 30 or so. :)


... Blessed are the meek for they shall inherit the crap.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

On 08-23-18 17:15, Static wrote to Bucko <=-

You shouldn't even need a nodelist if you set them up as a host with a couple of points and just crash any new mail to them.

Even if you setup a dedicated zone/net for them, the above applies, all links can be configured manually and you can crash mail through.


... Computers also eliminate spare time.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

On 08/23/18, Static said the following...

You shouldn't even need a nodelist if you set them up as a host with a couple of points and just crash any new mail to them.

I'm already doing the point system with a couple of nets on 2 of the boards,
so I can just make up node numbers, and then crash them to points? That works for me. Hmmm that sounds too easy! LOL

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

On 08/23/18, Deon George said the following...

It seems pretty easy - I was working on a plan of having 1 BBS that is
the "hub" to the outside world (my .0) and then the others to be points off of it. I might play with having my own FDN as well - just because I can.

That is sort of what I am looking at, my Mystic board will be the hub and the other 2 boards will be points. I think that is the easiest way.. I'll just
make up a node address set the Mystic up as a hub and point the other 2 off
of the hub so all 3 boards can share local message bases... Hmmm like I said
in another post it sounds too easy! LOL

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

On 08/24/18, Vk3jed said the following...

On 08-23-18 11:00, Bucko wrote to All <=-

Basically, it's just like setting up an "othernet", except you're not making it public. Choose an unused zone number, a 4 digit one would be good. You shouldn't need to create a nodelist, simply configure each
link in your mailers, so the BBSs know how to contact each other.

So in summary:

1. Choose a zone number and FTN domain (e.g. Zone 1234@localnet)
2. Assign BBS addresses (say 1234:1/1, 1234:1/2, 1234:1/3)
3. Configure links in your mailers.
4. Setup file and message echoes.

Should work a treat. :)

That works for me... Guess I have something to do... :) Thanks everyone for
the help..

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

On 08/23/18, Deon George pondered and said...

I've just dockerised Mystic for a Pi - so now I can deploy and play with Mystic's settings on another BBS without affecting my main BBS... I plan on sharing that container with instructions so that others can spawn a Pi MysticBBS by simply "docker run ..." ;)

That sounds good, if I created a turnkey version of Mystic Pi 1.12 A39 for fsxNet would you be happy to create the docker packing etc. (sorry not really across who all that works) and I could then host those files on bbs.nz ?

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 08/23/18, Bucko pondered and said...

That is sort of what I am looking at, my Mystic board will be the hub
and the other 2 boards will be points. I think that is the easiest way.. I'll just make up a node address set the Mystic up as a hub and point
the other 2 off of the hub so all 3 boards can share local message bases... Hmmm like I said in another post it sounds too easy! LOL

Point addresses using a network naming schema already in place would work nicely for you.

* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

So you would run your main systems as you do as 21:4/131 and set it to feed your other 2-3 systems as points... 4/131.1 4/131.2 etc.

Thing to remember is your HUB will be the key resource to your point systems and handle routing any netmail destined for your points... and you set your points to route netmail to your 4/113 HUB :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 08/24/18, Avon said the following...

That sounds good, if I created a turnkey version of Mystic Pi 1.12 A39
for fsxNet would you be happy to create the docker packing etc. (sorry
not really across who all that works) and I could then host those files
on bbs.nz ?

Sure - happy to...

What's in your "turnkey"? Ive got a "basic" install of Mystic installed working, and echomail/netmail flowing, etc. I've included Spell and criptlib
- and I'm calling this my "base" image. Due to the way Mystic is "installed", there is a "manual" element to this build. I know development of Mystic has stalled, but when it gets up and running again, I would like to provide some input - I want to get to a point where CI can build the base.

Then, from the base I plan to add "mods" - ie: games, improvements, etc.
Maybe we could work on this and be your turnkey. (I'll take your insight,
I've been playing with Mystic for a week - and your you tube videos helped a lot.)

Anybody should be able to take my "base" or "full featured" container and extend it if they so desire :)

As a background, Docker containers can be installed two ways:
* Pull from a registry (I have a registry) - and my container will be automtically put in it using CI
* Exported -> Sent to new Host -> Imported. So I could hatch the container
and sent it through fileechos (with instructions) and then folks can import
it that way. (Although via a registry is easier :)

...deo

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Chinwag (21:2/116)

On 08/24/18, Deon George pondered and said...

Sure - happy to...

Cool thanks :)

What's in your "turnkey"? Ive got a "basic" install of Mystic installed working, and echomail/netmail flowing, etc. I've included Spell and criptlib - and I'm calling this my "base" image. Due to the way Mystic

It's been a while since I set one up but there's a more dated Raspberry Pi version up on the fsxNet page at bbs.nz and (from memory) I just tried to set things up as per the videos with the key ini files in place and configuring
the echos etc.. along with setting the default /999 AKA and polling to
21:1/100

I have on my to-do list the plan of setting something like this for 1.12 A39
up as the last effort was a few alphas ago :)

is "installed", there is a "manual" element to this build. I know development of Mystic has stalled, but when it gets up and running
again, I would like to provide some input - I want to get to a point
where CI can build the base.

I wouldn't say stalled but yep the author is taking a break from the project. Rest assured when he opts to pick it up again there's often a flurry of development that takes place. The FSX_MYS echo has been a good place to contribute ideas during past bursts of activity..

Then, from the base I plan to add "mods" - ie: games, improvements, etc. Maybe we could work on this and be your turnkey. (I'll take your insight, I've been playing with Mystic for a week - and your you tube videos
helped a lot.)

I would suggest that a basic install turnkey should be just that so as to not overwhelm anyone but perhaps you may want to create a more 'advanced' model
of your docker image also?? I do think for many some of the fun is in setting up stuff so it's always a balance between helping by providing turnkeys etc. and letting folks doing their thing :)

As a background, Docker containers can be installed two ways:
* Pull from a registry (I have a registry) - and my container will be automtically put in it using CI
* Exported -> Sent to new Host -> Imported. So I could hatch the
container and sent it through fileechos (with instructions) and then
folks can import it that way. (Although via a registry is easier :)

So could I run a pull command like Git on my Pi and set your image up?

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 08/24/18, Avon said the following...

I would suggest that a basic install turnkey should be just that so as
to not overwhelm anyone but perhaps you may want to create a more 'advanced' model of your docker image also?? I do think for many some of the fun is in setting up stuff so it's always a balance between helping
by providing turnkeys etc. and letting folks doing their thing :)

I agree. The value that docker plays is that one time "installation" is done
by the "vendor" (or in my case the nominee ;), and users then just start using the app (which includes configuring it for the first time).

So I do plan to have 2 images - the "base" and the "all you can eat
(according to deon)". New users can pull either image depending on what
feature set the want to have. Advanced users who like to customise - can pull either image and "overwrite" or "extend" as appropriate.

So could I run a pull command like Git on my Pi and set your image up?

Yes you will be able to. I'm justing writing and testing the CI now on the "base" image - and when it passes it will be available here (might be a
couple of days - depends when I can hide from the wife and kids):

registry.leenooks.net/leenooks/mysticbbs:1.12a39-armv7l

The build and code will be available at https://dev.leenooks.net/leenooks/mysticbbs

I plan on creating an Linux x86_64 image (eventually) - it should autobuild too.

...deon

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Chinwag (21:2/116)

On 08/24/18, Avon said the following...

Point addresses using a network naming schema already in place would work nicely for you.

* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/13

So you would run your main systems as you do as 21:4/131 and set it to feed your other 2-3 systems as points... 4/131.1 4/131.2 etc.

Thing to remember is your HUB will be the key resource to your point systems and handle routing any netmail destined for your points... and
you set your points to route netmail to your 4/113 HUB :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

This is what I am already doing with fsx, Fido, and RetroNet. I am pointing them on my SynchroNet board. What I am going to do is setup a "inhouse"
network just my 3 possibly 4 boards. My Mystic board being the hub and the others as points or their own addresses, so my address might be 1000:1/1 for
my mystic, and either pointing them, or just giving them their own address 1000:1/2 and 1/3 etc. Either one would work as far as I can tell. We'll see though.. Thanks for the advice and help..

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

Got a question for the knowing.. I am running 3 different BBS' here at
my house.. I want to form a inhouse message network between all 3
BBS'to share some message bases and file bases.. What all is entailed
in that?? I assume I need a nodelist, then just set up like we do any other net?? Where can I find a nodelist creator that works? Does it
matter what zone numbers I use etc? Thanks..

I do that now between three boards, but I do not even use a nodelist. None
of the software I run really requires it. Also, it does not matter what
zone you choose so long as it is not one used by a network that you are
already a member of.

Since one of my boards is Synchronet, I am using QWK networking to move the messages between it and one board. The other does not have QWK networking support (yet) so that is where ftn comes in.



... Computer Hacker wanted. Must have own axe.
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636 * SSH:2122 (21:4/134)

On 08-23-18 20:23, Bucko wrote to Vk3jed <=-

That works for me... Guess I have something to do... :) Thanks everyone for the help..

Enjoy tinkering. :)


... If a bear is chasing you please don't run this way.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

On 08/23/18, Blue White said the following...

I do that now between three boards, but I do not even use a nodelist. None of the software I run really requires it. Also, it does not matter what zone you choose so long as it is not one used by a network that you are already a member of.

Since one of my boards is Synchronet, I am using QWK networking to move the messages between it and one board. The other does not have QWK networking support (yet) so that is where ftn comes in.

Cool.. Thanks for the info.. I will get it going.. :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

This is what I am already doing with fsx, Fido, and RetroNet. I am pointing them on my SynchroNet board. What I am going to do is setup a "inhouse" network just my 3 possibly 4 boards. My Mystic board being the hub and the others as points or their own addresses, so my address might be 1000:1/1 for my mystic, and either pointing them, or just giving them their own address 1000:1/2 and 1/3 etc. Either one would work as far as
I can tell. We'll see though.. Thanks for the advice and help..

Why not just setup a qwknetwork? - its really easy , you just have to peek inside your qwk packet and look at control.dat file to know the area numbers

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Mike's Mansion - Portland, OR (21:2/145)

So I thought I'd share for anybody who is interested (and for anybody new to Mystic), that I have put together some Docker containers so that Mystic can
run under Docker.

The containers are available for armv7l (Raspberry Pi) and x86_64.

I've tested them and they appear to work fine - and while my Mystic is not running under these containers (yet) [it is running in Docker - 1 node swarm
on the Pi and its been running well for a week now]. I plan to move it under these built containers this weekend (if I can get some time).

The containers will enable a first time Mystic user to get up and running quickly. It will also help when a new version of Mystic comes available -
while I'll need to understand an "upgrade" procedure and I may need to allow for any special instructions, what Docker provides is a backout option if things go pear shaped. Docker is also great if you ever want to move your app to a new host - you just move the data and load the container on the new host and things just work :) (Netmail me if you need any help.)

My "base" container (for each architecture) has Mystic, Cryptlib (for SSH)
and Hunspell (Spell Checker) all installed and working. I'm working on an "extas" container (for each architecture) that will have mods pre-installed (like games, blam, etc). Happy to receive ideas on what should be included.

If you have docker running, you can:

docker pull registry.leenooks.net/leenooks/mysticbbs:1.12a39-<ARCH>

where ARCH can be armv7l (PI) or x86_64.

If you need help getting docker running, you can ask me too - it is pretty easy...

...deon

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Chinwag (21:2/116)

On 08/25/18, michael2 said the following...

Why not just setup a qwknetwork? - its really easy , you just have to
peek inside your qwk packet and look at control.dat file to know the
area numbers

Haven't played with QKW Networking yet.. I got this going now so I am good as gold for now.. LOL :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)