Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

ICMP Flood Attack – How to Mitigate

by | Feb 20, 2021

Wondering how to mitigate ICMP Flood Attack? We can help you.

Ping flood, also known as ICMP flood, is a common Denial of Service (DoS) attack in which an attacker takes down a victim’s computer by overwhelming it with ICMP echo requests, also known as pings.

When the attack traffic comes from multiple devices, the attack becomes a DDoS attack.

Here at Bobcares, we often handle such DDoS attacks as apart of our Server Management Services.

Today let’s see the steps our Support Techs follow to mitigate this.

How does a Ping flood attack or ICMP Flood Attack work?

The Internet Control Message Protocol (ICMP) utilized during a Ping Flood attack, is an internet layer protocol used by network devices to communicate with each other.

Generally, ICMP uses echo-request and echo-reply messages to ping a network device. This is for checking the health and connectivity of the device and the connection between the sender and the device.

An ICMP request requires some server resources to process each request and to send a response. The request also requires bandwidth on both the incoming message (echo-request) and outgoing response (echo-reply).

The Ping Flood attack influences the targeted device’s ability to respond to the high number of requests. This, in turn, overloads the network connection with huge traffic.

The DDoS form of a Ping (ICMP) Flood can be split into the following steps:

1. Attacker sends many ICMP echo request packets to the target server using multiple devices.
2. The targeted server then sends an ICMP echo reply packet to each requesting device’s IP address as a response.

The damaging effect of a Ping Flood is directly proportional to the number of requests made to the targeted server. Ping Flood attack traffic is symmetrical.

How to mitigate ICMP Flood Attack?

Following are the ways in which we can mitigate ICMP flood attack.

1. Disabling ICMP functionality

Firstly we can try disabling a ping flood can be accomplished by disabling the ICMP functionality of the targeted router, computer, or other devices.

We can do this by accessing the administrative interface of the device and disable its ability to send and receive any requests using the ICMP.

We must keep in mind that all network activities involving ICMP will get disabled. This will make the device unresponsive to ping requests, traceroute requests, and other network activities.

2. Limiting the processing of incoming ICMP messages

Another approach to combating ICMP attacks is to rate-limit the processing of incoming ICMP messages.

This can be commonly done using Iptables. Here we will set 1 ping per second as it is plenty for legitimate uses.

We can use the following commands:

iptables -A INPUT -p icmp -m icmp --icmp-type address-mask-request -j DROP
iptables -A INPUT -p icmp -m icmp --icmp-type timestamp-request -j DROP
iptables -A INPUT -p icmp -m icmp --icmp-type 8 -m limit --limit 1/second -j ACCEPT

[Need assistance? We are happy to help you]


In short, we saw how the ICMP flood attack works, along with the ways which our Support Techs follow to mitigate this.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.