POTENTIONAL FIX: etded.x86 getstatus exploit Options

[schnoog]

There`s nothing you can do against the incoming traffic.

But the data which "comes" ("" because that are spoofed IPs) from an IPTables blocked IP isn`t reaching the gameserver at all.

The only traffic direction you can "handle" is the outgoing traffic. If your server are empty, the outgoin traffic should be near 0.
(it is not 0, because HLSW, SL, TB and many more are requesting serverdata from time to time).

Maybe you can lower the limit to catch offenders, but when I see the stats (6500p 3,3kB/s vs. 580 1,8kB/s) the script seems to do what it was developed for.
Each incoming getstatus request amplifies the traffic in outgoing direction with a factor >5.

[Ligustah]

I just recently had to answer that question to someone else and I think came up with a rather simple example.

Suppose you have a mail box infront of your house. Every day you check the letters. There are some "spam" mails in there every day, so you sort them out right away and trash them, without even reading (or answering) them.
However, you cannot stop people from putting spam letters into your mailbox.

It's the same with software firewalls. You can prevent your server from "reading/answering" the packet, but it will still reach your machine (be put in its "mailbox"). There is nothing you can do about that, unless you control the upstream router (which you don't).

Hope this example clarifies the situation to people who might have not understood before.