<?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: How you call this type STATIC ? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091603#M895646</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 01 Oct 2008 18:07:15 GMT</pubDate>
    <dc:creator>amarula115</dc:creator>
    <dc:date>2008-10-01T18:07:15Z</dc:date>
    <item>
      <title>How you call this type STATIC ?</title>
      <link>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091600#M895641</link>
      <description>&lt;P&gt;How you call properly this type of STATIC:&lt;/P&gt;&lt;P&gt;static (inside,outside) 172.16.32.0 172.16.32.0 netmask 255.255.255.0&lt;/P&gt;&lt;P&gt;and what is the purpose of such STATIC?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:51:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091600#M895641</guid>
      <dc:creator>amarula115</dc:creator>
      <dc:date>2019-03-11T13:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: How you call this type STATIC ?</title>
      <link>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091601#M895642</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is static because the translation is not dynamically created when traffic goes through the firewall. This a permanent translation that you want all the time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The purpose is because of an oddity with the pix/asa device. To allow traffic from a lower to a higher security level interface you need to &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i) allow it in an access-list&lt;/P&gt;&lt;P&gt;ii) have a NAT statement for it&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On most other firewalls you only NAT if you want to represent one address as another address. On pix/asa even if you don't want to change the address because of ii) you must have a nat statement and that is why you have it. It is almost a way of saying to the pix/asa i don't want to NAT for 172.16.32.0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As i say it is an oddity of the pix/asa firewalls.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Oct 2008 11:12:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091601#M895642</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2008-10-01T11:12:20Z</dc:date>
    </item>
    <item>
      <title>Re: How you call this type STATIC ?</title>
      <link>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091602#M895644</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you either use static (i,o) same-ip same-ip&lt;/P&gt;&lt;P&gt;or nat(inside) 0 access-list with Pix version &lt;/P&gt;&lt;P&gt;6.3(x).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With version 7.x, you do not have to do this&lt;/P&gt;&lt;P&gt;if you have "no nat-control".  That will&lt;/P&gt;&lt;P&gt;allow traffic from high to low.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HOWEVER, AS SOON AS YOU HAVE nat (inside) 1 x x&lt;/P&gt;&lt;P&gt;and global (outside) 1 interface, "NO NAT-CONTROL"  WILL BECOME USELESS FOR &lt;/P&gt;&lt;P&gt;INTERFACE "INSIDE"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Oct 2008 14:00:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091602#M895644</guid>
      <dc:creator>cisco24x7</dc:creator>
      <dc:date>2008-10-01T14:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: How you call this type STATIC ?</title>
      <link>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091603#M895646</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Oct 2008 18:07:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091603#M895646</guid>
      <dc:creator>amarula115</dc:creator>
      <dc:date>2008-10-01T18:07:15Z</dc:date>
    </item>
    <item>
      <title>Re: How you call this type STATIC ?</title>
      <link>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091604#M895649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Oct 2008 18:07:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-you-call-this-type-static/m-p/1091604#M895649</guid>
      <dc:creator>amarula115</dc:creator>
      <dc:date>2008-10-01T18:07:35Z</dc:date>
    </item>
  </channel>
</rss>

