11-09-2009 07:45 AM - edited 03-11-2019 09:37 AM
ASA 8.0(4), ASDM 6.1(3) I'm trying to do ssh from 1 inside host to an outside host. Static NAT translates private IP to public IP, translates response back - all good. But my app won't allow custom port, outside host must have port 20022. So I Enable Port Translation, original port ssh, translated port 20022. ASDM Packet Tracer Tools says it works, shows my IP and port translation. BUT when I run the real thing I get no translation of IP or Port - sniffer outside of ASA shows my inside IP as source IP trying to route across the internet. So my static NAT works with no Port Translation, but quites entirely with Port Translation. What do I have wrong?
Solved! Go to Solution.
11-09-2009 03:16 PM
Do you mean that the outside host is listening on port 20022 instead of 22?
If that is the case then you need to do outside nat. Keep the static (inside,outside) for the inside host translation. If the outsider is listening on 20022 and the insider is trying to use 22 then the 22 destined to the outside needs to be translated to 20022. That would be done by using
static (outside,inside) tcp
I hope it helps.
PK
11-09-2009 03:16 PM
Do you mean that the outside host is listening on port 20022 instead of 22?
If that is the case then you need to do outside nat. Keep the static (inside,outside) for the inside host translation. If the outsider is listening on 20022 and the insider is trying to use 22 then the 22 destined to the outside needs to be translated to 20022. That would be done by using
static (outside,inside) tcp
I hope it helps.
PK
11-10-2009 05:58 AM
exactly what I needed, thanks very much. Now I need to cogitate a while, so I can understand why it's which when getting the job done.
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