<?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 Firewall configuration in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441272#M531499</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;just wondering if there is a route pointing to isa for the subnet 172.18.1.0 on the pix.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. with the current pix config,&lt;/P&gt;&lt;P&gt;route inside 172.18.1.0 255.255.255.0 172.16.1.5&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 25 Oct 2005 00:41:45 GMT</pubDate>
    <dc:creator>jackko</dc:creator>
    <dc:date>2005-10-25T00:41:45Z</dc:date>
    <item>
      <title>PIX Firewall configuration</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441268#M531489</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;I need to have your suggestion on the following issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have pix firewall installed.The inside interface address is 172.16.1.0 /24&lt;/P&gt;&lt;P&gt;This pix inside is connected to the outside interface of ISA server. The ISA inside connected to the router eth0 interface. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;172.16.1.1(PIXINSIDE)-172.16.1.5(ISA-OUTSIDE)-172.18.1.5 (ISA-Inside)-172.18.1.1 (router eth0)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is I can ping all the lower interface ip being in 172.16.1.0 network i.e pix inside network, but I can not ping the same lower interfaces from the 172.18.1.0 network which is behind ISA Firewall.Please note that the ISA act as brige all the ports are opened both in &amp;amp; out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I used NAT (inside 0 0 0 0 0 &lt;/P&gt;&lt;P&gt;also NAT (inside) 0 access-list no-nat with&lt;/P&gt;&lt;P&gt;access-list no-nat permit ip 172.18.10 255.255.255.0 any ---&amp;gt; NAT EXEMPTION&lt;/P&gt;&lt;P&gt;nO RESULT&lt;/P&gt;&lt;P&gt;Please reply asasp.&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;swamy&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:28:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441268#M531489</guid>
      <dc:creator>arumugasamy</dc:creator>
      <dc:date>2020-02-21T08:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Firewall configuration</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441269#M531491</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you mentioned, "but I can not ping the same lower interfaces from the 172.18.1.0 network". just wondering if you are referring to the subnet that connected to the pix outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if so, then inbound acl is required for echo response on the pix. the reason being pix by default doesn't perform stateful inspection on icmp.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. one way is to configure inbound acl&lt;/P&gt;&lt;P&gt;access-list 100 permit icmp any any eq echo-reply&lt;/P&gt;&lt;P&gt;access-group 100 in interface outside&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 22 Oct 2005 12:19:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441269#M531491</guid>
      <dc:creator>jackko</dc:creator>
      <dc:date>2005-10-22T12:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Firewall configuration</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441270#M531494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mr.Jackko,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 172.18.1.0 network is behind ISA server. I can explain that the ISA server is between the PIX firewall and the 172.18.1.0 network. ISA inside NIC connected to the 172.18.1.0 network and the ISA server outsdie NIC connected to the PIX Inside network that is 172.16.1.0. other PIX's interfaces are DMZ1, DMZ2, DMZ3.We can ping all the dmzs from 172.16.1.0 not from 172.18.1.0. &lt;/P&gt;&lt;P&gt;In the pix firewall all high to lower interfaces are configured with identity NAT (NAT 0 )&lt;/P&gt;&lt;P&gt;Please help me&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Swamy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Oct 2005 18:13:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441270#M531494</guid>
      <dc:creator>arumugasamy</dc:creator>
      <dc:date>2005-10-24T18:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Firewall configuration</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441271#M531497</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had something like this happen to us.  Are you maybe missing a route statement.  Even though you may have an access-list, you will still need a route statement.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Oct 2005 22:24:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441271#M531497</guid>
      <dc:creator>flopez</dc:creator>
      <dc:date>2005-10-24T22:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Firewall configuration</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441272#M531499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;just wondering if there is a route pointing to isa for the subnet 172.18.1.0 on the pix.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. with the current pix config,&lt;/P&gt;&lt;P&gt;route inside 172.18.1.0 255.255.255.0 172.16.1.5&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Oct 2005 00:41:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441272#M531499</guid>
      <dc:creator>jackko</dc:creator>
      <dc:date>2005-10-25T00:41:45Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Firewall configuration</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441273#M531501</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;just wondering how you go.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Nov 2005 11:19:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-configuration/m-p/441273#M531501</guid>
      <dc:creator>jackko</dc:creator>
      <dc:date>2005-11-03T11:19:22Z</dc:date>
    </item>
  </channel>
</rss>

