Currently, I’m using IPFire for hosting online games to protect against DDoS attacks. However, some of the DDoS attacks are still able to penetrate my network. Is there a way for me to filter out these DDoS attacks using IPFire? Can you please help me with this? i realy need help you all please
I never seen a DDOS in my life, however if I were to deal with this issue in IPFire I would use Intrusion Prevention (suricata) with rules tailored for this goal. I quickly searched the web and I found (1) several(2) solutions. For the details of the implementation, I cannot help you but I am sure you can figure it out and, if you have specific questions about suricata, other members of this forum can also provide assistance.
EDIT: another approach would be to use geolocation, if the source of these attacks is different from the origin of your users traffic.
Need to be careful with those. One was last updated 4 years ago and the other 7 years ago.
The emerging-dos.rules ruleset is available from the Emergingthreats.net Community Rules provider that is available on IPFire. So that list can be selected directly without any need for manual modification of IPFire.
The actual rules selected would need to be reviewed to see if any of the ones not selected by default should also be selected. You would probably have to have some idea about the type of DDoS attack being used on the game server to be able to select the best rules.
If you press the Save button it doesn’t start, is that correct?
If it is not starting after pressing the Save button then you would need to go to the console command line and run the following command which will try to start Suricata but give you the messages for why it is abnormally failing to start.
Somehow or other your suricata program got crashed causing it to stop but leaving the pidfile in place, which then stops the program starting. Normally when suricata is stopped the pidfile is removed as part of the stop process.
Run the command /etc/rc.d/init.d/suricata stop
This should get rid of the pidfile.
Confirm by running /etc/rc.d/init.d/suricata status
and you should get the
/usr/bin/suricata is not running
message.
Then go back to your Intrusion Prevention WUI page and press the Save button and it should then start.
Why did you select every ruleset in your whole list. Some of those might well cause you problems.
The only ruleset I mentioned to select was emerging-dos.rules. That is a Denial of Service specific ruleset.
If the WUI no longer works due to all the rulesets having been selected, I will have to think and check of what needs to be modified via the console to fix that.
Maybe other forum members know the best way to fix that.
@eykalzz Adolf’s suggestion is pretty clear. Suricata is an expensive program to run, and more rules you select more memory you consume. If possible, I would also consider location block, which is instead much cheaper in terms of resource consumption.