<?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 Packet/Protocol decode in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-packet-protocol-decode/m-p/17437#M673898</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you are looking for information on you network, I would use a sniffer instead of using debug on the PIX. Debug is really meant for troubleshooting purposes and not for baselining. Like Vince mentioned, debugging can take a significant part of the available resources.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 08 Aug 2001 15:23:00 GMT</pubDate>
    <dc:creator>rrbleeker</dc:creator>
    <dc:date>2001-08-08T15:23:00Z</dc:date>
    <item>
      <title>Pix Packet/Protocol decode</title>
      <link>https://community.cisco.com/t5/network-security/pix-packet-protocol-decode/m-p/17435#M673851</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm having problems getting a Pix firewall to do a packet/Protocol decode of the packets hitting my firewall just to have granular info. regarding what is happening on the network from the internet. Is this possible if yes how? if not then this is something cisco should look at implementing in any upgraded version of code . &lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 05:49:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-packet-protocol-decode/m-p/17435#M673851</guid>
      <dc:creator>ebs_trader</dc:creator>
      <dc:date>2020-02-21T05:49:05Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Packet/Protocol decode</title>
      <link>https://community.cisco.com/t5/network-security/pix-packet-protocol-decode/m-p/17436#M673876</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not sure I understand the question. there is a debug packet command, But, on a busy network, depending on what you wish to decode, it can consume some resouces. What is it you want to decode?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jul 2001 21:16:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-packet-protocol-decode/m-p/17436#M673876</guid>
      <dc:creator>millerv</dc:creator>
      <dc:date>2001-07-25T21:16:18Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Packet/Protocol decode</title>
      <link>https://community.cisco.com/t5/network-security/pix-packet-protocol-decode/m-p/17437#M673898</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you are looking for information on you network, I would use a sniffer instead of using debug on the PIX. Debug is really meant for troubleshooting purposes and not for baselining. Like Vince mentioned, debugging can take a significant part of the available resources.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Aug 2001 15:23:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-packet-protocol-decode/m-p/17437#M673898</guid>
      <dc:creator>rrbleeker</dc:creator>
      <dc:date>2001-08-08T15:23:00Z</dc:date>
    </item>
  </channel>
</rss>

