since Z30 has improved object collisions, i think this is the best time for me to bring back my figure 8 server...

it's currently running TBO's (FXO-3%), and the only restriction AIRIO enforces is that you need to use street tires. (no using rally tires for cheap traction effects)

depending on turnouts, i may decide to hold weekly/monthly events.

enjoy!

I cant find it and join it

pm me your ip address, and i'll look into it.

I tried from few IP. I have dynamic IP.

it's not a problem with the ip itself, it's the range the ip's are in... i still need your ip address to determine what CIDR block you're in.

79.186.250.239
From this, it's working.

yes, i can confirm that range should be fine. the problem is, that i also host SSH accounts here, and some people can't secure their systems enough to prevent the propagation of SSH spam/DDoS bots, so I just block the ranges associated with those networks.

There is a nice little peace of software that allows you to analyse your logfiles by user defined pattern and use the gathered information for taking appropriate.

http://www.fail2ban.org

I use it since a long time to exclude certain ips from accessing servers,
after a few attacks, not only for ssh but also ftp, http, pop3 etc.

So there is no need for me to exclude whole subnets anymore.
I think it is the better solution to prevent brute force attacks.

Quote from yankman :

There is a nice little peace of software that allows you to analyse your logfiles by user defined pattern and use the gathered information for taking appropriate.

http://www.fail2ban.org

I use it since a long time to exclude certain ips from accessing servers,
after a few attacks, not only for ssh but also ftp, http, pop3 etc.

So there is no need for me to exclude whole subnets anymore.
I think it is the better solution to prevent brute force attacks.

yes, yes, i've heard all that jazz before, in fact, i've suggested it before. fail2ban does not do anything about distributed bots. i get those just as much as i do the type seen in past years.

Ok, nevermind.

You mean ssh bruteforce?
Just change the port and you'll get rid of 95-99% of bruteforce attacks.

And it's not a ddos attack. The purpose of it is to bring a machine of the network, not get access to the system by trying gazillion password and username combinations.

Or if you're blocking of subnets, you could also block of by specific ports. Make a new chain in iptables i.e. DROPBRUTEFORCE, add all ports that you want blocked in that chain and then -j DROPBRUTEFORCE on all of those subnets that you now just droped or rejected. Or even easier accept connections to ports that LFS uses before droping/rejecting the subnets.

Quote from xfirestorm :

You mean ssh bruteforce?
Just change the port and you'll get rid of 95-99% of bruteforce attacks.

why should i break RFC and piss off my users, because other people use "stupid" passwords?

and i didn't exactly mean DDoS, but when you have 500 or so computers pointed at you, it might as well be. the only thing that prevents it from denying service is the fact that i upgraded that server some time ago. in its previous form, the bots would consume CPU power normally used by the users, and that is a denial of service.

i'd be glad to [url="mailto:[email protected]"]continue[/url] this conversation, but the LFS forum is hardly the place to be talking about my entrepreneurial business practices.