Carpet Bombing attacks

@eykalzz I am not sure if you are still around? Your DDoS thread has been locked

I just read a bunch of articles about type of DDoS that you encountered a year go.

I think rate limiting connection per IP didn’t work

Did you figure out how to configure IPFire against these attacks?

Yes, I’m still active here. For TCP, it works for weak DDoS attacks, but if the attack is strong, there might still be issues. However, you still need anti-DDoS protection from the provider as well. For example, I’m currently using OVH, so I have to use their Game Dedicated servers. If you use anything other than Game Dedicated, it will go down 100% even with small DDoS attacks. That applies to TCP. But for UDP, it will go down 100% .. basically IPFire cannot filter DDoS on UDP ports.

1 Like

Thank you for the update.

So basically UDP is how they operate,. and you need big bucks to deal with something like that.

I found a Cloudflare press release from last week confirming that :

“The 29.7 Tbps was a UDP carpet-bombing attack bombarding an average of 15,000 destination ports per second,” Omer Yoachimik and Jorge Pacheco said. “The distributed attack randomized various packet attributes in an attempt to evade defenses.”

To summarize for those who don’t want to read the whole piece Aisuru got on the first page the using 4 million IP’s .

An incoming traffic like that seems impossible to handle unless you have the ability to stop it upstream.

IPFire has a few tools to handle “C2 & DNS obfuscation” and prevent your client machines to operate as one of the Bots, although that’s doesn’t seem to be an issue in your case.

Looking forward to hear more.