Cozmo wrote to All <=-
What would cause the message "Lost Carrier" when trying to run a door?
I'm using Netfoss as my fossil.
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.
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
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
Okay my netfoss version is 1.14R but for same reason it working now
but what to use it without fossil if I can.
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?
okay is is my Data c:\bbs\mystic\mydoors\fsxnet\bre\bre.bat %3 line
I had a go at but doesn'y work for me, nothing happens after I press
the no of bre on the menu
okay I did all that and YES it is working fine now useing dx and
no fossel
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
okay it work now, so I am sure we don't have to do any thing about
NTVDM, right.
just another question about dx in linuk rasbperry os in mystic.
or is it only Window.
Thank you
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 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.
just another question about dx in linuk rasbperry os in mystic.
or is it only Window.
It's 32 bit Windows only.
also who are like with linus raspberry pi os per port binding
as to the mystic mis
sorry about the language barrier
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 "::"
**│ 07:23:23 SSH Unable to open IPV4 port: Error -1 (13)
**│ 07:23:23 SSH Unable to open IPV6 port: Error -1 (13)
mystic config
ssh server config
active yes
id ssh
adapter type ipv4=ipv6
ipv adapter 0.0.0.0
ipv adapter ::
Γöé 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?
** 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 :::*
mystic config
whoops sorry left that out, it port 22
** 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.
#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
#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. ;)
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.
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
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 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.
That's cool all fixed now with your help thank you
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
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,053 |
Nodes: | 15 (1 / 14) |
Uptime: | 83:38:01 |
Calls: | 500,790 |
Calls today: | 1 |
Files: | 109,358 |
D/L today: |
1,751 files (584M bytes) |
Messages: | 466,387 |
Posted today: | 5 |