ssh port 22 forwarding on RBK53

Port forwarding is affected by several factors:

• There has to be a device on the LAN with that port open and willing to accept connections.  When ports are forwarded, the router simply copies data packets (including TCP connection requests) and addresses them to the device in the forwarding table.  It is very common for device firewalls to refuse to accept connections.  Windows Firewall, for example, has separate settings for private (the LAN subnet) and public (the reset of the IP space).  Several times I have been confident that a server on my Windows computer was working because I could connect to it from the LAN, but then found it would not accept connections from the internet.
• Packets have to reach the router.  If, for example, the router is connected to another router (such as an ISP combination modem/router), then packets have to get through that router first before the second router can deal with them.
  One quick way to determine what is happening is to use one of the "am I open" web sites on the internet, such as ShieldsUp! by Gibson Research: https://www.grc.com/shieldsup  I like this web site because I distinguishes between ports that are:
  • Open (accepting connections)
  • Closed (rejecting connections)
  • Stealth (no response of any kind. maybe there's not even a computer there?)
• On any of these "am I open?" checks, the IP address reported by the site must match the public IP address reported in the Orbi web administration Advanced Tab home page under Internet Port.  If they do not match, there is almost certainly a router in the way.

Probably a good idea here to ask the brand/model of ISP device the router is connected to.