<?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: ICMP Flooding  in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/icmp-flooding/m-p/556882#M92702</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What do I check for specifically?  I read on Cisco.com that you cant configure with the CLI:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Quote:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Action Configuration via CLI No Longer Supported &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco IOS IPS actions (such as resetting the TCP connection) can no longer be configured via CLI. If you are using the attack-drop.sdf signature file, the signatures are preset with actions to mitigate the attack by dropping the packet and resetting the connection, if applicable. If you are using VMS or SDM to deploy signatures to the router, you will need to tune the signatures to use the desired actions before the deployment. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Aug 2006 10:13:11 GMT</pubDate>
    <dc:creator>jstevensen</dc:creator>
    <dc:date>2006-08-07T10:13:11Z</dc:date>
    <item>
      <title>ICMP Flooding</title>
      <link>https://community.cisco.com/t5/network-security/icmp-flooding/m-p/556880#M92700</link>
      <description>&lt;P&gt;I have a 2611xm with IOS/FW 12.4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After enabling IPS, I get the following when I show ip inspect sessions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Session 83E4AD08 (192.168.5.101:8)=&amp;gt;(192.168.240.251:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C84EAC (192.168.5.101:8)=&amp;gt;(192.168.240.170:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E4C2C8 (192.168.5.101:8)=&amp;gt;(192.168.240.217:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E460E8 (192.168.5.101:8)=&amp;gt;(192.168.240.214:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E41A38 (192.168.5.101:8)=&amp;gt;(192.168.240.186:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E4DB40 (192.168.5.101:8)=&amp;gt;(192.168.241.26:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C8E6EC (192.168.5.101:8)=&amp;gt;(192.168.240.155:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C86724 (192.168.5.101:8)=&amp;gt;(192.168.240.153:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E50C30 (192.168.5.101:8)=&amp;gt;(192.168.240.250:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E41780 (192.168.5.101:8)=&amp;gt;(192.168.240.175:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C8DC0C (192.168.5.101:8)=&amp;gt;(192.168.240.171:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C8E9A4 (192.168.5.101:8)=&amp;gt;(192.168.240.191:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E45608 (192.168.5.101:8)=&amp;gt;(192.168.240.187:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E47138 (192.168.5.101:8)=&amp;gt;(192.168.241.31:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E5FD68 (192.168.5.101:8)=&amp;gt;(192.168.240.164:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C81024 (192.168.5.101:8)=&amp;gt;(192.168.241.79:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E56528 (192.168.5.101:8)=&amp;gt;(192.168.241.69:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E42A88 (192.168.5.101:8)=&amp;gt;(192.168.240.239:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C8AB1C (192.168.5.101:8)=&amp;gt;(192.168.240.196:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C84BF4 (192.168.5.101:8)=&amp;gt;(192.168.240.192:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E5DF80 (192.168.5.101:8)=&amp;gt;(192.168.240.149:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E5BEE0 (192.168.5.101:8)=&amp;gt;(192.168.240.139:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C88254 (192.168.5.101:8)=&amp;gt;(192.168.240.181:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C8DEC4 (192.168.254.161:138)=&amp;gt;(192.168.5.11:138) udp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83C8B08C (192.168.5.101:8)=&amp;gt;(192.168.240.213:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt; Session 83E4A798 (192.168.5.101:8)=&amp;gt;(192.168.240.209:0) icmp SIS_OPEN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is this:  Why is it being allowed, and logged, but not prevented?&lt;/P&gt;&lt;P&gt;This machine obviously has a worm on it - but I'd like to at least be able to have the IPS block it till we can get to the machine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:09:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/icmp-flooding/m-p/556880#M92700</guid>
      <dc:creator>jstevensen</dc:creator>
      <dc:date>2019-03-10T10:09:04Z</dc:date>
    </item>
    <item>
      <title>Re: ICMP Flooding</title>
      <link>https://community.cisco.com/t5/network-security/icmp-flooding/m-p/556881#M92701</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi  ..  check the signatures that relate to icmp floods they might be configured to alert and log only by default ..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps ..  please rate if it does !!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Aug 2006 20:22:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/icmp-flooding/m-p/556881#M92701</guid>
      <dc:creator>Fernando_Meza</dc:creator>
      <dc:date>2006-08-05T20:22:04Z</dc:date>
    </item>
    <item>
      <title>Re: ICMP Flooding</title>
      <link>https://community.cisco.com/t5/network-security/icmp-flooding/m-p/556882#M92702</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What do I check for specifically?  I read on Cisco.com that you cant configure with the CLI:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Quote:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Action Configuration via CLI No Longer Supported &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco IOS IPS actions (such as resetting the TCP connection) can no longer be configured via CLI. If you are using the attack-drop.sdf signature file, the signatures are preset with actions to mitigate the attack by dropping the packet and resetting the connection, if applicable. If you are using VMS or SDM to deploy signatures to the router, you will need to tune the signatures to use the desired actions before the deployment. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Aug 2006 10:13:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/icmp-flooding/m-p/556882#M92702</guid>
      <dc:creator>jstevensen</dc:creator>
      <dc:date>2006-08-07T10:13:11Z</dc:date>
    </item>
  </channel>
</rss>

