09-29-2011 01:36 PM - edited 03-07-2019 02:31 AM
Hi all,
i'm would like to set a non standard ssh port with the following cmd:
1) ip nat inside source static tcp 192.168.1.45 22 MY.PUBLIC.IP.3 12345 extendable
but it doesn't seems to work, if i do
2) ip nat inside source static tcp 192.168.1.45 789 MY.PUBLIC.IP.3 12345 extendable
or:
3) ip nat inside source static tcp 192.168.1.45 12345 MY.PUBLIC.IP.3 12345 extendable
it works!
in all the above cases i'm making sure that there is a ssh server running on the ports 22, 789 and 12345 and that there is the corresponding firewall rule to make the traffic pass through.
does port 22 requires some additional configuration?
thanks,
kky
02-08-2012 03:01 PM
its seems that if the router has an ssh service it doesn't allow to set nat on ssh, i've resolved setting a dmz ssh server on a non standard port.
Let me know if you have a different experience,
thanks!!
03-05-2020 08:19 PM
Hello,
I am experiencing the same behavior, did you find a solution?
Thanks
03-06-2020 01:05 AM
Hello,
try and map ssh t a different port, e.g. (in global config mode):
ip port-map ssh port 12345
then try the NAT statement again...
03-06-2020 07:33 PM
03-07-2020 06:22 AM
Hi,
Can you define what is your configuration and what you want to achieve that's not working? "ip port-map" is not used for NAT. You can, if you want, remove the default port-mappings for a protocol and add your own: first remove the default mapping via "no ip port-map ssh" and add your custom ones via "ip port-map ssh port xyz".
Regards,
Cristian Matei.
03-07-2020 07:45 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide