NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
robo731
Oct 31, 2018Follower
SSH abuse on port 22
I host a server behind my router and have port 22 forwarded so that I can SSH to the server. I noticed a couple days ago that I couldn't connect and after some troubleshooting decided to look at the ...
- Oct 31, 2018
> I host a server behind my router and have port 22 forwarded so that I
> can SSH to the server. [...]
You need to forward _some_ external port to port 22 on your server.
Using some external port other than 22 for that might amaze you by the
drop in the number of unwanted connection attempts you'll see.
> Is this normal for networks that have port 22 open for SSH?
That's been my experience.
> Is it likely someone is targeting my network or machine?
It's likely that many ones are trying every network on the Internet.
> Could this open port have been discovered via a port scan?
Sure, but many/most such attacks simply try port 22.
> Is it likely this is the reason I couldn't connect to my server?
I know nothing about that problem.
Years ago, I tried using external port 22. Big mistake. Complaining
to ISPs of offenders could easily be a full-time (unpaid) occupation.
Moved to external port 22 + N * 100, and get a few attempts per year.
"-p <port_number>" is your friend.
antinode
Oct 31, 2018Guru
> I host a server behind my router and have port 22 forwarded so that I
> can SSH to the server. [...]
You need to forward _some_ external port to port 22 on your server.
Using some external port other than 22 for that might amaze you by the
drop in the number of unwanted connection attempts you'll see.
> Is this normal for networks that have port 22 open for SSH?
That's been my experience.
> Is it likely someone is targeting my network or machine?
It's likely that many ones are trying every network on the Internet.
> Could this open port have been discovered via a port scan?
Sure, but many/most such attacks simply try port 22.
> Is it likely this is the reason I couldn't connect to my server?
I know nothing about that problem.
Years ago, I tried using external port 22. Big mistake. Complaining
to ISPs of offenders could easily be a full-time (unpaid) occupation.
Moved to external port 22 + N * 100, and get a few attempts per year.
"-p <port_number>" is your friend.