I'm running a simple Ubuntu installation on a custom built box on my home network. I am able to SSH into the box from the local 192.x.x.x address while on my home wifi.
I've been trying to get this connected in a way that I can SSH into the box from other networks, like at work and I think I've read every article on the internet now about how to do this.
- Server is running OpenSSH, can connect to it from within the network. Check.
- Router (Eero) has port forwarding enabled. I have one port forwarding reservation set up forwarding 21>192.x.x.x:22 Check.
- I can ping my external IP, 67.x.x.x (I tethered my laptop to my phone's cellular before doing so). Check.
- Now I assume I should be able to do
ssh [email protected] -p 21
but this times out.
When I run nmap
on this IP, it does not find any open ports.
All 1000 scanned ports on ai.sytes.net (67.x.x.x) are filtered
Running it with -nP
says I have about 999 "filtered" ports. Only port 21 is listed as open. Could any of that be the reason?
Starting Nmap 7.60 ( https://nmap.org ) at 2018-03-06 21:33 PST
Nmap scan report for yy.yy.net (67.x.x.x)
Host is up (0.018s latency).
rDNS record for 67.x.x.x: c-67-x-x-x.hsd1.ca.comcast.net
Not shown: 999 filtered ports
PORT STATE SERVICE
21/tcp open ftp
Nmap done: 1 IP address (1 host up) scanned in 10.68 seconds
Edit: Looks like 22 and another four digit port were open to when I ran nmap -sT -p XX [host]
against those ports. I've set up port forward reservations for those as well but am still getting the same results.
ssh -p 21 [email protected]
instead. All options after user@host are passed to the remote shell, not to local ssh