Hello, sorry to bother you, great work on Mystic. I've got the BBS
able to send and receive echomail after following Mystic Guy videos.
I'm using the Linux A46 version. When I fire up the mis server over
the local network it tells me telnet error 1 13. I can telnet into the
computer over the local network on port 23, but Mystic BBS is not
available. I've also tried the OSX Mystic and that won't send and
receive echomail when I try to connect to 21:1/100, it gives me "error
4." Don't you think it would be a good idea to publish these error
codes with an explanation of what they mean? Or at least give your
email address on the wiki. I had to join another BBS in order to send
you a message!

--- Ezycom V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

On 10 Aug 2021, Suji said the following...

I'm using the Linux A46 version. When I fire up the mis server over
the local network it tells me telnet error 1 13. I can telnet into the computer over the local network on port 23, but Mystic BBS is not available. I've also tried the OSX Mystic and that won't send and
receive echomail when I try to connect to 21:1/100, it gives me "error
4." Don't you think it would be a good idea to publish these error
codes with an explanation of what they mean? Or at least give your

g00r00 isn't quick here and most of us will try to help, I'm Brian and run Mysitc Pi BBS since 2016 or so on a Pi. If you look at the tagline you'll see I'm currently chasing the A47 Alpha version of mystic which is likely near release. My general handle is bcw142 as you should see above.

Something has to be wrong with your binkp settings for 21:1/100. There is also likely no hole in your router firewall for incoming signals. You can get to other systems so normal outgoing is working. I get through from my work so
I know even a tricky vpn/firewall can be binkp connected through. I'd say that is the first thing to tackle. I'll have to look at the mystic/docs, but I think the error messages are there if in programeze (header file or the like). Are you using the /999 for binkp or have you got a number from Avon?

My main BBS system (A Pi) is setup as DMZ on my router, which means all of
it is directly exposed to the net. Mystic works well to keep the attackers
out even then. My other systems have holes through the router's firewall.

* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

I see you used tinysbbs to get through. Mine is at bcw142.zapto.org using mostly standard ports (21, 22, 23, 80...). You'll find a webpage there using the old http://bcw142.zapto.org/ setup (haven't figured out the SSL and such for https on Mystic yet, but the SSH port is working.

... Evil triumphs when good people do nothing. - Einstein

--- Mystic BBS v1.12 A47 2021/08/05 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

The best tutorials for Mystic setup come from Avon as "Mystic Guy"
on YouTube. The first things you'll usually see are:
Mystic BBS - Installing + First Steps
Mystic BBS - Message Network Setup Part 1
Mystic BBS - Message Network Setup Part 2

A telnet error isn't all that important, getting binkp up and running is.
That would give you a way to get help on your system. Generally you setup
the system as in the above videos and then use nodespy as a terminal to
send and receive via mystic. Nodespy should handle the telnet side of
things without issues. nodespy has a 'phonebok' setup, if you hit spacebar
on the 'Waiting; lines you'll see the 'phonebook' setup. On empty lines
you can use Alt-E to edit the 'Phonebook' in nodespy that allows you to
setup an autodial like entry to reach your bbs and others.
Graphically the general /999 setup for binkp looks like:

/mystic $ ./mystic -cfg ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ █ Configuration Networking Servers Editors Other Exit █ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Available Servers ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄
█ █
█ Active Type ID Port IPV4 IPV6 █
▄▄ ▄█─────────────────────────────────────────────────█ ░▓gj!
▐█▄▄ ■ ▀ █ Yes TELNET TELNET 23 Yes Yes ░▀▀▄▄▄▄▄▄▄██▄▄
░███▄▄ ▄█ Yes RLOGIN RLOGIN 513 Yes Yes ░▀███████████▒■ ▀ ▓████▄▄▀█▓▀▄█ Yes SSH SSH 22 Yes Yes ░▀▐█▓ ▄▄ ▄███▌▐ ▓ ▒▓▓▓█▀▀█▄▄█▀█ Yes BINKP BINKP 24556 Yes Yes ▓▓▓▓▒ ▓ ▐▓▓▓░ ▓ ▀ █░░░█ ▀▀▀▀ █ Yes FTP FTP 21 Yes Yes ░▒░░░▌▀ ░░░█░ ▓ ░░▓████ ▓▄▄▄▄▓█ Yes NNTP NNTP 119 Yes Yes ░▀████▄▄▄▄▄ ▄▄█ ▄▄■ ▀▀▓ ▒ ░░▓█ Yes POP3 POP3 110 Yes Yes ░ ▀▀▀▀▀▀▀ ▌░░
░ █ Yes SMTP SMTP 25 Yes Yes ░ ▀▄
█ Yes HTTP HTTP 80 Yes Yes ░
█─────────────────────────────────────────────────█
█ Press / for command list █
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█


+++────────────────────────────────────────────────────────────── ─── ── ─ ─ · ::: (Servers) -> Configure Servers... ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ █ Configuration Networking Servers Editors Other Exit █ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Server BINKP ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄
█ █
█ Active │ Yes Force CRAM-MD5 │ No █
▄▄ █ ID │ BINKP Allow UnSecure │ Yes █▓gj!
▐█▄█ Adapter Type │ IPV4+IPV6 File Conflicts │ Rename ██▄▄
░███ IPV4 Adapter │ 0.0.0.0 ███▒■ ▀ ▓██ IPV6 Adapter │ :: ███▌▐ ▓ ▒▓█ Port │ 24556 █▓░ ▓ ▀ █░█ Max Allowed │ 10 ██░ ▓ ░░▓██ Auto IP Ban │ 0 in 0 secs █ ▄▄█ ▄▄■ █ Country Block │ No █ ▌░░
█ Send Blocked │ No █ ▀▄
█ Time Out │ 60 █
█ SSL Port │ 0 █
█ █
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█


+++────────────────────────────────────────────────────────────── ─── ── ─ ─ · ::: (Server BINKP) -> Is server active?... ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ █ Configuration Networking Servers Editors Other Exit █ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄
█ Network Address Domain Pri Description █
█ ──────────────────────────────────────────────────────────────── █
▄▄ █ 0:0/0 No Local Address ▓░▓gj!
▐█▄▄ █ 21:1/999 fsxnet Yes FSXNet ░██▄▄
░███▄█ 0:0/0 No ░███▒■ ▀ ▓████ 0:0/0 No ░███▌▐ ▓ ▒▓▓▓█ 0:0/0 No ░▓▓░ ▓ ▀ █░░░█ 0:0/0 No ░░█░ ▓ ░░▓████ 0:0/0 No ░▄ ▄▄█ ▄▄■ ▀▀█ 0:0/0 No ░▀ ▌░░
█ 0:0/0 No ░ ▀▄
█ 0:0/0 No ░
█ 0:0/0 No ░
█ 0:0/0 No ░
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█


+++────────────────────────────────────────────────────────────── ─── ── ─ ─ · ::: (Networking) -> Echomail Addresses... ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ █ Configuration Networking Servers Editors Other Exit █ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄
█ Netwo█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Echomail Network ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄ █
█ ─────█ █────── █
▄▄ █ 0:0/0█ Address █ ▓░▓gj!
▐█▄▄ █ 21:1/█ Zone │ 21 █ ░██▄▄
░███▄█ 80:60█ Net │ 1 █ ░███▒■ ▀ ▓████ 0:0/0█ Node │ 999 █ ░███▌▐ ▓ ▒▓▓▓█ 0:0/0█ Point │ 0 █ ░▓▓░ ▓ ▀ █░░░█ 0:0/0█ █ ░░█░ ▓ ░░▓████ 0:0/0█ Domain │ fsxnet █ ░▄ ▄▄█ ▄▄■ ▀▀█ 0:0/0█ Description │ FSXNet █ ░▀ ▌░░
█ 0:0/0█ Primary │ Yes █ ░ ▀▄
█ 0:0/0█ █ ░
█ 0:0/0▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ ░
█ 0:0/0 No ░
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█


+++────────────────────────────────────────────────────────────── ─── ── ─ ─ · ::: (Echomail Network) -> Network Zone...

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ █ Configuration Networking Servers Editors Other Exit █ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ EchoMail Nodes ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄ █ I█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Node ID 1 (21:1/100@fsxnet) ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄k █ █ ─█ Active │ Yes 1:GENERAL █─ █ █ 3█ Description │ FSXNet_Hub 2:Security █2 ░ █ 2█ SysOp Name │ bcw142 3:Groups █0 ░ █ 1█ Address │ 21:1/100 4:BinkP █0 ▓ █ 4█ Domain │ fsxnet 5:FTP █2 ░ █ 5█ Session Type │ BinkP 6:Dir Toss █1 ░ █ 6█ Archive Type │ █3 ░ █ 7█ Export Type │ Normal █3 ░ █ 8█ Route Info │ 21:* █5 ░ █ 9█ Max PKT Size │ 512 █4 ░ █ 1█ Max ARC Size │ 2048 █4 ░ █ ─█ Use Filebox │ No █─ █ █ █ Filebox Dir │ █3 █ █ █ Crash Limiter │ 0 █5 █ █ █ │ Page 1 of 6 █ █ █ C▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ █ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Press / for command list ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ +++────────────────────────────────────────────────────────────── ─── ── ─ ─ · ::: (Echomail Node) -> Node active... ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ █ Configuration Networking Servers Editors Other Exit █ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ EchoMail Nodes ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄ █ I█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Node ID 1 (21:1/100@fsxnet) ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄k █ █ ─█ BINKP Hostname │ agency.bbs.nz:24556 1:General █─ █ █ 3█ IP Type │ IPV4+IPV6 2:Security █2 ░ █ 2█ Server Type │ Normal 3:Groups █0 ░ █ 1█ Password │ LETMEIN 4:BINKP █0 ▓ █ 4█ Time Out │ 30 5:FTP █2 ░ █ 5█ Block Size │ 16384 6:Dir Toss █1 ░ █ 6█ CRAM-MD5 │ Yes █3 ░ █ 7█ Hide AKAs │ Yes █3 ░ █ 8█ │ █5 ░ █ 9█ │ █4 ░ █ 1█ │ █4 ░ █ ─█ │ █─ █ █ █ │ █3 █ █ █ │ █5 █ █ █ │ Page 4 of 6 █ █ █ C▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ █ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Press / for command list ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ +++────────────────────────────────────────────────────────────── ─── ── ─ ─ · ::: (Echomail Node) -> <hostname>:<port>...

That should be able to get binkp up till you get a proper number from Avon
for a BBS.

... Old computers make great boat anchors

--- Mystic BBS v1.12 A47 2021/08/05 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

Thanks for your reply and for taking the time to explain your setup.
My Binkp is working fine and I have been able to send and receive
echomail using 21:1/999. The problem I'm having is that I can't telnet
from one computer to another over the local network. The mis server is
showing error 1 13, which I have since found out is a permissions
error. So if I run mis with sudo, the error changes to error 1 98. I
don't have a firewall running, it's just two computers on the local
network. Binkp is running with no errors. I can telnet in from one
computer and log in with my user name, but I am not interfacing with
mystic even though it is up and running on the other computer. My
intention was only to apply for a node number once I was able to get
mystic running on the local network. I have tried linux, windows, and
OS X and they all act differently but I can't telnet no matter what.s

--- Ezycom V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

On 11 Aug 2021, Suji said the following...

showing error 1 13, which I have since found out is a permissions
error. So if I run mis with sudo, the error changes to error 1 98. I
don't have a firewall running, it's just two computers on the local network. Binkp is running with no errors. I can telnet in from one computer and log in with my user name, but I am not interfacing with mystic even though it is up and running on the other computer. My intention was only to apply for a node number once I was able to get mystic running on the local network. I have tried linux, windows, and
OS X and they all act differently but I can't telnet no matter what.s

It does seem odd, as you may have noticed I'm running on Linux so I use
sudo ./mis daemon
to start mystic from in my case the /mystic directory. If you can telnet
in then you've opened port 23 I guess. Between Linux & Windows I use putty
and run mystic on Linux. The permissions thing can be tricky and error messages as well, my guess is the 1 is the fpc (Free Pascal Compiler)error
and the 98 is from mystic. I generally use nodespy between machines and to
get to the outside world as well. On the machine running mystic you should
be able to telnet using both nodespy & the normal telnet command though
you may need to change the general settings in mystic. There are two
important settings under Configuration, General Settings: Config Theme
as 3D ANSI and Local Codepage UTF8. Current Linux & Windows are both using
UTF8 at present by default. The easiest thing to do is using nodespy on
the machine running mystic, Linux in my case so
./nodespy #from /mystic directory
It should come up with default entries that include localhost or the IP4 address of the machine on the local network (10.0.0.21 in my case). So
in nodespy hitting space on a waiting line will show the phonebook entries
with a system name, Address like localhost:23 LastCall date and number of calls. With Alt-E you can edit the entries and use either localhost if on
the machine or the IP4 address (10.0.0.21 in my case) and both should work fine. To exit a login you can use Alt-X which will 'drop carrier' in the old
way of looking at it (drop telnet session) and put you back to nodespy. If
you have mystic on both machines that should all work If not, then putty
on the remote machine should work (on Linux or Windows). It will need a
host name or IP4 address for the remote machine and port 23 for telnet with connection type set to Telnet, then give it a name under Saved Sessions
and click the Save so you can easily call it up after this.and click open.
The PuTTY window should open with the BBS prompt and login as was done with nodespy locally. If the Mystic screen looks all messed up but the text of the lines is right you want to change a setting in putty, so drop out using
the close window, it will ask to close this session and click Yes. Start
putty again pick the saved one and load them click Translation under Window.
If it says UTF-8 then click on the down arrow at the end of the line and
pick CP437 and uncheck the Override with UTF-8. Then click Session and Save
so it will be saved that way and open again. It should appear right now and
you should login and use the BBS. Everything should look and work correctly. You can google putty to find a version for Windows or generally just load
it under Linux with:
sudo apt install putty
Or using whatever the install setup is for that Linux. Putty will setup the permissions on that end. If your still getting errors from the remote machine, but nodespy worked, then you need to set the permissions for the mystic directory. In my case that's
sudo chown -R user:user /mystic
with user as your Linux user name. It will run OK even with mis running and things should work correctly after that. You may want to change or add user names to mystic (./mystic -cfg) and change permissions under mystic for them. under Editors, U User Editor, enter on a user name and Ctrl-U to change the mystic permission level to 20 (regular user) or 255 (sysop) after you've logged off mystic with the remote setup.

... There is an exception to every rule, except this one.

--- Mystic BBS v1.12 A47 2021/08/05 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

On 11 Aug 2021 at 10:24p, Suji pondered and said...

echomail using 21:1/999. The problem I'm having is that I can't telnet from one computer to another over the local network. The mis server is showing error 1 13, which I have since found out is a permissions
error. So if I run mis with sudo, the error changes to error 1 98. I
don't have a firewall running, it's just two computers on the local

Can you ping the mystic telnet server from the other box on the lan?

What client are you using on the other box to try and connect to the mystic telnet server running on the other machine?

Best, Paul

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I'm using the Linux A46 version. When I fire up the mis server over
the local network it tells me telnet error 1 13. I can telnet into the

First I would recommend upgrading to the most recent A47 version. http://wwwmysticbbs.com/downloads/prealpha/
Second a Telnet 1 error means the port is not open. Make sure you have that port open on your router/firewall.
Jeff

... Back up my hard drive? I can't find the reverse switch!

--- Mystic BBS v1.12 A47 2021/08/07 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

Sparky, thanks to you and everyone else for your replies and patience. I couldn't reply for a while because i was communicating via Tiny's BBS which has either been down for days or I have been locked out. What i discovered after days of searching and trying is that telnet on the linux machine was already on port 23 and that mystic had to be on another port to respond automatically. That really should be in the documentation. I'm slowly making progress and I will soon apply for a node number from Avon. I really am amazed at the generosity of this community and all that info certainly steered me in the right direction. I hope some day I can return the favors!

--- Mystic BBS v1.12 A47 2021/08/08 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 19 Aug 2021 at 05:49p, suji pondered and said...

documentation. I'm slowly making progress and I will soon apply for a
node number from Avon. I really am amazed at the generosity of this community and all that info certainly steered me in the right direction.
I hope some day I can return the favors!

Kudos guys for your support helping new folks get into our great hobby.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)