Shurato wrote to All <=-
Ok, it seems to work with OPNSense, but I can't get inbound SSH connections to work on any port... I'm not looking to connect to the OPNSense, but the BBS. All of the google suggestions are for the
former, not the latter. My port forwarding is set up right for
everything else, but ssh is timing out when trying to connect to shsbbs.net port 22. Any ideas? Mystic isn't showing any connections.
Shurato wrote to All <=-
Ok, it seems to work with OPNSense, but I can't get inbound SSH connections to work on any port... I'm not looking to connect to the OPNSense, but the BBS. All of the google suggestions are for the former, not the latter. My port forwarding is set up right for everything else, but ssh is timing out when trying to connect to shsbbs.net port 22. Any ideas? Mystic isn't showing anyconnections.
Is Mystic *listening* on port 22? I tried 'nmap' on that host, and it doesn't appear that there's anything active on port 22:
danc@moria:~$ nmap shsbbs.net Starting Nmap 7.93 ( https://nmap.org
) at 2025-07-16 08:10 CDT Nmap scan report for shsbbs.net
(174.27.216.208) Host is up (0.091s latency). rDNS record for 174.27.216.208: 174-27-216-208.bois.qwest.net Not shown: 995 filtered
tcp ports (no-response) PORT STATE SERVICE 21/tcp open ftp 23/tcp
open telnet 80/tcp open http 119/tcp open nntp 443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 6.70 seconds
... 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)
Shurato wrote to All <=-
Ok, it seems to work with OPNSense, but I can't get inbound SSH connections to work on any port... I'm not looking to connect to the OPNSense, but the BBS. All of the google suggestions are for the former, not the latter. My port forwarding is set up right for everything else, but ssh is timing out when trying to connect to shsbbs.net port 22. Any ideas? Mystic isn't showing anyconnections.
Is Mystic *listening* on port 22? I tried 'nmap' on that host, and it doesn't appear that there's anything active on port 22:
danc@moria:~$ nmap shsbbs.net Starting Nmap 7.93 ( https://nmap.org
) at 2025-07-16 08:10 CDT Nmap scan report for shsbbs.net
(174.27.216.208) Host is up (0.091s latency). rDNS record for 174.27.216.208: 174-27-216-208.bois.qwest.net Not shown: 995 filtered
tcp ports (no-response) PORT STATE SERVICE 21/tcp open ftp 23/tcp
open telnet 80/tcp open http 119/tcp open nntp 443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 6.70 seconds
... 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)
Shurato wrote to Gamgee <=-
Ok, it seems to work with OPNSense, but I can't get inbound SSH connections to work on any port... I'm not looking to connect to the OPNSense, but the BBS. All of the google suggestions are for the former, not the latter. My port forwarding is set up right for everything else, but ssh is timing out when trying to connect to shsbbs.net port 22. Any ideas? Mystic isn't showing anyconnections.
Is Mystic *listening* on port 22? I tried 'nmap' on that host, and it doesn't appear that there's anything active on port 22:
danc@moria:~$ nmap shsbbs.net Starting Nmap 7.93 ( https://nmap.org
) at 2025-07-16 08:10 CDT Nmap scan report for shsbbs.net
(174.27.216.208) Host is up (0.091s latency). rDNS record for 174.27.216.208: 174-27-216-208.bois.qwest.net Not shown: 995 filtered
tcp ports (no-response) PORT STATE SERVICE 21/tcp open ftp 23/tcp
open telnet 80/tcp open http 119/tcp open nntp 443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 6.70 seconds
Ok, the windows firewall wasn't set up for public access, only private
and the sshd on the guest hadn't been installed since an OS reinstallation... User error is the way! Odd with the firewall rule,
it was working with my ng1100!
Shurato wrote to Gamgee <=-
theOk, it seems to work with OPNSense, but I can't get inbound SSH connections to work on any port... I'm not looking to connect to
OPNSense, but the BBS. All of the google suggestions are for the former, not the latter. My port forwarding is set up right for everything else, but ssh is timing out when trying to connect to shsbbs.net port 22. Any ideas? Mystic isn't showing anyconnections.
Is Mystic *listening* on port 22? I tried 'nmap' on that host, andit
doesn't appear that there's anything active on port 22:
danc@moria:~$ nmap shsbbs.net Starting Nmap 7.93 ( https://nmap.org ) at 2025-07-16 08:10 CDT Nmap scan report for shsbbs.net (174.27.216.208) Host is up (0.091s latency). rDNS record for 174.27.216.208: 174-27-216-208.bois.qwest.net Not shown: 995 filtered tcp ports (no-response) PORT STATE SERVICE 21/tcp open ftp 23/tcp
open telnet 80/tcp open http 119/tcp open nntp 443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 6.70 seconds
Ok, the windows firewall wasn't set up for public access, onlyprivate
and the sshd on the guest hadn't been installed since an OS reinstallation... User error is the way! Odd with the firewall rule, 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)
Gamgee wrote to Shurato <=-
Yep, nmap now shows port 22 available.
You're welcome.
Digimaus wrote to Gamgee <=-
Gamgee wrote to Shurato <=-
Yep, nmap now shows port 22 available.
Personally, I turn off Windows Firewall. No need for it with a good
edge firewall and programs that can handle being exposed to the public Internet.
You're welcome.
You sound like you've worked in IT for some reason. XD
++ Sean "Did you turn it off and back on?"
Absolutely. Thankfully, the only Windows around here is my wife's
desktop, so I only have to turn it off once. ;-)
Sean Dennis wrote to Gamgee <=-
Hi Dan,
Absolutely. Thankfully, the only Windows around here is my wife's
desktop, so I only have to turn it off once. ;-)
Yeah, at John Deere, they had so many problems becaue HQ -insistred- on leaving WF on and every time we had to update Windows via SCCM, that firewall would break and a manufacturing line would go down which was
an expensive process. I'd log into the master controller system for
that line, disable WF, and nine times out of ten, the line would
magically work again.
I am looking at moving from pfSense on my edge firewall to OpenWRT. OpenWRT looks to be easier and much more functional for me since it has
so many extensions. I'll probably put that off until next month. The next few weeks are going to be busy for me.
Sysop: | Nitro |
---|---|
Location: | Portland, OR |
Users: | 4 |
Nodes: | 10 (0 / 10) |
Uptime: | 77:25:35 |
Calls: | 163 |
Files: | 758 |
Messages: | 91,207 |