<?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 capture with SFR in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4261822#M1076811</link>
    <description>&lt;P&gt;Dear all&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a short question to you guys, when I run a capture on the outside (Internet) interface of an ASA-5545 (the ASA has the SFR module installed and acts as a NGFW) with the following command:&lt;/P&gt;&lt;PRE&gt;capture capin interface outside match ip host 100.100.100.100 any&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And then checking this capture with the command:&lt;/P&gt;&lt;PRE&gt;show capture capin dump&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are the details I see now how this data really enters the interface? Without any applied Service Policy Rules, without any applied ACLs and before the Firepower module would take any actions? Means when I see a certain flag in the dump within the protocol, I can assume this flag has been sent by the source IP address and has not been changed by my ASA firewall within a policy?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Of course you have a good article which describes this behavior, where the capture applies to?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Markus&lt;/P&gt;</description>
    <pubDate>Mon, 21 Dec 2020 13:27:44 GMT</pubDate>
    <dc:creator>markus.albisser1</dc:creator>
    <dc:date>2020-12-21T13:27:44Z</dc:date>
    <item>
      <title>ASA capture with SFR</title>
      <link>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4261822#M1076811</link>
      <description>&lt;P&gt;Dear all&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a short question to you guys, when I run a capture on the outside (Internet) interface of an ASA-5545 (the ASA has the SFR module installed and acts as a NGFW) with the following command:&lt;/P&gt;&lt;PRE&gt;capture capin interface outside match ip host 100.100.100.100 any&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And then checking this capture with the command:&lt;/P&gt;&lt;PRE&gt;show capture capin dump&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are the details I see now how this data really enters the interface? Without any applied Service Policy Rules, without any applied ACLs and before the Firepower module would take any actions? Means when I see a certain flag in the dump within the protocol, I can assume this flag has been sent by the source IP address and has not been changed by my ASA firewall within a policy?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Of course you have a good article which describes this behavior, where the capture applies to?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Markus&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2020 13:27:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4261822#M1076811</guid>
      <dc:creator>markus.albisser1</dc:creator>
      <dc:date>2020-12-21T13:27:44Z</dc:date>
    </item>
    <item>
      <title>Re: ASA capture with SFR</title>
      <link>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4261865#M1076813</link>
      <description>&lt;P&gt;check below blog will give you some idea what interface using to capture :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://popravak.wordpress.com/2017/03/17/packet-capture-with-sourcefire-cli/" target="_blank"&gt;https://popravak.wordpress.com/2017/03/17/packet-capture-with-sourcefire-cli/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2020 15:00:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4261865#M1076813</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2020-12-21T15:00:16Z</dc:date>
    </item>
    <item>
      <title>Re: ASA capture with SFR</title>
      <link>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4261896#M1076814</link>
      <description>&lt;P&gt;Hi Balaji&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for this link. Helpful troubleshooting steps when logging on the SFR module! This is what I can do, check the logging there and compare it with the capture from the ASA.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Nevermind, do you know if the ASA capture is really on the ingress of the interface, therefore before the SFR module comes in charge? That the ASA capture gets the raw-data before anything within the ASA has been handled?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Markus&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2020 15:40:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4261896#M1076814</guid>
      <dc:creator>markus.albisser1</dc:creator>
      <dc:date>2020-12-21T15:40:56Z</dc:date>
    </item>
    <item>
      <title>Re: ASA capture with SFR</title>
      <link>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4261907#M1076815</link>
      <description>&lt;P&gt;you need to understand the traffic flow how this process works, and where you capturing.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.ciscopress.com/articles/article.asp?p=2730336&amp;amp;seqNum=7" target="_blank"&gt;https://www.ciscopress.com/articles/article.asp?p=2730336&amp;amp;seqNum=7&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image.png" style="width: 901px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/100060i3195CF9F6FAA329B/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2020 16:13:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4261907#M1076815</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2020-12-21T16:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: ASA capture with SFR</title>
      <link>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4262184#M1076835</link>
      <description>&lt;P&gt;An ASA capture on an interfaces does indeed show you the raw traffic entering the interface, prior to any action potentially taken by the ASA to evaluate the flow or disposition of the packet(s).&lt;/P&gt;</description>
      <pubDate>Tue, 22 Dec 2020 03:52:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4262184#M1076835</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-12-22T03:52:55Z</dc:date>
    </item>
    <item>
      <title>Re: ASA capture with SFR</title>
      <link>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4262198#M1076837</link>
      <description>&lt;P&gt;Great diagram, thanks Balaji for this post. This is what I looked for. Together with Marvin's answer below, this answers my question.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Markus&lt;/P&gt;</description>
      <pubDate>Tue, 22 Dec 2020 05:11:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-capture-with-sfr/m-p/4262198#M1076837</guid>
      <dc:creator>markus.albisser1</dc:creator>
      <dc:date>2020-12-22T05:11:19Z</dc:date>
    </item>
  </channel>
</rss>

