<?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: Best way to config a PIX without NAT in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128804#M615146</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you need a static and an ACL for outside users to initiate a connection inside:&lt;/P&gt;&lt;P&gt;static(inside,outside) &lt;HIGH&gt; &lt;HIGH&gt;&lt;/HIGH&gt;&lt;/HIGH&gt;&lt;/P&gt;&lt;P&gt;access-list 101 permit ip any &lt;HIGH&gt;&lt;/HIGH&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group 101 in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 Sep 2003 10:41:44 GMT</pubDate>
    <dc:creator>atdhingr</dc:creator>
    <dc:date>2003-09-19T10:41:44Z</dc:date>
    <item>
      <title>Best way to config a PIX without NAT</title>
      <link>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128800#M615139</link>
      <description>&lt;P&gt;I have tried, "NAT (inside) 0 x.x.x.x 255.255.255.0"&lt;/P&gt;&lt;P&gt;it's working, but some how outside host cannot access anything behind the pix unless the inside machine start a session to outside first. &lt;/P&gt;&lt;P&gt;Any idea why this happen? is this normal?&lt;/P&gt;&lt;P&gt;any idea would be appreciate.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:59:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128800#M615139</guid>
      <dc:creator>tkpsimon</dc:creator>
      <dc:date>2020-02-21T06:59:07Z</dc:date>
    </item>
    <item>
      <title>Re: Best way to config a PIX without NAT</title>
      <link>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128801#M615141</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is normal - you need to write an access list to open ports, and apply it to the outside interface&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2003 15:36:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128801#M615141</guid>
      <dc:creator>mostiguy</dc:creator>
      <dc:date>2003-09-10T15:36:15Z</dc:date>
    </item>
    <item>
      <title>Re: Best way to config a PIX without NAT</title>
      <link>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128802#M615142</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your reply, &lt;/P&gt;&lt;P&gt;actually i already have ACL apply on the outside interface, let set permit icmp any any. But problem still happen to be that way, always require inside host to initial traffic, then outside can access. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand this is not a big of issue, but for web server, it's kind of annoying. We always need to send out icmp to outside. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2003 15:42:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128802#M615142</guid>
      <dc:creator>tkpsimon</dc:creator>
      <dc:date>2003-09-10T15:42:14Z</dc:date>
    </item>
    <item>
      <title>Re: Best way to config a PIX without NAT</title>
      <link>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128803#M615143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need to a nat 0 rule with an access-list for this to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat 0 (inside) access-list no-nat&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list no-nat permit ip 10.10.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Sep 2003 14:39:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128803#M615143</guid>
      <dc:creator>r.sneekes</dc:creator>
      <dc:date>2003-09-18T14:39:22Z</dc:date>
    </item>
    <item>
      <title>Re: Best way to config a PIX without NAT</title>
      <link>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128804#M615146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you need a static and an ACL for outside users to initiate a connection inside:&lt;/P&gt;&lt;P&gt;static(inside,outside) &lt;HIGH&gt; &lt;HIGH&gt;&lt;/HIGH&gt;&lt;/HIGH&gt;&lt;/P&gt;&lt;P&gt;access-list 101 permit ip any &lt;HIGH&gt;&lt;/HIGH&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group 101 in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Sep 2003 10:41:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/best-way-to-config-a-pix-without-nat/m-p/128804#M615146</guid>
      <dc:creator>atdhingr</dc:creator>
      <dc:date>2003-09-19T10:41:44Z</dc:date>
    </item>
  </channel>
</rss>

