Subj : Re: Got it!
To   : Shurato
From : Gamgee
Date : Wed Jul 16 2025 16:15:53

-=> Shurato wrote to Gamgee <=-

 Ga> Sh> Ok, it seems to work with OPNSense, but I can't get inbound SSH
 Ga> Sh> connections to work on any port... I'm not looking to connect to the
 Ga> Sh> OPNSense, but the BBS.  All of the google suggestions are for the
 Ga> Sh> former, not the latter.  My port forwarding is set up right for
 Ga> Sh> everything else, but ssh is timing out when trying to connect to
 Ga> Sh> shsbbs.net port 22.  Any ideas?  Mystic isn't showing any
 Ga> connections.

 Ga> Is Mystic *listening* on port 22?  I tried 'nmap' on that host, and it
 Ga> doesn't appear that there's anything active on port 22:

 Ga> danc@moria:~$ nmap shsbbs.net Starting Nmap 7.93 ( https://nmap.org
 Ga> ) at 2025-07-16 08:10 CDT Nmap scan report for shsbbs.net
 Ga> (174.27.216.208) Host is up (0.091s latency). rDNS record for
 Ga> 174.27.216.208: 174-27-216-208.bois.qwest.net Not shown: 995 filtered
 Ga> tcp ports (no-response) PORT STATE SERVICE 21/tcp open ftp 23/tcp
 Ga> open  telnet 80/tcp open http 119/tcp open nntp 443/tcp open https

 Ga> Nmap done: 1 IP address (1 host up) scanned in 6.70 seconds

 Sh> Ok, the windows firewall wasn't set up for public access, only private
 Sh> and the sshd on the guest hadn't been installed since an OS
 Sh> reinstallation... User error is the way!  Odd with the firewall rule,
 Sh> it was working with my ng1100!

Yep, nmap now shows port 22 available.

You're welcome.



.... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.28-Linux
 * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (618:250/24)

.