<?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: Blocking on external router in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/blocking-on-external-router/m-p/2129213#M54324</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From the link that I posted, here are the steps that the IPS takes when building the ACL:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; When the sensor starts up, it reads the contents of the two ACLs. It creates a third ACL with the following entries: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; •&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/customer/i/templates/blank.gif" width="19" /&gt;A &lt;STRONG&gt;permit&lt;/STRONG&gt; line for the sensor IP address &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; •&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/customer/i/templates/blank.gif" width="19" /&gt;Copies of all configuration lines of the Pre-Block ACL &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; •&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/customer/i/templates/blank.gif" width="19" /&gt;A &lt;STRONG&gt;deny&lt;/STRONG&gt; line for each address being blocked by the sensor &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; •&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/customer/i/templates/blank.gif" width="19" /&gt;Copies of all configuration lines of the Post-Block ACL &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The sensor applies the new ACL to the interface and direction that you designate. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your case, you could use the ACL_Router_External as your Post-Block ACL.&amp;nbsp; The IPS will add a permit for itself and a deny entry for the address being blocked.&amp;nbsp; It will then append the existing ACL_Router_External entries that you already have configured before pushing the new combined ACL to the g0/0 interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Dec 2012 05:36:29 GMT</pubDate>
    <dc:creator>Todd Pula</dc:creator>
    <dc:date>2012-12-10T05:36:29Z</dc:date>
    <item>
      <title>Blocking on external router</title>
      <link>https://community.cisco.com/t5/network-security/blocking-on-external-router/m-p/2129210#M54318</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i want to configure blocking on external router for some specfic signature, i already have access list on the outside interface to block some traffic and fragment packets with the name ACL_Router_External applied on interface outisde (G0/0)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when i configure blocking on IPS it create another ACL and applied to interface same interface in order to block.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how can i push ACL configuration from IPS to exisiting ACL&amp;nbsp; (ACL_Router_External) ???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 20:42:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-on-external-router/m-p/2129210#M54318</guid>
      <dc:creator>alkabeer80</dc:creator>
      <dc:date>2019-03-10T20:42:51Z</dc:date>
    </item>
    <item>
      <title>Blocking on external router</title>
      <link>https://community.cisco.com/t5/network-security/blocking-on-external-router/m-p/2129211#M54320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The blocking feature on the IPS will always push its own ACL to the router interface in question.&amp;nbsp; When it builds this new ACL, the IPS will reference any pre and post-block ACLs that you have statically configured on the router.&amp;nbsp; The IPS will then sandwich the deny statements in between for the block traffic in question before deploying the combined ACL to the configured router interface.&amp;nbsp; You can read more about the feature at the following link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/customer/docs/security/ips/7.0/configuration/guide/ime/ime_blocking.html#wp2188519"&gt;http://www.cisco.com/en/US/customer/docs/security/ips/7.0/configuration/guide/ime/ime_blocking.html#wp2188519&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2012 05:04:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-on-external-router/m-p/2129211#M54320</guid>
      <dc:creator>Todd Pula</dc:creator>
      <dc:date>2012-12-10T05:04:22Z</dc:date>
    </item>
    <item>
      <title>Blocking on external router</title>
      <link>https://community.cisco.com/t5/network-security/blocking-on-external-router/m-p/2129212#M54323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Todd,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;my case is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ISP ------&amp;gt; (G0/0) External Router ---------&amp;gt; Switch1----------&amp;gt;IPS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ----------&amp;gt; Switch2 ---------&amp;gt;IPS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interface G0/0 already has ACL which deny unwanted traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have configured IPS to block some attacks based signature fireing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any solution i can do ????&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanksss&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2012 05:16:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-on-external-router/m-p/2129212#M54323</guid>
      <dc:creator>alkabeer80</dc:creator>
      <dc:date>2012-12-10T05:16:19Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking on external router</title>
      <link>https://community.cisco.com/t5/network-security/blocking-on-external-router/m-p/2129213#M54324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From the link that I posted, here are the steps that the IPS takes when building the ACL:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; When the sensor starts up, it reads the contents of the two ACLs. It creates a third ACL with the following entries: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; •&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/customer/i/templates/blank.gif" width="19" /&gt;A &lt;STRONG&gt;permit&lt;/STRONG&gt; line for the sensor IP address &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; •&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/customer/i/templates/blank.gif" width="19" /&gt;Copies of all configuration lines of the Pre-Block ACL &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; •&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/customer/i/templates/blank.gif" width="19" /&gt;A &lt;STRONG&gt;deny&lt;/STRONG&gt; line for each address being blocked by the sensor &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; •&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/customer/i/templates/blank.gif" width="19" /&gt;Copies of all configuration lines of the Post-Block ACL &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The sensor applies the new ACL to the interface and direction that you designate. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your case, you could use the ACL_Router_External as your Post-Block ACL.&amp;nbsp; The IPS will add a permit for itself and a deny entry for the address being blocked.&amp;nbsp; It will then append the existing ACL_Router_External entries that you already have configured before pushing the new combined ACL to the g0/0 interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2012 05:36:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-on-external-router/m-p/2129213#M54324</guid>
      <dc:creator>Todd Pula</dc:creator>
      <dc:date>2012-12-10T05:36:29Z</dc:date>
    </item>
  </channel>
</rss>

