Subj : Re: BBS door "lost carrier"
To   : Sneaky
From : Wall E. Weasel
Date : Mon Aug 02 2021 11:30 am

Sn>  sorry about the language barrier

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

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

Sn> │ 07:23:23 TELNET   Listening on IPV4 port 23 using interface
Sn> "127.0.0.1"
Sn> │ 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.

Sn> **│ 07:23:23 SSH      Unable to open IPV4 port: Error -1 (13)
Sn> **│ 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.

Sn> mystic config

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

Which port is it set to use?

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

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.