This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Local SSH works, remove SSH fails even with port-forwarding
I have enabled SSH, and locally works fine for the accounts that have SSH enabled.
However, when I port forward port 22 to the NAS, it doesn't respond when trying to use SSH (on laptop/phone when away/using mobile data). There is a timeout response from the client and the logs from the NAS just show (auth.log):
Sep 10 19:07:21 NAS sshd[10270]: pam_unix(sshd:session): session opened for user admin by (uid=0) Sep 10 19:07:21 NAS sshd[10270]: pam_unix(sshd:session): session closed for user admin
Any way to diagnose what's preventing access to the NAS via SSH?
I've also enabled FTP (+SFTP) and same issue, no response/time outs when connecting from an external IP (non-LAN).
When port-forwarding to another device (not the NAS) on the same port, it works fine....
I have enabled SSH, and locally works fine for the accounts that have SSH enabled.
However, when I port forward port 22 to the NAS, it doesn't respond when trying to use SSH (on laptop/phone when away/using mobile data). There is a timeout response from the client and the logs from the NAS just show (auth.log):
Sep 10 19:07:21 NAS sshd[10270]: pam_unix(sshd:session): session opened for user admin by (uid=0) Sep 10 19:07:21 NAS sshd[10270]: pam_unix(sshd:session): session closed for user admin
Any way to diagnose what's preventing access to the NAS via SSH?.
Uneducated guess: You need to use the username root, instead of admin.
Re: Local SSH works, remove SSH fails even with port-forwarding
When trying to log in, it's not even prompting for anything. When using an external IP not related to the NAS external IP (ie not LAN IP's), it appears to not respond at all (no banner, login, etc.). I switch to the NAS public IP (NAS is within a LAN), and the login prompt appear fine.
It appears there's a external IP blocker or external IP blacklist, since the LAN IP's work and the External IP of the NAS works fine too. I don't recall setting one up (fail2ban, hosts, etc.) but hen again, it's been awhile since I did anything with the NAS....
Not running fail2ban, the /etc/hosts.deny is empty, /etc/hosts.allow is empty
When trying to log in, it's not even prompting for anything. When using an external IP not related to the NAS external IP (ie not LAN IP's), it appears to not respond at all (no banner, login, etc.). I switch to the NAS public IP (NAS is within a LAN), and the login prompt appear fine.
It appears there's a external IP blocker or external IP blacklist, since the LAN IP's work and the External IP of the NAS works fine too. I don't recall setting one up (fail2ban, hosts, etc.) but hen again, it's been awhile since I did anything with the NAS....
Assuming you have a public routeable WAN IP on your Internet connection: Some ISPs are blocking common ports, or have firewall services blocking major services, like 22/TCP for example.
Coming back on your comment of ftp and sftp - which are two complete different beasts: sftp does operate on the named 22/TCP, while ftp does operate on 23/TCP for the control connection, plus one more port for the FTP data connection - what can make things much more difficult for the NAT, for the FTP server config, and for the FTP client.
Re: Local SSH works, remove SSH fails even with port-forwarding
It's on a RN316, OS 6.10.8. I've stripped down to a bare external SSH connection to troubleshoot external IP's accessing the NAS, it won't be permanently exposed in the end, but for now as part of a process of elimination I need to start with a simple base-line of Client -> External IP -> ISP -> Router (Port Forwarding) -> NAS (LAN)
It's not the ISP or the router. I keep the port-forwarding settings on the router the same, except change destination IP from the NAS to another server and it works fine with the other server. When I use the NAS as the destination IP, it doesn't work. This is the same regardless of which external port used.
ie
Client -> External IP -> ISP -> Router (Any External Port -> Port Forwarding to internal 22) -> RPi-Server (LAN) ** works
Client -> External IP -> ISP -> Router (Any External Port -> Port Forwarding to internal 22) -> NAS (LAN) ** fails
Port forwarded using TCP/UDP and both, same result. Access to the other LAN Server works fine, but NAS fails.
Yep FTP usually uses port 21 for control and port 20 for data but I also have high port ranges on that as well for passive mode. I was using FTP just to test connectivity, I'm mainly after the SSH (or SFTP) to work for now.
Does the the RN OS have any other ip settings that could cause external ip blocks? There's the standard ones I've listed above (the usual for Ubuntu/Debian, etc.)
Does the the RN OS have any other ip settings that could cause external ip blocks? There's the standard ones I've listed above (the usual for Ubuntu/Debian, etc.)
Not that I know of.
Just wondering - do you have both NICs connected on the RN316?
