<?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: netflow not passing through the firewall in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3346818#M1033138</link>
    <description>&lt;P&gt;Did you run the capture? What do you see there?&lt;/P&gt;
&lt;P&gt;Instead of guessing we can review captured packet on different ASA interfaces.&lt;/P&gt;</description>
    <pubDate>Mon, 12 Mar 2018 15:06:34 GMT</pubDate>
    <dc:creator>Florin Barhala</dc:creator>
    <dc:date>2018-03-12T15:06:34Z</dc:date>
    <item>
      <title>netflow not passing through the firewall</title>
      <link>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3345116#M1033134</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have configured flexible netflow on cisco 4351.&amp;nbsp; I want to sync it with Solarwinds using port 2055.&amp;nbsp;its generating stats, but some how all the netflow information is not passing through Cisco ASA as it is not syncing with Solarwinds (showing never under last received netflow).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Below is the config:-&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;flow record FLOW_RECORD_IPv4&lt;BR /&gt; match ipv4 tos&lt;BR /&gt; match ipv4 protocol&lt;BR /&gt; match ipv4 source address&lt;BR /&gt; match ipv4 destination address&lt;BR /&gt; match transport source-port&lt;BR /&gt; match transport destination-port&lt;BR /&gt; collect counter bytes&lt;BR /&gt; collect counter packets&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;flow exporter EXPORTER_A.B.C.D&lt;BR /&gt; destination A.B.C.D&lt;BR /&gt; transport udp 2055&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;flow monitor FLOW_MONITOR_IPv4&lt;BR /&gt; exporter EXPORTER_A.B.C.D&lt;BR /&gt; record FLOW_RECORD_IPv4&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/0/2&lt;BR /&gt;ip flow monitor FLOW_MONITOR_IPv4 input&lt;BR /&gt; ip flow monitor FLOW_MONITOR_IPv4 output&lt;/P&gt;
&lt;P&gt;!&lt;/P&gt;
&lt;P&gt;Also, On ASA i have applied access-list to permit udp traffic on port 2055.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Suggestions please. Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:29:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3345116#M1033134</guid>
      <dc:creator>jasmeet.guru</dc:creator>
      <dc:date>2020-02-21T15:29:44Z</dc:date>
    </item>
    <item>
      <title>Re: netflow not passing through the firewall</title>
      <link>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3345121#M1033135</link>
      <description>&lt;P&gt;Is the ASA perhaps NATing the source address so when it arrives it appears to have come from a different IP address than your router?&lt;/P&gt;</description>
      <pubDate>Thu, 08 Mar 2018 20:14:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3345121#M1033135</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2018-03-08T20:14:44Z</dc:date>
    </item>
    <item>
      <title>Re: netflow not passing through the firewall</title>
      <link>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3345429#M1033136</link>
      <description>On the same idea as Philip, can you run a capture on ASA on the EXIT interface aka 2nd interface and check traffic status.</description>
      <pubDate>Fri, 09 Mar 2018 09:36:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3345429#M1033136</guid>
      <dc:creator>Florin Barhala</dc:creator>
      <dc:date>2018-03-09T09:36:36Z</dc:date>
    </item>
    <item>
      <title>Re: netflow not passing through the firewall</title>
      <link>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3345664#M1033137</link>
      <description>&lt;P&gt;Hi Philip,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ASA is not NATing the source address from router, however the inside network (solarwinds address is NATed). I have applied the ACL for destination (solarwinds both Original and NATed address) to permit traffic from any source, no luck.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;What should be changed ?&lt;/P&gt;</description>
      <pubDate>Fri, 09 Mar 2018 16:06:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3345664#M1033137</guid>
      <dc:creator>jasmeet.guru</dc:creator>
      <dc:date>2018-03-09T16:06:22Z</dc:date>
    </item>
    <item>
      <title>Re: netflow not passing through the firewall</title>
      <link>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3346818#M1033138</link>
      <description>&lt;P&gt;Did you run the capture? What do you see there?&lt;/P&gt;
&lt;P&gt;Instead of guessing we can review captured packet on different ASA interfaces.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Mar 2018 15:06:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/3346818#M1033138</guid>
      <dc:creator>Florin Barhala</dc:creator>
      <dc:date>2018-03-12T15:06:34Z</dc:date>
    </item>
    <item>
      <title>Re: netflow not passing through the firewall</title>
      <link>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/5045563#M1110126</link>
      <description>&lt;P&gt;Not sure if you ever solved this. I have seen where the FTD drops traffic when the source IP used to originate UDP traffic does not have a route to send traffic back to the interface that it received the traffic from.&amp;nbsp; The packet capture tool with trace can help identify this.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 16:53:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/netflow-not-passing-through-the-firewall/m-p/5045563#M1110126</guid>
      <dc:creator>mahyatt</dc:creator>
      <dc:date>2024-03-20T16:53:10Z</dc:date>
    </item>
  </channel>
</rss>

