Subj : Re: telnet error
To   : Suji
From : bcw142
Date : Fri Aug 13 2021 02:27 am

On 11 Aug 2021, Suji said the following...
 
 Su> showing error 1 13, which I have since found out is a permissions
 Su> error. So if I run mis with sudo, the error changes to error 1 98. I
 Su> don't have a firewall running, it's just two computers on the local
 Su> network. Binkp is running with no errors. I can telnet in from one
 Su> computer and log in with my user name, but I am not interfacing with
 Su> mystic even though it is up and running on the other computer. My
 Su> intention was only to apply for a node number once I was able to get
 Su> mystic running on the local network. I have tried linux, windows, and
 Su> 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)

.