topic NAT from outside source to an internal server in Network Security

NAT from outside source to an internal server

Keith Brugnani — Tue, 12 Mar 2019 03:52:54 GMT

I have been working on this for months and I am still not able to get this working correctly. What I am trying to accomplish is to allow Usablenet to connect to our staging web server from the internet with an IP range for Usablenet.

The odd thing is this does not seem to be correct

object network web_staging_net

nat (web_staging,outside) dynamic interface

nat (web_staging,outside) source static obj-10.x.x.197 obj-209.x.x.97 destination static Useablenet Useablenet!

ACL

access-list outside_in extended permit tcp object-group Useablenet host 10.x.x.197 eq www

Any help will be greatly appreciated.

Re: NAT from outside source to an internal server

jj27 — Mon, 03 Mar 2014 15:08:48 GMT

What is the configuration of the object web_staging_net? Is it a subnet or single host?

I would recommend creating a separate host entry for 10.x.x.197 and removing the static NAT entry from the other object.

Something like this:

object network web_10.x.x.197

host 10.x.x.197

nat (web_staging,outside) static obj-209.x.x.97

NAT from outside source to an internal server

Keith Brugnani — Thu, 06 Mar 2014 12:48:13 GMT

It is a single host and web_staging is a network object group and I am just trying to create a one to one relationship.

For example

useablenet connects through 209.x.x.97 that translates to 10.x.x.97 and only allowing usablenet to connect

NAT from outside source to an internal server

jj27 — Thu, 06 Mar 2014 14:08:49 GMT

Please post the current output of:

show run object

show run object-group

show run nat

NAT from outside source to an internal server

Keith Brugnani — Thu, 06 Mar 2014 20:13:44 GMT

This has been resolved, it was simply a routing issue where the 209.x.x.97 was not routable.