What would cause the message "Lost Carrier" when trying to run a door? I'm using Netfoss as my fossil.
Menu Command: c:\mystic\netfoss\nf.bat /N%3 /H%0 c:\mystic\doors\ultslots\ultslots.bat %3 %0
Netfoss loads but i get "Lost Carrier"

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/32)
* Origin: Lunatics Unleashed BBS (21:3/135)

Cozmo wrote to All <=-

What would cause the message "Lost Carrier" when trying to run a door?
I'm using Netfoss as my fossil.

The most common reason would be that the door doesn't use a FOSSIL driver, instead it is attempting to perform it's own hardware I/O over the UART. You would need to use the DOSXTRN option in Mystic and forgo using NetFoss at all.

What's the door that is doing this?

--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

Hi Wall E. Weasel

What would cause the message "Lost Carrier" when trying to run a door?
I'm using Netfoss as my fossil.

The most common reason would be that the door doesn't use a FOSSIL driver, >instead it is attempting to perform it's own hardware I/O over the UART. You >would need to use the DOSXTRN option in Mystic and forgo using NetFoss
at all.

I have been running bre game on my bbs for quite a few year and all of a sudden I haveing trouble with "Lost Carrier" as well I using netfoss, and I noticed this and thought try this DOSXTRN option

I changed to D3 Exec /w DOSXTRN (Win32)
Data c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3

but after the no to enter bre it didnt enter jast came back to menu

so can you or any one help me to get bre working via DOSXTRN option

Thank you

Ian 2nd Choice Core Nz

--- Mystic BBS v1.12 A47 2020/10/31 (Windows/32)
* Origin: 2nd Choice Core : New Zealand (21:1/152)

Sneaky wrote to Wall E. Weasel <=-

I have been running bre game on my bbs for quite a few year and all of
a sudden I haveing trouble with "Lost Carrier" as well I using netfoss, and I noticed this and thought try this DOSXTRN option

What version of NetFoss are you using? There was previously an issue (fixed in 1.23R or sometime around there) which caused a false loss of carrier from time to time. Is BRE getting this situation every time the door loads or just on occasion? The NetFoss bug was pretty intermittent.

I changed to D3 Exec /w DOSXTRN (Win32)
Data c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3

but after the no to enter bre it didnt enter jast came back to menu

D3 is used to shell to 32 bit doors. It doesn't actually load DOSXTRN. You'll need to use DX instead. Also, have you manually installed DOSXTRN.EXE to the Mystic directory and SBBSEXEC.DLL to Windows\System32?

Don't forget to stop loading NetFoss when using this option. DOSXTRN provides its own FOSSIL driver.

To stop using FOSSIL support in BRE you'll need to edit the game's RESOURCE.DAT file and set the FOSSIL option to NO. Depending on your setup you might have more than one of the resource files to edit.

--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

Okay my netfoss version is 1.14R but for same reason it working now
but what to use it without fossil if I can.

Might want to grab NetFoss 1.25 just in case. Don't install it yet unless you want to update it for other reasons.

Yes I notice I put it on D3 instead of DX but done now and downloaded DOSXTRN.rar from mysticbbs\downloads and put Mystic directory and SBBSEXEC.DLL to Windows\System32?

I downloaded this version and tried it. This version of DOSXTRN does not have UART emulation. It does function as a FOSSIL driver, but that's what you're attempting to get rid of.

Be patient for a day. A newer version may somehow appear on your BBS.

okay is is my Data c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3 line

Can you post your BRE.BAT file if it isn't too huge? I don't think it's the problem but let's make sure.

I had a go at but doesn'y work for me, nothing happens after I press
the no of bre on the menu

What do you see in the BBS window for that node when it attempts to run the game?

Do you have a physical serial port at COM1 on the BBS machine? If so, BRE is using that if it runs with the Fossil option set to No. You should see the game running but with no data going to the remote user.

If you don't have one I would expect the NTVDM to barf when BRE attempts to
un.

--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

okay I did all that and YES it is working fine now useing dx and
no fossel

Great!

bre
@echo off
c:
cd \bbs\mystic\mydoors\fsxnet\bre
srdoor
bre planetary
bre
c:
cd \bbs\mystic
mis poll 21:1/10
exit

Now you fix DX, what do I have to do to fix my bat file

It's both the game and batch file that need adjustment. As it's configured now it only reads the DOOR.SYS file from one directory, regardless of which node runs the game. Each node is loading the same SETUP.SR file which (most likely) points to C:\Mystic\Temp1\DOOR.SYS. So if someone runs the game from node 2, it's still looking for door.sys in the node 1 directory. One of two things will happen.

1. If the user on node 1 is running a door, there will be a door.sys file where BRE is expecting it. But it contains the information of the user on node 1, not on node 2. Node 1's info will be used to play the door.

2. If there isn't a user on node 1 running a door, there will be no door.sys where BRE expects to find it. Most doors would simply exit with an error at this point. But BRE has a peculiarity there. Insted of giving an error, BRE will go ahead and run but will do so using the data of the last user to run the door.

You need to make a copy of SETUP.SR for each node, change each node's new configuration file to point at the correct DOOR.SYS file, and change the batch file so each node uses its own config file.

Make a copy of SETUP.SR for each node using the node # as part of the filename.
Manually copy SETUP.SR to NODE1.SR, NODE2.SR, etc for each node you have. Or make friends with the FOR command to do it for you:

for /L %N in (1, 1, 4) do (copy SETUP.SR NODE%N.SR)

Replace the 4 with however many nodes you have set up.

Next, edit each one of those files with a text editor. The first line contains the location and name of the drop file. Make NODE2.SR point to C:\Mystic\Temp2\DOOR.SYS and so on. The FOR command makes this easier here, too:

for %F in (node*.sr) do (edit %F)

This will bring up each of the new files in edit.com. You'll see the filename with the node number in it. Change the drop file location to that node's temp directory, save the file, and exit. The next file will come up automatically.

Next, change BRE.BAT so it calls the correct setup file for each node:

@echo off
REM BRE.BAT - Called with node # as %1
c:
cd \bbs\mystic\mydoors\fsxnet\bre
srdoor -f node%1.sr
bre planetary
bre
c:
cd \bbs\mystic
mis poll 21:1/10
exit

BRE.BAT needs to be called with the node # as its only parameter. I believe you already have it set up that way but double check.

okay it work now, so I am sure we don't have to do any thing about
NTVDM, right.

Keep an eye on it. It shouldn't have given an error when BRE was in FOSSIL mode.

just another question about dx in linuk rasbperry os in mystic.
or is it only Window.

It's 32 bit Windows only.

Thank you

Not a problem!
--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

Hi Wall E. Weasel

BRE.BAT needs to be called with the node # as its only parameter. I believeyou already have it set up that way but double check.

Okay I have saved all that infomation and will work on so bre can
be played on all nodes

okay it work now, so I am sure we don't have to do any thing about NTVDM, right.

Keep an eye on it. It shouldn't have given an error when BRE was in FOSSILmode.

I keep an eye on it, but at moment all going well.

just another question about dx in linuk rasbperry os in mystic.
or is it only Window.

It's 32 bit Windows only.

that's ok thank you and for your help


also who are like with linus raspberry pi os per port binding

as to the mystic mis

Ian 2nd Choice Core Nz

--- Mystic BBS v1.12 A47 2020/10/31 (Windows/32)
* Origin: 2nd Choice Core : New Zealand (21:1/152)

also who are like with linus raspberry pi os per port binding

as to the mystic mis

I think we have a language barrier here. Can you ask this again differently? --- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

sorry about the language barrier

It's not a problem. I just didn't understand what you were asking.

I have installed mystic on a new raspberry pi (raspberry s linux) and
trying to get ssh to work in mystic, I have posted in this echo before

│ 07:23:23 TELNET Listening on IPV4 port 23 using interface "127.0.0.1"
│ 07:23:23 TELNET Listening on IPV6 port 23 using interface "::"

Since these are working it would seem to indicate that setcap has correctly set the capabilities. But double check with:

getcap ./mis

from the Mystic directory just to make sure. It should show "cap_net_bind_service+ep" for the file.

**│ 07:23:23 SSH Unable to open IPV4 port: Error -1 (13)
**│ 07:23:23 SSH Unable to open IPV6 port: Error -1 (13)

My first guess is you're attempting to use the default port number but SSHD is already using it. Make sure mis is not running and try:

netstat -ltn

Look for something already listening on port 22 (0.0.0.0:22 or <IP
ddress>:22).

Also, just to rule it out, see if SELinux is installed and active. Run the command "sestatus". Hopefully you won't have that command available, and if you do have it hopefully it is not enabled. I don't know if Raspbian installs this by default.

mystic config

ssh server config
active yes
id ssh
adapter type ipv4=ipv6
ipv adapter 0.0.0.0
ipv adapter ::

Which port is it set to use?

--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

Hi Wall E. Weasel

│ 07:23:23 TELNET Listening on IPV4 port 23 using interface "127.0.0.1"
│ 07:23:23 TELNET Listening on IPV6 port 23 using interface "::"

Since these are working it would seem to indicate that setcap has correctly set the capabilities. But double check with:

getcap ./mis

got this ./mis = cap_net_bind_service+ep

from the Mystic directory just to make sure. It should show "cap_net_bind_service+ep" for the file.

**│ 07:23:23 SSH Unable to open IPV4 port: Error -1 (13)
**│ 07:23:23 SSH Unable to open IPV6 port: Error -1 (13)

My first guess is you're attempting to use the default port number but SSHD is already using it. Make sure mis is not running and try:

netstat -ltn

and this

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN tcp6 0 0 :::5900 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN tcp6 0 0 ::1:631 :::* LISTEN

Look for something already listening on port 22 (0.0.0.0:22 or <IP ddress>:22).

Also, just to rule it out, see if SELinux is installed and active. Run the command "sestatus". Hopefully you won't have that command
available, and if you do have it hopefully it is not enabled. I don't know if Raspbian installs this by default.

ranun sestatus

bash: sestatus: command not found

mystic config

ssh server config
active yes
id ssh
adapter type ipv4=ipv6
ipv adapter 0.0.0.0
ipv adapter ::

Which port is it set to use?

whoops sorry left that out, it port 22

Thank you

Ian


--- MultiMail/Win32 v0.49


--- Talisman v0.8-dev (Linux/armv7l)
* Origin: 6th Choice Core (21:1/152.2)

** 07:23:23 SSH Unable to open IPV4 port: Error -1 (13)
** 07:23:23 SSH Unable to open IPV6 port: Error -1 (13)

My first guess is you're attempting to use the default port number but SSHD is already using it. Make sure mis is not running and try:
netstat -ltn

LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:*
LISTEN tcp6 0 0 :::22 :::*

Yep, SSHD is already binding to port 22 on all interfaces. Which means...

mystic config
whoops sorry left that out, it port 22

Mystic can't use port 22 at the same time.

You'll need to change one of the two. Mystic can be changed in its own configuration program.

SSHD's configuration can be changed via the sshd_config command, though it may not bring up your text editor of choice. You can also edit /etc/ssh/sshd_config yourself, then restart SSHD. Either way, change the "Port" directive to something else.

If you don't have a console set up on this Pi then I would leave SSHD alone and move Mystic. If you break SSHD you can effectively brick the installation.

If it was my machine, I would simply move Mystic to port 2222. If the machine is behind a router you'll need to set the router up for port forwarding anyway.
It's just as easy to forward to port 2222 as it is 22.

--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

Wall E. Weasel

** 07:23:23 SSH Unable to open IPV4 port: Error -1 (13)
** 07:23:23 SSH Unable to open IPV6 port: Error -1 (13)

My first guess is you're attempting to use the default port number but SSHD is already using it. Make sure mis is not running and try:
netstat -ltn

LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:*
LISTEN tcp6 0 0 :::22 :::*

Yep, SSHD is already binding to port 22 on all interfaces. Which means...

Okay, at least I know that now for next time.

mystic config
whoops sorry left that out, it port 22

Mystic can't use port 22 at the same time.

Okay. in mystic -cfg servers for ssh I put 24 + set the router up for port and is working fine
so that's good just have to advt that port no.

You'll need to change one of the two. Mystic can be changed in its own configuration program.

SSHD's configuration can be changed via the sshd_config command, though it may not bring up your text editor of choice. You can also edit /etc/ssh/sshd_config yourself, then restart SSHD. Either way, change
the "Port" directive to something else.

had a look at sshd_config

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options override the
# default value.

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::


would I just change port to say 24 or would I have to insert it in another
line with out the # save a reboot.

If you don't have a console set up on this Pi then I would leave SSHD alone and move Mystic. If you break SSHD you can effectively brick the installation.

I just lease things were there are at present

If it was my machine, I would simply move Mystic to port 2222. If the machine is behind a router you'll need to set the router up for port forwarding anyway.
It's just as easy to forward to port 2222 as it is 22.

do you mean What I have done in mystic config server port 22 to 24
and set the router up for port


Thank you

Ian 2nd Choice Core NZ

--- MultiMail/Win32 v0.49


--- Talisman v0.8-dev (Linux/armv7l)
* Origin: 6th Choice Core (21:1/152.2)

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

I have a couple of ssh servers setup and I always change the port to something else, 7022 or something so you could do that in your config and that will leave port 22 available for your BBS on the default port.

There is so much scum doing nothing good on port 22 (23 and 25 is much the same) that I use an alternative port for the BBS also.

Just don't forget what is on port what if you do that. ;)

--- BBBS/Li6 v4.10 Toy-5
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)

Hi Al

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

I have a couple of ssh servers setup and I always change the port to something else, 7022 or something so you could do that in your config
and that will leave port 22 available for your BBS on the default port.

There is so much scum doing nothing good on port 22 (23 and 25 is much
the same) that I use an alternative port for the BBS also.

just asking, so you saying, leave the sshd as is and change
./mystic -cfg server ssh to 2222

Just don't forget what is on port what if you do that. ;)

I have to take a note of the port no , so I don't forget

Thank you

Ian




___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A47 2020/10/31 (Windows/32)
* Origin: 2nd Choice Core : New Zealand (21:1/152)

had a look at sshd_config

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

would I just change port to say 24 or would I have to insert it in
another line with out the # save a reboot.

You would either remove the # and change it to say "Port 24" or insert another line with only "Port 24". The # indicates the rest of the line is a comment so it's ignored by SSHD.

I tend to always insert a new line with my configuration and leave the original commented one in. It helps me remember the default values when I'm messing with things.

It's just as easy to forward to port 2222 as it is 22.

do you mean What I have done in mystic config server port 22 to 24
and set the router up for port

Yes, just have your router forward to whichever port you have set up instead of 22.

--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

There is so much scum doing nothing good on port 22 (23 and 25 is much
the same) that I use an alternative port for the BBS also.

just asking, so you saying, leave the sshd as is and change
./mystic -cfg server ssh to 2222

I would move the sshd port elswhere and leave it free for the BBS. You could put your BBS on an alternative port also, that's a choice you have to make.

It's probably easier for everyone to leave ports on there standard port whenever possible. If you use non standard ports you and your users need to know what port to use.

--- BBBS/Li6 v4.10 Toy-5
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)

Hi Al

just asking, so you saying, leave the sshd as is and change
./mystic -cfg server ssh to 2222

I would move the sshd port elswhere and leave it free for the BBS. You could put your BBS on an alternative port also, that's a choice you
have to make.

It's probably easier for everyone to leave ports on there standard port whenever possible. If you use non standard ports you and your users
need to know what port to use.

I have set sshd to 2222 and bbs sshserver to 22 and working the way I wanted it, if there is a reason to change, at lease I know now how to do it.

so thank you for your help

Ian 2nd Choice Core Nz
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A47 2020/10/31 (Windows/32)
* Origin: 2nd Choice Core : New Zealand (21:1/152)

That's cool all fixed now with your help thank you

Great! Glad it's working.

just a question in bre per mystic data command line
mine is c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3

is this setting okay to use for the node1 node2 node3 etc

Yes, %3 passes the node # which is what you want to use. %N would also be fine.

--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)