The foillowing situations >>>>

[oceano]

1st example: Someone create 20 chars, mass log it and go to a safe area(all together) and start spamming.. the server for some 5-10 min the server start lagging.. and maybe it crash... any idea to avoid it?

2nd example: Someone start spamming your normally 7171 port and makes some 500 connections all zero bytes send and zero received and at 7171, and then your server crash any idea to avoid it?
Firewall? what one?

3rd example: This one is sprut problem... he just put your ip and the login port at program and imediatly crash your ot.

O Well i will expose my solutions and i am here to hear all yours too:

I think that all this problem can be solved in the distros with simple rules.

but we havent. so...
first case.. block mcs? not block but limit for 3-4-5 same ips?

second case good firewall? i didn t find a software... that control a used port... and limit the connection spam of a same ip.

Third case.. distro only... its a bug.., of tfs 0.3.5

Give me your ideas.. too lets share it... and show more troubles maybe it makes the job of realeasers of distro easier!!

 

[nclx]

0- u gay

1- Delay onlogin...

local lastLogin = 0
local timeNow = os.time()

if(lastLogin + 2 >= timeNow) then
   return FALSE
end

lastLogin = timeNow

Didnt test, but you will...

2- Yes, firewall, obviously... and about the port, you kidding... the noobest firewall can prevent that... also, wtf, 0 bytes?, 0 bytes = no info -.----------------...if linux, iptables.

3- Program magically crash the ot, rox, biggest lie