<?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: How to capture-traffic in FirePower 8000 Series Firewall in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-to-capture-traffic-in-firepower-8000-series-firewall/m-p/4143517#M1073475</link>
    <description>&lt;P&gt;Maybe you should insert "vlan" word at the filter to be able to capture dot1q tagged packets.&lt;/P&gt;</description>
    <pubDate>Sun, 30 Aug 2020 01:35:10 GMT</pubDate>
    <dc:creator>rogerf100</dc:creator>
    <dc:date>2020-08-30T01:35:10Z</dc:date>
    <item>
      <title>How to capture-traffic in FirePower 8000 Series Firewall</title>
      <link>https://community.cisco.com/t5/network-security/how-to-capture-traffic-in-firepower-8000-series-firewall/m-p/4090398#M1070413</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;How to capture-traffic in FirePower 8000 Series Firewall ? Below command does not work. But with system support trace command i verified traffic is moving. Just note that this is L2 Firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;gt; system support capture-traffic&lt;/P&gt;&lt;P&gt;Please choose domain to capture traffic from:&lt;BR /&gt;0 - eth0&lt;BR /&gt;1 - Core (Interfaces s4p3, s4p4, s4p1, s4p2, s3p3, s3p4, s3p1, s3p2, s2p3, s2p4, s2p1, s2p2)&lt;/P&gt;&lt;P&gt;Selection? 1&lt;/P&gt;&lt;P&gt;WARNING: Running tcpdump can cause performance degradation and lead to packet loss!&lt;/P&gt;&lt;P&gt;Please specify tcpdump options desired.&lt;BR /&gt;(or enter '?' for a list of supported options)&lt;BR /&gt;Options: -w cap.pcap -s 1518 -c 5000 host 10.7.22.25&lt;BR /&gt;tcpdump: listening on nfe0.1.22:nfe1.1.22:nfe2.1.22:nfe3.1.22, link-type EN10MB (Ethernet), capture size 1518 bytes&lt;BR /&gt;^C0 packets captured&lt;BR /&gt;0 packets received by filter&lt;BR /&gt;0 packets dropped by kernel&lt;BR /&gt;NS NFM Errors&lt;BR /&gt;Receive Errors: 0&lt;BR /&gt;Transmit Errors: 0&lt;BR /&gt;Tick Errors: 0&lt;/P&gt;</description>
      <pubDate>Thu, 21 May 2020 22:52:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-capture-traffic-in-firepower-8000-series-firewall/m-p/4090398#M1070413</guid>
      <dc:creator>subrun.jamil</dc:creator>
      <dc:date>2020-05-21T22:52:26Z</dc:date>
    </item>
    <item>
      <title>Re: How to capture-traffic in FirePower 8000 Series Firewall</title>
      <link>https://community.cisco.com/t5/network-security/how-to-capture-traffic-in-firepower-8000-series-firewall/m-p/4143517#M1073475</link>
      <description>&lt;P&gt;Maybe you should insert "vlan" word at the filter to be able to capture dot1q tagged packets.&lt;/P&gt;</description>
      <pubDate>Sun, 30 Aug 2020 01:35:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-capture-traffic-in-firepower-8000-series-firewall/m-p/4143517#M1073475</guid>
      <dc:creator>rogerf100</dc:creator>
      <dc:date>2020-08-30T01:35:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to capture-traffic in FirePower 8000 Series Firewall</title>
      <link>https://community.cisco.com/t5/network-security/how-to-capture-traffic-in-firepower-8000-series-firewall/m-p/4143530#M1073478</link>
      <description>&lt;P&gt;I'm not positive that feature (capture) is supported on a classic Firepower 8000 series. Every reference I have seen talks about it being used on devices running FTD. It may also be a limitation of L2 inline mode vs. routed mode.&lt;/P&gt;</description>
      <pubDate>Sun, 30 Aug 2020 04:01:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-capture-traffic-in-firepower-8000-series-firewall/m-p/4143530#M1073478</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-08-30T04:01:38Z</dc:date>
    </item>
  </channel>
</rss>

