Subj : BBS door "lost carrier" To : Wall E. Weasel From : Sneaky Date : Tue Aug 03 2021 07:46 am Hi Wall E. Weasel 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 "::" WEW> Since these are working it would seem to indicate that setcap has WEW> correctly set the capabilities. But double check with: WEW> getcap ./mis got this ./mis = cap_net_bind_service+ep WEW> from the Mystic directory just to make sure. It should show WEW> "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) WEW> My first guess is you're attempting to use the default port number but WEW> SSHD is already using it. Make sure mis is not running and try: WEW> 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 WEW> Look for something already listening on port 22 (0.0.0.0:22 or ddress>:22). WEW> Also, just to rule it out, see if SELinux is installed and active. Run WEW> the command "sestatus". Hopefully you won't have that command WEW> available, and if you do have it hopefully it is not enabled. I don't WEW> know if Raspbian installs this by default. ranun sestatus bash: sestatus: command not found 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 :: WEW> 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) .