Hello,

I'm following Avon's video tutorial on setting up fsxnet on the Rasp. Pi. I set up the echomail information as given and have fsxnet as message group
3. I then set up message area 5 with the appropriate permissions to connect
it with group 3.

Even after exiting the CFG, stopping the MIS service and restarting it,
message group 3 doesn't appear on the join list. I double-checked all the
node settings, passwords, etc. and they match the tutorial.

What am I missing?

Thanks,
Chris aka Lord Gareth

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

Pi. I set up the echomail information as given and have fsxnet as
message group 3. I then set up message area 5 with the appropriate permissions to connect it with group 3.

Found those tutorials great & worked great under windows. Maybe permissions
is the issue. g5s20 - group 5 security 20 for permission.

Even after exiting the CFG, stopping the MIS service and restarting it, message group 3 doesn't appear on the join list. I double-checked all
the node settings, passwords, etc. and they match the tutorial.

Have found many times TYPOS being my main issues at times LOL

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The Unknown Realm - turealm.no-ip.org:3023 (21:3/111)

Hi Grim Reaper,

Thank you for the advice. So the fsxnet message group is group 3. The
fsxnet Chat, Testing, + More... message base is message base 5.

I tried what you said for settings in Message Base 5 and tried several permission combinations:
g3s10
g5s10
s10g3
s10g5

The message group itself has the Access set to 10. No matter what I try, I
go to my message menu, select Join and message group 3 doesn't appear.

Do I need to add fsxnet to an echomail group as well? If so, what do the permissions look like in a message base to link it to an echomail group vs. a message group? I'm thinking the message group setup should work but, saw the echomail group setting and figured I'd ask.

-Lord Gareth

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

112
I did end up getting this working. It turned out the group had a permission
of 10 instead of s10 which caused the problem.

As you can see, I now have my own fsxNet node. Thanks again for your help!

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: Mirrored Lands BBS (21:4/174)

permission of 10 instead of s10 which caused the problem.

Thats probably why during setup, customization and all that stuff, I left
most security settings blank, minus the GROUP flag setting. Then went back
and started adding them in as i changed settings etc :)

LG> As you can see, I now have my own fsxNet node. Thanks again
for your LG> help!

Welcome about & good to see another active BBS & User :)

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The Unknown Realm - turealm.no-ip.org:3023 (21:3/111)