<?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 Hi Philip, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/inside-another-inside-interface-not-triggering-firepower/m-p/2814432#M44205</link>
    <description>&lt;P&gt;Hi Philip,&lt;/P&gt;
&lt;P&gt;So you do &lt;BR /&gt;service-policy&amp;nbsp;sfr-service-policy interface inside&lt;/P&gt;
&lt;P&gt;service-policy sfr-service-policy interface dmz&lt;/P&gt;
&lt;P&gt;etc?&lt;/P&gt;</description>
    <pubDate>Wed, 10 Feb 2016 12:53:39 GMT</pubDate>
    <dc:creator>babiojd01</dc:creator>
    <dc:date>2016-02-10T12:53:39Z</dc:date>
    <item>
      <title>Inside another inside interface not triggering firepower signatures</title>
      <link>https://community.cisco.com/t5/network-security/inside-another-inside-interface-not-triggering-firepower/m-p/2814430#M44202</link>
      <description>&lt;P&gt;I can't seem to get firepower to alert on communication from 1 inside interface to another. I only get it to trigger when I go from inside to outside. Any thoughts? I even modified the HOME_NET to be any. I have the sfr policy global and the 2 interfaces are 1 inside interface and a subinterface off of that.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:33:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-another-inside-interface-not-triggering-firepower/m-p/2814430#M44202</guid>
      <dc:creator>babiojd01</dc:creator>
      <dc:date>2019-03-10T13:33:17Z</dc:date>
    </item>
    <item>
      <title>So the global policy only</title>
      <link>https://community.cisco.com/t5/network-security/inside-another-inside-interface-not-triggering-firepower/m-p/2814431#M44204</link>
      <description>&lt;P&gt;So the global policy only applies if an interface policy does not apply.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I normally apply the sfr policy to all interfaces except the outside interface (at least, every interface I want inspected), and let the global inspection policy (not using sfr) act on that.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2016 03:15:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-another-inside-interface-not-triggering-firepower/m-p/2814431#M44204</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-02-10T03:15:27Z</dc:date>
    </item>
    <item>
      <title>Hi Philip,</title>
      <link>https://community.cisco.com/t5/network-security/inside-another-inside-interface-not-triggering-firepower/m-p/2814432#M44205</link>
      <description>&lt;P&gt;Hi Philip,&lt;/P&gt;
&lt;P&gt;So you do &lt;BR /&gt;service-policy&amp;nbsp;sfr-service-policy interface inside&lt;/P&gt;
&lt;P&gt;service-policy sfr-service-policy interface dmz&lt;/P&gt;
&lt;P&gt;etc?&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2016 12:53:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-another-inside-interface-not-triggering-firepower/m-p/2814432#M44205</guid>
      <dc:creator>babiojd01</dc:creator>
      <dc:date>2016-02-10T12:53:39Z</dc:date>
    </item>
    <item>
      <title>Yes, that is my preferred</title>
      <link>https://community.cisco.com/t5/network-security/inside-another-inside-interface-not-triggering-firepower/m-p/2814433#M44206</link>
      <description>&lt;P&gt;Yes, that is my preferred deployment approach.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;This differs from the way Cisco shows in their documents. &amp;nbsp;The nice thing about this way is you can still use FTP fixups and the like.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2016 19:50:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-another-inside-interface-not-triggering-firepower/m-p/2814433#M44206</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-02-10T19:50:03Z</dc:date>
    </item>
  </channel>
</rss>

