|reply to Broken NAT |
Re: SSH forwarding
You are advised to run your SSH on a non standard port anyways. Trust me, you will thank me. My logs were filled with script kiddies and bots, but no one guesses my high range port now! absolutely no one.
But yeah it probably has some remote management on the router which you would access using ssh. Did you try and ssh into the router yet? did you look up the router manual?
My active port 22 machines, were showing around 24000 attempts on root each 24 hour period, before I started to auto-ban them, they were at times crashing my NAT router...
Not as annoying as the FTP bots that tries hundreds/thousands of passwords each run, even when I allow their current username on any password (access granted) they disconnect and keep trying.
But I agree with @noclue unless you need to run on port 22, I advise picking a different port.
Port 443 works well, because network/traffic monitoring software is expecting encypted traffic on that port when you are travelling.
Yes, I am not employed and looking for IT work. Have passport, will travel.