<?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: Need alternative to packet-tracer for Firepower 4110 with L7 rules on FMC in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/need-alternative-to-packet-tracer-for-firepower-4110-with-l7/m-p/4412145#M1081245</link>
    <description>&lt;P&gt;It's not exactly the same, but if you have live traffic to check with you can get more reliable output using &lt;STRONG&gt;system support firewall-engine-debug&lt;/STRONG&gt; and &lt;STRONG&gt;system-support-trace&lt;/STRONG&gt; output.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/214577-firepower-data-path-troubleshooting-phas.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/214577-firepower-data-path-troubleshooting-phas.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 02 Jun 2021 18:14:14 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2021-06-02T18:14:14Z</dc:date>
    <item>
      <title>Need alternative to packet-tracer for Firepower 4110 with L7 rules on FMC</title>
      <link>https://community.cisco.com/t5/network-security/need-alternative-to-packet-tracer-for-firepower-4110-with-l7/m-p/4412137#M1081244</link>
      <description>&lt;P&gt;Packet-tracer doesn't work reliably when you have upper layer rules on an FMC. Rules often show traffic is passed, when the FMC will actually block it. I know there is a similar method, and I heard that Cisco will eventually fix packet-tracer to work with the higher layer rules. Can someone send over directions? I've not been able to find this in the Firepower documentation. Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 17:56:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/need-alternative-to-packet-tracer-for-firepower-4110-with-l7/m-p/4412137#M1081244</guid>
      <dc:creator>ABaker94985</dc:creator>
      <dc:date>2021-06-02T17:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: Need alternative to packet-tracer for Firepower 4110 with L7 rules on FMC</title>
      <link>https://community.cisco.com/t5/network-security/need-alternative-to-packet-tracer-for-firepower-4110-with-l7/m-p/4412145#M1081245</link>
      <description>&lt;P&gt;It's not exactly the same, but if you have live traffic to check with you can get more reliable output using &lt;STRONG&gt;system support firewall-engine-debug&lt;/STRONG&gt; and &lt;STRONG&gt;system-support-trace&lt;/STRONG&gt; output.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/214577-firepower-data-path-troubleshooting-phas.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/214577-firepower-data-path-troubleshooting-phas.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 18:14:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/need-alternative-to-packet-tracer-for-firepower-4110-with-l7/m-p/4412145#M1081245</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2021-06-02T18:14:14Z</dc:date>
    </item>
    <item>
      <title>Re: Need alternative to packet-tracer for Firepower 4110 with L7 rules on FMC</title>
      <link>https://community.cisco.com/t5/network-security/need-alternative-to-packet-tracer-for-firepower-4110-with-l7/m-p/4412149#M1081246</link>
      <description>&lt;P&gt;That's exactly what I was looking for. Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 18:20:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/need-alternative-to-packet-tracer-for-firepower-4110-with-l7/m-p/4412149#M1081246</guid>
      <dc:creator>ABaker94985</dc:creator>
      <dc:date>2021-06-02T18:20:42Z</dc:date>
    </item>
  </channel>
</rss>

