<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Identity NAT on Pix using the Static command in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411211#M557630</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To allow traffic from a lower security level interface to a higher security level interface, two things are required:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.  An ACL that permits the traffic from source to destination for a particular service.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. A static statement that instructs the PIX how to translate the destination ip address (or source in the case of higher security --&amp;gt; lower security traffic).  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your particular instance, because the destination ip address presented to the lower security level interface is the same as the physically configured IP address on the destination host, and because a static statement is still required, the static statement will reference the same ip:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (high,low) x.x.x.x x.x.x.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another common situation in which this is used, is for accomodating traffic sourced from a dmz interface to an inside network, e.g., web server to db server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Jun 2005 01:22:08 GMT</pubDate>
    <dc:creator>rshedlow</dc:creator>
    <dc:date>2005-06-02T01:22:08Z</dc:date>
    <item>
      <title>Identity NAT on Pix using the Static command</title>
      <link>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411208#M557622</link>
      <description>&lt;P&gt;I've seen this configuration on CCO and I'm not sure what it means. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside, outside) 10.1.1.1 10.1.1.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: The same IP is used for both the public and private address. In what scenario would this be used and what specifically does it accomplish?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:10:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411208#M557622</guid>
      <dc:creator>rsalomon</dc:creator>
      <dc:date>2020-02-21T08:10:52Z</dc:date>
    </item>
    <item>
      <title>Re: Identity NAT on Pix using the Static command</title>
      <link>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411209#M557624</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Typically used in situations wehre you dont have a private ip assigned to say your web server in the DMZ. A host trying to reach this server from the internet will get the DNS address resolved as x.x.x.x. When this traffic hits the pix, the pix needs to translate the destination address as x.x.x.x. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) x.x.x.x x.x.x.x&lt;/P&gt;&lt;P&gt;conduit or acl (to specify appropriate port)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: You need a conduit or acl to permit a specific port or protocol to the server x.x.x.x specified above.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Jun 2005 01:07:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411209#M557624</guid>
      <dc:creator>thisisshanky</dc:creator>
      <dc:date>2005-06-01T01:07:04Z</dc:date>
    </item>
    <item>
      <title>Re: Identity NAT on Pix using the Static command</title>
      <link>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411210#M557627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the quick response but I have one question though. If my web server on the DMZ has a public IP then a static NAT is not required. My internet router only needs a static route to that subnet and my pix, with the use of an ACL or conduit simply allows the necessary traffic to that host. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess I don't see how the DNS resolution comes in. Please clarify&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Jun 2005 11:55:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411210#M557627</guid>
      <dc:creator>rsalomon</dc:creator>
      <dc:date>2005-06-01T11:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: Identity NAT on Pix using the Static command</title>
      <link>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411211#M557630</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To allow traffic from a lower security level interface to a higher security level interface, two things are required:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.  An ACL that permits the traffic from source to destination for a particular service.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. A static statement that instructs the PIX how to translate the destination ip address (or source in the case of higher security --&amp;gt; lower security traffic).  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your particular instance, because the destination ip address presented to the lower security level interface is the same as the physically configured IP address on the destination host, and because a static statement is still required, the static statement will reference the same ip:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (high,low) x.x.x.x x.x.x.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another common situation in which this is used, is for accomodating traffic sourced from a dmz interface to an inside network, e.g., web server to db server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jun 2005 01:22:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411211#M557630</guid>
      <dc:creator>rshedlow</dc:creator>
      <dc:date>2005-06-02T01:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: Identity NAT on Pix using the Static command</title>
      <link>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411212#M557634</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, it does help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jun 2005 12:07:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/identity-nat-on-pix-using-the-static-command/m-p/411212#M557634</guid>
      <dc:creator>rsalomon</dc:creator>
      <dc:date>2005-06-02T12:07:09Z</dc:date>
    </item>
  </channel>
</rss>

