<?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: trying to debug an ACL on PIX in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/trying-to-debug-an-acl-on-pix/m-p/184439#M612561</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Debugging on the PIX will certainly give you a ton of information.  With the PIX you can either use the "capture" command to capture all traffic based on an ACL (which can then even be saved off in Sniffer format, very useful), or in 6.3 code you can add a log keyword to the end of the access-list command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See &lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/ab.htm#1067755" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/ab.htm#1067755&lt;/A&gt; for details, the default logging level of ACL lines is informational, so if you do "logging monitor info" then you should see these and not get all the other stuff you get at debug level.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Aug 2003 02:32:09 GMT</pubDate>
    <dc:creator>gfullage</dc:creator>
    <dc:date>2003-08-26T02:32:09Z</dc:date>
    <item>
      <title>trying to debug an ACL on PIX</title>
      <link>https://community.cisco.com/t5/network-security/trying-to-debug-an-acl-on-pix/m-p/184438#M612559</link>
      <description>&lt;P&gt;I would like to setup an ACL then use a "debug packet" type command to observe certain traffic on my PIX 515e.  I have used this technique many times with IOS routers but the PIX just doesn't behave the same way.  As soon as I give the "logging monitor debug" I am swamped with all sorts of info concerning other operations of the PIX like denied inbound packets, NAT events, TCP connections established and so on.  How can I get the PIX to show me ONLY the traffic defined by my ACL and NOTHING else?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Diego&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:57:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/trying-to-debug-an-acl-on-pix/m-p/184438#M612559</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2020-02-21T06:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: trying to debug an ACL on PIX</title>
      <link>https://community.cisco.com/t5/network-security/trying-to-debug-an-acl-on-pix/m-p/184439#M612561</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Debugging on the PIX will certainly give you a ton of information.  With the PIX you can either use the "capture" command to capture all traffic based on an ACL (which can then even be saved off in Sniffer format, very useful), or in 6.3 code you can add a log keyword to the end of the access-list command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See &lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/ab.htm#1067755" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/ab.htm#1067755&lt;/A&gt; for details, the default logging level of ACL lines is informational, so if you do "logging monitor info" then you should see these and not get all the other stuff you get at debug level.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Aug 2003 02:32:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/trying-to-debug-an-acl-on-pix/m-p/184439#M612561</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2003-08-26T02:32:09Z</dc:date>
    </item>
  </channel>
</rss>

