<?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: ACL Problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/acl-problem/m-p/876931#M954820</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any ideas why the PIX is doing this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Feb 2008 15:31:17 GMT</pubDate>
    <dc:creator>niro</dc:creator>
    <dc:date>2008-02-19T15:31:17Z</dc:date>
    <item>
      <title>ACL Problem</title>
      <link>https://community.cisco.com/t5/network-security/acl-problem/m-p/876930#M954819</link>
      <description>&lt;P&gt;I'm running a PIX 525 with software version 7.2(2)...I'm having a weird acl problem.  I've inserted a few lines to the beginning of the acl inside_access_out, however the firewall seems to ignore them and just skip to the end.  Here is what I get from the show access-list command (My IP is 10.14.2.39):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_out; 13 elements&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 1 extended permit ip host 10.14.2.39 host x.x.x.x(hitcnt=0) 0x7a832d4&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 2 extended permit ip host 10.14.2.39 any (hitcnt=0) 0x28f7c337&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 3 extended permit tcp host 10.11.2.184 host x.x.x.x eq https (hitcnt=0) 0x428081&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 4 extended permit ip host 10.11.2.184 host x.x.x.x (hitcnt=0) 0x331c68af&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 5 extended permit ip host 10.14.2.30 host x.x.x.x (hitcnt=0) 0x2a424acd&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 6 extended permit ip host 10.14.2.68 host x.x.x.x (hitcnt=0) 0xc049a2b&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 7 extended permit ip host 10.14.2.52 host x.x.x.x (hitcnt=0) 0x8be52cb1&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 8 extended permit ip 192.168.14.0 255.255.255.0 host x.x.x.x (hitcnt=0) 0xfbe0b816&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 9 extended permit tcp any any eq www (hitcnt=10659185) 0xe7714247&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 10 extended permit tcp any any eq https (hitcnt=1505514) 0xec7b1d&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 11 extended permit icmp any any (hitcnt=464352) 0x4416cbd7&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 12 extended permit udp any any (hitcnt=10074659) 0x9c2207a6&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 13 extended permit ip any any (hitcnt=2341790) 0xbc49651&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group inside_access_out out interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I replaced some IP addresses with x.x.x.x.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you can see all the lines before the tcp any any www line get a hit count of 0.  Any idea why that would be?  I know I've initiated www traffic (and many other types of traffic), yet it doesn't seem to register.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:04:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-problem/m-p/876930#M954819</guid>
      <dc:creator>niro</dc:creator>
      <dc:date>2019-03-11T12:04:18Z</dc:date>
    </item>
    <item>
      <title>Re: ACL Problem</title>
      <link>https://community.cisco.com/t5/network-security/acl-problem/m-p/876931#M954820</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any ideas why the PIX is doing this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2008 15:31:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-problem/m-p/876931#M954820</guid>
      <dc:creator>niro</dc:creator>
      <dc:date>2008-02-19T15:31:17Z</dc:date>
    </item>
    <item>
      <title>Re: ACL Problem</title>
      <link>https://community.cisco.com/t5/network-security/acl-problem/m-p/876932#M954821</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe this is because since your acl is applied out of the outside interface, your source address is no longer 10.14.2.39, it is whatever you are natting to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore, your acl would need to be...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_out line 1 extended permit ip host &lt;NATTED.ADDRESS&gt; host x.x.x.x&lt;/NATTED.ADDRESS&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you wanted to use the 10. address you could apply the acl into the inside interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group inside_access_out in interface inside&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2008 16:25:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-problem/m-p/876932#M954821</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-02-19T16:25:38Z</dc:date>
    </item>
    <item>
      <title>Re: ACL Problem</title>
      <link>https://community.cisco.com/t5/network-security/acl-problem/m-p/876933#M954822</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;simple..thats because the traffic not matching the ACLs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;do this set this capture on Pix which would verify this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;acsess-l abc permit ip host 10.x.x.x host x.x.x.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;capture cpo access-l abc packet-length 1518 interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;replace the hosts in the above ACL with actual hosts from access-lists where you don't have hit count&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now get me &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh cap cpo&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2008 16:29:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-problem/m-p/876933#M954822</guid>
      <dc:creator>abinjola</dc:creator>
      <dc:date>2008-02-19T16:29:02Z</dc:date>
    </item>
    <item>
      <title>Re: ACL Problem</title>
      <link>https://community.cisco.com/t5/network-security/acl-problem/m-p/876934#M954823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ah I think you're right...I'm going to try applying the acl for inbound filtering on the inside interface instead.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, I'll try that tonight.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2008 17:07:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-problem/m-p/876934#M954823</guid>
      <dc:creator>niro</dc:creator>
      <dc:date>2008-02-19T17:07:43Z</dc:date>
    </item>
  </channel>
</rss>

