<?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 Netflow for IPSec Tunnel in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/netflow-for-ipsec-tunnel/m-p/2352111#M308958</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi maruis,&lt;/P&gt;&lt;P&gt;Yes , we have applied the service-policy on the outside interface. If we change the service policy to inside interface, will we be able to view the exact source &amp;amp; destination IP of the servers behind the firewall?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 Nov 2013 12:37:55 GMT</pubDate>
    <dc:creator>pratik_193</dc:creator>
    <dc:date>2013-11-18T12:37:55Z</dc:date>
    <item>
      <title>Netflow for IPSec Tunnel</title>
      <link>https://community.cisco.com/t5/network-security/netflow-for-ipsec-tunnel/m-p/2352109#M308955</link>
      <description>&lt;P&gt;hey guys..&lt;/P&gt;&lt;P&gt;I have a question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have 2 different offices at 2 different locations, these locations are connected via a VPN tunnel (IPSec, site to site) configured on Cisco ASA Firewall on both the sides. We do see the netflow between these two locations , but we do not get the exact server details on both the ends in netflow, only detail that we get is the outside IP of both the firewalls. &lt;BR /&gt; &lt;BR /&gt; Below is the scenario &amp;amp; what we want to achieve.&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; Location A , Server A --&amp;gt; Firewall at location A --&amp;gt; IPSec tunnel&amp;nbsp; --&amp;gt;Firewall at location B --&amp;gt;Server B&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; What is happening now is that in NTA, we get the source &amp;amp; destination as Outside Interface on both the Firewall, what we want is the IP Address of Server A &amp;amp; Server B as source &amp;amp; destination.&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; Is the above achievable?&lt;BR /&gt; &lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 03:04:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/netflow-for-ipsec-tunnel/m-p/2352109#M308955</guid>
      <dc:creator>pratik_193</dc:creator>
      <dc:date>2019-03-12T03:04:55Z</dc:date>
    </item>
    <item>
      <title>Netflow for IPSec Tunnel</title>
      <link>https://community.cisco.com/t5/network-security/netflow-for-ipsec-tunnel/m-p/2352110#M308956</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;to which interface did you apply the service-policy?&amp;nbsp; From the sounds of it you applied it to the outside interface, this will show the source and destination as the public / ASA interface IPs.&amp;nbsp; Apply the service-policy to the inside interface on the ASA and you should see the correct source and destination IPs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Please rate all helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Nov 2013 20:30:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/netflow-for-ipsec-tunnel/m-p/2352110#M308956</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2013-11-17T20:30:35Z</dc:date>
    </item>
    <item>
      <title>Netflow for IPSec Tunnel</title>
      <link>https://community.cisco.com/t5/network-security/netflow-for-ipsec-tunnel/m-p/2352111#M308958</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi maruis,&lt;/P&gt;&lt;P&gt;Yes , we have applied the service-policy on the outside interface. If we change the service policy to inside interface, will we be able to view the exact source &amp;amp; destination IP of the servers behind the firewall?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Nov 2013 12:37:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/netflow-for-ipsec-tunnel/m-p/2352111#M308958</guid>
      <dc:creator>pratik_193</dc:creator>
      <dc:date>2013-11-18T12:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: Netflow for IPSec Tunnel</title>
      <link>https://community.cisco.com/t5/network-security/netflow-for-ipsec-tunnel/m-p/2352112#M308960</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, once you apply the service-policy to the inside interface where the traffic you want to monitor is ingressing the ASA, you will see the correct source and destination IPs.&amp;nbsp; Unless you have some other device further into your network that is performing NAT, then you will see the NATed address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Please rate all helpful posts&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Nov 2013 15:19:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/netflow-for-ipsec-tunnel/m-p/2352112#M308960</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2013-11-18T15:19:38Z</dc:date>
    </item>
  </channel>
</rss>

