<?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 PIx Configuration in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-configuration/m-p/159187#M615299</link>
    <description>&lt;P&gt;I am just started to configure the PIX Firewall.&lt;/P&gt;&lt;P&gt;But I am in  confusion.&lt;/P&gt;&lt;P&gt;Here is the conf file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX Version 6.2(2)&lt;/P&gt;&lt;P&gt;nameif ethernet0 backbone_251 security0&lt;/P&gt;&lt;P&gt;nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;nameif ethernet2 intf2 security10&lt;/P&gt;&lt;P&gt;nameif ethernet3 intf3 security15&lt;/P&gt;&lt;P&gt;nameif ethernet4 intf4 security20&lt;/P&gt;&lt;P&gt;nameif ethernet5 intf5 security25&lt;/P&gt;&lt;P&gt;hostname dmg-fw&lt;/P&gt;&lt;P&gt;domain-name mos.com.np&lt;/P&gt;&lt;P&gt;access-list 101 permit icmp any any &lt;/P&gt;&lt;P&gt;acess-list 110 permit tcp host 202.52.227.18 host 202.52.227.2 eq smtp &lt;/P&gt;&lt;P&gt;access-list 111 permit tcp host 202.52.227.10 host 202.52.227.18 eq smtp &lt;/P&gt;&lt;P&gt;access-list 111 permit tcp host 202.52.227.10 host 202.52.227.2 eq smtp &lt;/P&gt;&lt;P&gt;interface ethernet0 10baset&lt;/P&gt;&lt;P&gt;interface ethernet1 10baset&lt;/P&gt;&lt;P&gt;interface ethernet2 10baset&lt;/P&gt;&lt;P&gt;interface ethernet3 10baset&lt;/P&gt;&lt;P&gt;interface ethernet4 10baset shutdown&lt;/P&gt;&lt;P&gt;interface ethernet5 10baset shutdown&lt;/P&gt;&lt;P&gt;mtu backbone_251 1500&lt;/P&gt;&lt;P&gt;ip address backbone_251 202.52.251.3 255.255.255.0&lt;/P&gt;&lt;P&gt;ip address inside 202.52.227.1 255.255.255.248&lt;/P&gt;&lt;P&gt;ip address intf2 202.52.227.9 255.255.255.248&lt;/P&gt;&lt;P&gt;ip address intf3 202.52.227.17 255.255.255.248&lt;/P&gt;&lt;P&gt;ip address intf4 127.0.0.1 255.255.255.255&lt;/P&gt;&lt;P&gt;ip address intf5 127.0.0.1 255.255.255.255&lt;/P&gt;&lt;P&gt;nat (inside) 0 0.0.0.0 0.0.0.0 0 0&lt;/P&gt;&lt;P&gt;static (intf3,backbone_251) 202.52.227.16 202.52.227.16 netmask 255.255.255.248 0 0 &lt;/P&gt;&lt;P&gt;static (intf3,intf2) 202.52.227.16 202.52.227.16 netmask 255.255.255.248 0 0 &lt;/P&gt;&lt;P&gt;static (intf2,backbone_251) 202.52.227.8 202.52.227.8 netmask 255.255.255.248 0 0 &lt;/P&gt;&lt;P&gt;static (inside,intf2) 202.52.227.0 202.52.227.0 netmask 255.255.255.248 0 0 &lt;/P&gt;&lt;P&gt;static (inside,intf3) 202.52.227.0 202.52.227.0 netmask 255.255.255.248 0 0 &lt;/P&gt;&lt;P&gt;access-group 101 in interface backbone_251&lt;/P&gt;&lt;P&gt;access-group 111 in interface intf2&lt;/P&gt;&lt;P&gt;access-group 110 in interface intf3&lt;/P&gt;&lt;P&gt;route backbone_251 0.0.0.0 0.0.0.0 202.52.251.1 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But as soon as I apply the 110 in interface intf3&lt;/P&gt;&lt;P&gt;It obey the rule&lt;/P&gt;&lt;P&gt;cess-list 110 permit tcp host 202.52.227.18 host 202.52.227.2 eq smtp &lt;/P&gt;&lt;P&gt;But it close the connection to lower interface.For example I can not Browse from intf3.Now should I add the access-list to permit in lower interface??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me&lt;/P&gt;&lt;P&gt;Ishwar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 06:56:20 GMT</pubDate>
    <dc:creator>ishwar</dc:creator>
    <dc:date>2020-02-21T06:56:20Z</dc:date>
    <item>
      <title>PIx Configuration</title>
      <link>https://community.cisco.com/t5/network-security/pix-configuration/m-p/159187#M615299</link>
      <description>&lt;P&gt;I am just started to configure the PIX Firewall.&lt;/P&gt;&lt;P&gt;But I am in  confusion.&lt;/P&gt;&lt;P&gt;Here is the conf file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX Version 6.2(2)&lt;/P&gt;&lt;P&gt;nameif ethernet0 backbone_251 security0&lt;/P&gt;&lt;P&gt;nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;nameif ethernet2 intf2 security10&lt;/P&gt;&lt;P&gt;nameif ethernet3 intf3 security15&lt;/P&gt;&lt;P&gt;nameif ethernet4 intf4 security20&lt;/P&gt;&lt;P&gt;nameif ethernet5 intf5 security25&lt;/P&gt;&lt;P&gt;hostname dmg-fw&lt;/P&gt;&lt;P&gt;domain-name mos.com.np&lt;/P&gt;&lt;P&gt;access-list 101 permit icmp any any &lt;/P&gt;&lt;P&gt;acess-list 110 permit tcp host 202.52.227.18 host 202.52.227.2 eq smtp &lt;/P&gt;&lt;P&gt;access-list 111 permit tcp host 202.52.227.10 host 202.52.227.18 eq smtp &lt;/P&gt;&lt;P&gt;access-list 111 permit tcp host 202.52.227.10 host 202.52.227.2 eq smtp &lt;/P&gt;&lt;P&gt;interface ethernet0 10baset&lt;/P&gt;&lt;P&gt;interface ethernet1 10baset&lt;/P&gt;&lt;P&gt;interface ethernet2 10baset&lt;/P&gt;&lt;P&gt;interface ethernet3 10baset&lt;/P&gt;&lt;P&gt;interface ethernet4 10baset shutdown&lt;/P&gt;&lt;P&gt;interface ethernet5 10baset shutdown&lt;/P&gt;&lt;P&gt;mtu backbone_251 1500&lt;/P&gt;&lt;P&gt;ip address backbone_251 202.52.251.3 255.255.255.0&lt;/P&gt;&lt;P&gt;ip address inside 202.52.227.1 255.255.255.248&lt;/P&gt;&lt;P&gt;ip address intf2 202.52.227.9 255.255.255.248&lt;/P&gt;&lt;P&gt;ip address intf3 202.52.227.17 255.255.255.248&lt;/P&gt;&lt;P&gt;ip address intf4 127.0.0.1 255.255.255.255&lt;/P&gt;&lt;P&gt;ip address intf5 127.0.0.1 255.255.255.255&lt;/P&gt;&lt;P&gt;nat (inside) 0 0.0.0.0 0.0.0.0 0 0&lt;/P&gt;&lt;P&gt;static (intf3,backbone_251) 202.52.227.16 202.52.227.16 netmask 255.255.255.248 0 0 &lt;/P&gt;&lt;P&gt;static (intf3,intf2) 202.52.227.16 202.52.227.16 netmask 255.255.255.248 0 0 &lt;/P&gt;&lt;P&gt;static (intf2,backbone_251) 202.52.227.8 202.52.227.8 netmask 255.255.255.248 0 0 &lt;/P&gt;&lt;P&gt;static (inside,intf2) 202.52.227.0 202.52.227.0 netmask 255.255.255.248 0 0 &lt;/P&gt;&lt;P&gt;static (inside,intf3) 202.52.227.0 202.52.227.0 netmask 255.255.255.248 0 0 &lt;/P&gt;&lt;P&gt;access-group 101 in interface backbone_251&lt;/P&gt;&lt;P&gt;access-group 111 in interface intf2&lt;/P&gt;&lt;P&gt;access-group 110 in interface intf3&lt;/P&gt;&lt;P&gt;route backbone_251 0.0.0.0 0.0.0.0 202.52.251.1 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But as soon as I apply the 110 in interface intf3&lt;/P&gt;&lt;P&gt;It obey the rule&lt;/P&gt;&lt;P&gt;cess-list 110 permit tcp host 202.52.227.18 host 202.52.227.2 eq smtp &lt;/P&gt;&lt;P&gt;But it close the connection to lower interface.For example I can not Browse from intf3.Now should I add the access-list to permit in lower interface??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me&lt;/P&gt;&lt;P&gt;Ishwar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:56:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-configuration/m-p/159187#M615299</guid>
      <dc:creator>ishwar</dc:creator>
      <dc:date>2020-02-21T06:56:20Z</dc:date>
    </item>
    <item>
      <title>Re: PIx Configuration</title>
      <link>https://community.cisco.com/t5/network-security/pix-configuration/m-p/159188#M615300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ishwar,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To your question, yes, you must configure access-list to lower interface.  At  the moment, you use access-list on an interface, you must specify all rules to permit/deny any traffic passing through this interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Aug 2003 13:28:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-configuration/m-p/159188#M615300</guid>
      <dc:creator>bdube</dc:creator>
      <dc:date>2003-08-17T13:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: PIx Configuration</title>
      <link>https://community.cisco.com/t5/network-security/pix-configuration/m-p/159189#M615301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ben,&lt;/P&gt;&lt;P&gt;Thanks a lot.&lt;/P&gt;&lt;P&gt;Now is there any way to configure PIX that&lt;/P&gt;&lt;P&gt;It does not affect the default behavior when I apply the rule to access in  higher interface so that I do not have to add long access-list again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ishwar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Aug 2003 03:21:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-configuration/m-p/159189#M615301</guid>
      <dc:creator>ishwar</dc:creator>
      <dc:date>2003-08-18T03:21:18Z</dc:date>
    </item>
    <item>
      <title>Re: PIx Configuration</title>
      <link>https://community.cisco.com/t5/network-security/pix-configuration/m-p/159190#M615302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately, ACL affects default behavior.  Then, you use it or not.  But, since your access-list only apply to SMTP servers between inside and DMZ, you can use "NAT 0 access-list id" between those servers.  The "NAT 0 access-list id" is apply to inside interface and leaves incoming or outgoing traffics that match the access-list specified.  That way, i suppose you can simply remove your ACL 110 applied to int3, to keep default behavior (browsing), and permit traffics between your SMTP servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Aug 2003 10:49:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-configuration/m-p/159190#M615302</guid>
      <dc:creator>bdube</dc:creator>
      <dc:date>2003-08-18T10:49:36Z</dc:date>
    </item>
  </channel>
</rss>

