<?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 ASA exclude in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-exclude/m-p/2663740#M195974</link>
    <description>&lt;P&gt;Hi community&lt;/P&gt;&lt;P&gt;One of our customers is facing a porblem with the default HTTP inspection (page loads slowly). I now tried to exclude this specific range via the MPF of the ASA (IPs are just for example):&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family:courier new,courier,monospace;"&gt;access-list http-inspection extended deny tcp host 172.22.10.50 host 8.8.8.8 eq www&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family:courier new,courier,monospace;"&gt;class-map http-inspection&lt;BR /&gt;&amp;nbsp;match access-list http-inspection&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;policy-map global_policy&lt;BR /&gt;&amp;nbsp;class inspection_default&lt;BR /&gt;&amp;nbsp; inspect icmp&lt;BR /&gt;&amp;nbsp; &amp;lt;snip&amp;gt;&lt;BR /&gt;&amp;nbsp; inspect ip-options&lt;BR /&gt;&amp;nbsp;class http-inspection&lt;BR /&gt;&amp;nbsp; inspect http&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The packet-tracer shows, that with this ACL only traffic from 172.22.10.50 to 8.8.8.8 is inspected. Traffic from 172.22.10.50 to 7.7.7.7 for example is not expected. I tried to modify the ACL to a permit:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family:courier new,courier,monospace;"&gt;access-list http-inspection extended permit tcp host 172.22.10.50 host 8.8.8.8 eq www&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family:arial,helvetica,sans-serif;"&gt;In the packet-tracer this shows me the exact same result. I checked this option in the ASDM. There is an option for "DO NOT MATCH" and the ACL is with a deny statement. From this I&amp;nbsp;would assume that it is possible to exclude some traffic from the inspection.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone a solution on this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Matthias&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:39:31 GMT</pubDate>
    <dc:creator>Matthias Jeker</dc:creator>
    <dc:date>2019-03-12T05:39:31Z</dc:date>
    <item>
      <title>ASA exclude</title>
      <link>https://community.cisco.com/t5/network-security/asa-exclude/m-p/2663740#M195974</link>
      <description>&lt;P&gt;Hi community&lt;/P&gt;&lt;P&gt;One of our customers is facing a porblem with the default HTTP inspection (page loads slowly). I now tried to exclude this specific range via the MPF of the ASA (IPs are just for example):&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family:courier new,courier,monospace;"&gt;access-list http-inspection extended deny tcp host 172.22.10.50 host 8.8.8.8 eq www&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family:courier new,courier,monospace;"&gt;class-map http-inspection&lt;BR /&gt;&amp;nbsp;match access-list http-inspection&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;policy-map global_policy&lt;BR /&gt;&amp;nbsp;class inspection_default&lt;BR /&gt;&amp;nbsp; inspect icmp&lt;BR /&gt;&amp;nbsp; &amp;lt;snip&amp;gt;&lt;BR /&gt;&amp;nbsp; inspect ip-options&lt;BR /&gt;&amp;nbsp;class http-inspection&lt;BR /&gt;&amp;nbsp; inspect http&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The packet-tracer shows, that with this ACL only traffic from 172.22.10.50 to 8.8.8.8 is inspected. Traffic from 172.22.10.50 to 7.7.7.7 for example is not expected. I tried to modify the ACL to a permit:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family:courier new,courier,monospace;"&gt;access-list http-inspection extended permit tcp host 172.22.10.50 host 8.8.8.8 eq www&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family:arial,helvetica,sans-serif;"&gt;In the packet-tracer this shows me the exact same result. I checked this option in the ASDM. There is an option for "DO NOT MATCH" and the ACL is with a deny statement. From this I&amp;nbsp;would assume that it is possible to exclude some traffic from the inspection.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone a solution on this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Matthias&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:39:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-exclude/m-p/2663740#M195974</guid>
      <dc:creator>Matthias Jeker</dc:creator>
      <dc:date>2019-03-12T05:39:31Z</dc:date>
    </item>
    <item>
      <title>*push*</title>
      <link>https://community.cisco.com/t5/network-security/asa-exclude/m-p/2663741#M195975</link>
      <description>&lt;P&gt;*push*&lt;/P&gt;</description>
      <pubDate>Fri, 20 Mar 2015 07:37:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-exclude/m-p/2663741#M195975</guid>
      <dc:creator>Matthias Jeker</dc:creator>
      <dc:date>2015-03-20T07:37:02Z</dc:date>
    </item>
    <item>
      <title>Solved. This is a bug in the</title>
      <link>https://community.cisco.com/t5/network-security/asa-exclude/m-p/2663742#M195976</link>
      <description>&lt;P&gt;Solved. This is a bug in the packet-tracer which doesn't look up the MPF correctly. You should use show service-policy flow&amp;nbsp;instead.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2015 07:39:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-exclude/m-p/2663742#M195976</guid>
      <dc:creator>Matthias Jeker</dc:creator>
      <dc:date>2015-03-24T07:39:01Z</dc:date>
    </item>
  </channel>
</rss>

