- Posts: 21
- Thank you received: 0
static or nat
17 years 9 months ago #19599
by lomaree
static or nat was created by lomaree
i read in the cisco documentation that if i want users on the outside interface (lower security level) telnet to inside interface (higher security level) we should use static with access-list to allow the traffic. Now this is called translation, right?
now, what if you want the same instead that when the users on the outside interface (lower security level) telnet to inside interface (higher security level) we should be able to nat his IP from the one he is originally coming from e.g. 1.2.3.4 to say 172.16.1.53 and let me access the server inside whose IP Address is say 66.55.44.22
i believe there is something to do route because pix will not know 66.55.44.22 untill we define the route because PIX inside is on different ip subnet say 172.16.1.1
why i want this because outside user who is coming from IP 1.2.3.4 needs to be natted or translated to 172.16.1.53 because 66.55.44.22 only accepts connections from 172.16.1.53 therefore if he coming from 1.2.3.4 or anyother IP will not help.
So, Can i do this and how? i have read alot of cisco documents but i can't seems to find any solution or practice closer to my case.
i tried this on our pix and it didn't work
static (inside,outside) 66.55.44.22 172.16.1.53 netmask 255.255.255.255
access-list HELP permit ip host 172.16.1.53 host 1.2.3.4
now, what if you want the same instead that when the users on the outside interface (lower security level) telnet to inside interface (higher security level) we should be able to nat his IP from the one he is originally coming from e.g. 1.2.3.4 to say 172.16.1.53 and let me access the server inside whose IP Address is say 66.55.44.22
i believe there is something to do route because pix will not know 66.55.44.22 untill we define the route because PIX inside is on different ip subnet say 172.16.1.1
why i want this because outside user who is coming from IP 1.2.3.4 needs to be natted or translated to 172.16.1.53 because 66.55.44.22 only accepts connections from 172.16.1.53 therefore if he coming from 1.2.3.4 or anyother IP will not help.
So, Can i do this and how? i have read alot of cisco documents but i can't seems to find any solution or practice closer to my case.
i tried this on our pix and it didn't work
static (inside,outside) 66.55.44.22 172.16.1.53 netmask 255.255.255.255
access-list HELP permit ip host 172.16.1.53 host 1.2.3.4
Time to create page: 0.112 seconds