A distributed denial-of-service (DDoS) attack is one of the most powerful weapons on the internet. When you hear about a website being “brought down by hackers,” it generally means it has become a victim of a DDoS attack. In short, this means that hackers have attempted to make a website or computer unavailable by flooding or crashing the website with too much traffic.
In a DDoS attack, the incoming traffic flooding the victim originates from many different sources. This makes it impossible to stop the attack simply by blocking a single source.
This article provides instructions on how to enable the protective measures in Kerio Control against such an attack.
To protect your network from DDoS attacks, please follow the steps below to update the settings in Kerio Control:
Log in to the Kerio Control console via SSH.
Run the following command:
mount -o rw,remount /
/etc/sysctl.conffile via Nano or Vim:
Uncomment each of the following lines by removing
#before each line:
After modification, the file should look like this:
Save the file by pressing Ctrl+O.
Restart Kerio Control by using the following command:
(Optional) Depending on your network setup/environment, it is possible to improve the security of the firewall further. Follow these steps:
Uncomment the following lines in the
Restart Kerio Control using the command in Step 6.
The following steps are workarounds for DDOS protection that can be performed from Kerio Control Webadmin or SSH:
To find the IP address, look in the Security log, for example:[01/Nov/2019 18:54:58] IPS: Port Scan, protocol: TCP, source: 126.96.36.199, destination: x.x.x.x,(where x.x.x.x is the attackers' IP address)
[01/Nov/2019 18:55:20] IPS: Packet drop, severity: Blacklist, Rule ID: 1:2402000 ET DROP Dshield Block Listed Source group 1, proto:TCP, ip/port:188.8.131.52:47834 -> x.x.x.x:37980
Disconnect Kerio Control for 20-30 minutes so that attackers will be redirected to a different target.
Increase the Connection limits.
- Decrease the
- Log in via SSH.
- Run the following commands:
/opt/kerio/winroute/tinydbclient "update Firewall set DefaultTcpTimeout=10"
Note: The default TCP timeout value is
40, and it should be modified only as a last resort. If you experience some issues after this modification, please re-set the value to the default (