Port forwarding not working for port 22 (even though 2200 for examle works)

[jelmew]

Hi all,

I am probably just missing something, but port forwarding on port 22 (extern and intern) does not seem to work. If I change the extern port to something else (like 2200) it does work. I have already disabled UPnP. Am I still missing something?

Kind regards,

Jelmew

[jelmew · Accepted solution]

Hi,

I solved it. If I only set tcp for external port 22, it works flawlessly. I know higher ports are better, but I'm forced to use this port due to the fact that my work only has a few outbound ports whitelisted. Fortunately, I'm using private/public key authentication and fail2ban, so it is not too bad.

[antinode]

> Model: R7000P|Nighthawk AC2300 Smart WiFi Router with MU-MIMO

   Is that accurate?  Firmware version?

> [...] port forwarding on port 22 (extern and intern) does not seem to
> work.

   What's the failure?

   Assuming that your (invisible) port-forwarding rule is correct, then
I'd expect it to work.  But, it's Netgear firmware, so many things are
possible.

   Years ago, I actually passed external port 22 to an internal port 22,
but there were so many attacks on that port that I changed my external
port for SSH from 22 to something different, and haven't looked back.
That was so long ago that I can't even be sure which router I used then
(but it definitely wasn't an R7000P).  Although 22 -> 22 should work,
even if it did, I'd really advise against doing it.  Is there any
SSH-related application which doesn't let you specify a different port?
Any other (good) reason to do it?

[jelmew · Accepted solution]

Hi,

I solved it. If I only set tcp for external port 22, it works flawlessly. I know higher ports are better, but I'm forced to use this port due to the fact that my work only has a few outbound ports whitelisted. Fortunately, I'm using private/public key authentication and fail2ban, so it is not too bad.