<?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: PIX Multiple Inside Config in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852525#M954985</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Typo maybe, capital "G" in guest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group Guest_out in interface Guest &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Feb 2008 19:04:58 GMT</pubDate>
    <dc:creator>acomiskey</dc:creator>
    <dc:date>2008-02-14T19:04:58Z</dc:date>
    <item>
      <title>PIX Multiple Inside Config</title>
      <link>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852524#M954983</link>
      <description>&lt;P&gt;This should be straight forward, but for some reason I'm missing something.  I have a PIX with 6 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;E0 Outside&lt;/P&gt;&lt;P&gt;E1 Inside&lt;/P&gt;&lt;P&gt;E2 DMZ&lt;/P&gt;&lt;P&gt;E3 Guest&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Guest interface is the guest VLAN for the company and I want to allow access to the Internet while blocking all of our internal stuff.  Sample config is here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;int e0&lt;/P&gt;&lt;P&gt;nameif outside&lt;/P&gt;&lt;P&gt;ip add 1.1.1.1 255.255.255.0&lt;/P&gt;&lt;P&gt;security-level 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;int e1&lt;/P&gt;&lt;P&gt;nameif inside&lt;/P&gt;&lt;P&gt;ip add 10.10.10.1 255.255.255.0&lt;/P&gt;&lt;P&gt;security-level 100&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;int e2&lt;/P&gt;&lt;P&gt;nameif dmz&lt;/P&gt;&lt;P&gt;ip add 172.16.1.1 255.255.255.0&lt;/P&gt;&lt;P&gt;security level 50&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;int e3&lt;/P&gt;&lt;P&gt;nameif Guest&lt;/P&gt;&lt;P&gt;ip add 192.168.1.1 255.255.255.0&lt;/P&gt;&lt;P&gt;security level 90&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 1 0 0&lt;/P&gt;&lt;P&gt;nat (Guest) 2 0 0&lt;/P&gt;&lt;P&gt;global (outside) 1 1.1.1.2&lt;/P&gt;&lt;P&gt;global (outside) 2 1.1.1.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list Guest_out permit ip any any&lt;/P&gt;&lt;P&gt;access-gr Guest_out in interface guest&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Based on the config above, that should be enough to have the Guest vlan traffic PAT to 1.1.1.3 and have no issue going out?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Am I missing something?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:03:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852524#M954983</guid>
      <dc:creator>r.lusignan</dc:creator>
      <dc:date>2019-03-11T12:03:09Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Multiple Inside Config</title>
      <link>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852525#M954985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Typo maybe, capital "G" in guest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group Guest_out in interface Guest &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 19:04:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852525#M954985</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-02-14T19:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Multiple Inside Config</title>
      <link>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852526#M954988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Typo maybe, capital "G" in guest. Although that would not have prevented you from getting outside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group Guest_out in interface Guest &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 19:08:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852526#M954988</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-02-14T19:08:55Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Multiple Inside Config</title>
      <link>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852527#M954990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There isn't any issue with Typo...the config is absolutely good and would allow all IP traffic from Guest to go outside patting to 1.1.1.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;are you facing any issue ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 19:14:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852527#M954990</guid>
      <dc:creator>abinjola</dc:creator>
      <dc:date>2008-02-14T19:14:42Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Multiple Inside Config</title>
      <link>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852528#M954994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually there is a typo. And as I said, it would not have effected his ability to go outside.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 19:20:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852528#M954994</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-02-14T19:20:41Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Multiple Inside Config</title>
      <link>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852529#M954996</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes I am, return traffic is not being permitted back in.  I can see the xlate going through ie:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Built ICMP connection for faddr x.x.x.x/0 gaddr 1.1.1.3 laddr 192.168.1.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That outside IP i'm pinging is a router which is running debug ip icmp.  I can see the source address of the ping as the global PAT'd address on the Firewall.  So the config looks good, return traffic is not getting back through.  The ACL on the outside interface shouldn't be blocking the traffic as it was sourced from inside..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 19:21:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852529#M954996</guid>
      <dc:creator>r.lusignan</dc:creator>
      <dc:date>2008-02-14T19:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Multiple Inside Config</title>
      <link>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852530#M954998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is not the case with icmp. You must allow it in your outside acl on the firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This also serves as proof there was a typo, as he would have had to allow icmp as well in his Guest acl.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 19:28:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852530#M954998</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-02-14T19:28:24Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Multiple Inside Config</title>
      <link>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852531#M954999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;add a line permit icmp any any echo-reply on the outside access-list, if not then create one access-g on outside permitting icmp echo-reply&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you are correct firewall doesn't block traffic initiated from inside, however this is ICMP, firewall treats it stateless protocol and consider the return echo reply as different connection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They fixed this issue in code 7.0 and above with "Inspect Icmp" feature&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 19:29:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-multiple-inside-config/m-p/852531#M954999</guid>
      <dc:creator>abinjola</dc:creator>
      <dc:date>2008-02-14T19:29:52Z</dc:date>
    </item>
  </channel>
</rss>

