Recent Posts41
General Discussion / Finding and preventing the DDOS attacks
« Last post by nidhinjo on November 01, 2018, 12:28:59 pm »Below are some of the useful netstat commands to check during DDOS attack,
----------------------------------------------------------------------------------------------------------
To list the connections to the target IPs (server's IP's) use the below command :
To list the connections from source IP's use the below command:
To see the state of each connection and the value use the below command:
You can use tcpdump to identify the attacker too:
where x can be 0 or 1,n=number(100 or 1000). If it is a VPS, it can be venet0 too. Check the Output of ifconfig.
To check if a server is under a DoS attack with netstat, it’s common to use:
If the output of below command returns a result like 2000 or 3000 connections!, then obviously it’s very likely the server is under a DoS attack.
To detect a SYN flood with netstat :
If the output returns a value of 1032,1032 SYNs per second is quite a high number and except if the server is not serving let’s say 5000 user requests per second, therefore as the above output reveals it’s very likely the server is under attack, if however I get results like 100/200 SYNs, then obviously there is no SYN flood targetting
Checking if UDP Denial of Service is targetting the server :
The above command will list information concerning possible UDP DoS.
The command can easily be accustomed also to check for both possible TCP and UDP denial of service, like so :
You can see the output as :
335 212.56.156.36
456 96.56.89.223
1565 198.141.85.45
If after getting an IP that has too many connections to the server and is almost certainly a DoS host you would like to filter this IP.
Here is how I remove hosts to not be able to route packets to my server:
The above command would null route the access of IP 198.141.85.45 to my server.
Later on to look up for a null routed IP to my host, I use:
Block the IPs with high connection above using CSF or APF firewall :
==============================
===================================
----------------------------------------------------------------------------------------------------------
To list the connections to the target IPs (server's IP's) use the below command :
Code: [Select]
netstat -alpn | grep :80 | awk '{print $4}' |awk -F: '{print $(NF-1)}' |sort |uniq -c | sort -nTo list the connections from source IP's use the below command:
Code: [Select]
netstat -alpn | grep :80 | awk '{print $5}' |awk -F: '{print $(NF-1)}' |sort |uniq -c | sort -nTo see the state of each connection and the value use the below command:
Code: [Select]
netstat -an|grep ":80"|awk '/tcp/ {print $6}'|sort| uniq -cYou can use tcpdump to identify the attacker too:
Code: [Select]
tcpdump -c -n -i eth"x" -p host IP_Addresswhere x can be 0 or 1,n=number(100 or 1000). If it is a VPS, it can be venet0 too. Check the Output of ifconfig.
To check if a server is under a DoS attack with netstat, it’s common to use:
Code: [Select]
netstat -ntu | awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -n|wc -lIf the output of below command returns a result like 2000 or 3000 connections!, then obviously it’s very likely the server is under a DoS attack.
To detect a SYN flood with netstat :
Code: [Select]
netstat -nap | grep SYN | wc -lIf the output returns a value of 1032,1032 SYNs per second is quite a high number and except if the server is not serving let’s say 5000 user requests per second, therefore as the above output reveals it’s very likely the server is under attack, if however I get results like 100/200 SYNs, then obviously there is no SYN flood targetting
Checking if UDP Denial of Service is targetting the server :
Code: [Select]
netstat -nap | grep 'udp' | awk '{print $5}' | cut -d: -f1 | sort |uniq -c |sort -nThe above command will list information concerning possible UDP DoS.
The command can easily be accustomed also to check for both possible TCP and UDP denial of service, like so :
Code: [Select]
netstat -anp |grep 'tcp\|udp' | awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -nYou can see the output as :
335 212.56.156.36
456 96.56.89.223
1565 198.141.85.45
If after getting an IP that has too many connections to the server and is almost certainly a DoS host you would like to filter this IP.
Here is how I remove hosts to not be able to route packets to my server:
Code: [Select]
route add 198.141.85.45 rejectThe above command would null route the access of IP 198.141.85.45 to my server.
Later on to look up for a null routed IP to my host, I use:
Code: [Select]
route -n |grep -i 198.141.85.45Block the IPs with high connection above using CSF or APF firewall :
Code: [Select]
csf -d IP {reason}
apf -d IP==============================
===================================