T
T
TRUEC0DER2021-03-31 19:52:17
linux
TRUEC0DER, 2021-03-31 19:52:17

DDoS protection directly on IP?

There is a server with an open port, which must be open, and there are unscrupulous people who wish us and the server everything bad, who use a paid stresser to send attacks to our server (The server is rented from Hetzner, and according to them there should be protection against attacks , but not visible..). From attacks, the server starts to suffocate, the server is configured with IPTables, fail2ban + firewall from Hetzner is configured to allow only TCP requests, to no avail. Is it possible to do something on the server side without resorting to the hardware? Server specs below.


Intel Core i7-8700

NIC 1 Gbit
- Intel I219-LM

2x SSD M.2 NVMe 1 TB

4x RAM 16384 MB DDR4

Answer the question

In order to leave comments, you need to log in

5 answer(s)
V
Vladimir, 2021-03-31
@MechanID

If you don’t have money for a normal ddos ​​protection, then your options are as follows:
1 smoke the netstat exhaust with different keys and think whether it is possible to distinguish the client IP from the attacking IP by the number of connections, if so, smoke the documentation on the iptables connlimit module
2 smoke the tcpdump exhaust or wireshark we are looking for a pattern in the packets that bombard you - in text or byte order, if we have found the iptables documentation for the string module.

N
Nadim Zakirov, 2021-03-31
@zkrvndm

Contact your hosting provider, as a rule, most hosting companies have a DDoS protection service.

V
Vladimir Korotenko, 2021-03-31
@firedragon

Crushing the channel is the easiest thing. And from this, few will save. And then you need to think. After all, the user somehow acts, so cut off these scenarios. After all, let's say 200 rps from one user to the search engine is unlikely? Then ban this bot.

K
ky0, 2021-03-31
@ky0

the server is configured with IPTables, fail2ban + firewall from Hetzner is configured to allow only TCP requests, to no avail

Apparently, some of the listed measures are not set up well enough (do you have, for example, a restriction on the geolocation of addresses?). If the entire channel is surviving, this is one thing, but if it rests on the processor, it means that you are not actively pushing the IPs, and the application, therefore, is poorly optimized.

V
Vitaly Karasik, 2021-04-01
@vitaly_il1

1) For a port that should be open to users - open a support ticket from Hetzner with a request to protect it.
The second option is Cloudflare
2) Close all "your" services for the Internet, open for your IP or via VPN

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question