Upgraded to 2.02.02 and Sentinel flood banning too many

Regular Joined: Nov 27, 2005 Posts: 58

Upgraded to 2.02.02 from RN76v1 and this morning Sentinel banned 30 people for flooding. I changed it to direct them to the default flood page for now instead of banning. Everything else seems ok so far.

Any ideas ?

Posted: Sun Nov 05, 2006 12:11 pm

I would recommend upgrading to the latest version of Sentinel.

I believe the flood protection was removed for a brief period, then reintroduced once it was fixed.

Posted: Sun Nov 05, 2006 12:30 pm

Are you sure they were flooding and it wasn't the proxy blocker turned up too high?
Sorry, I just had to ask!

If they are causing a flood trip, then it might be set too low for your needs.

Posted: Sun Nov 05, 2006 12:44 pm

Post delay 5, get delay 3, proxy blocker is off.

Any suggested settings, or is this version broke ?

Posted: Sun Nov 05, 2006 1:05 pm

The fact that it was 30 people not the odd one suggests there is a problem, possibly with the site itself - it may be reidrcting back on itself causing the flood to trip.
There is nothing in the version you are using to cause this as RN you are using is well tested and in use on a great many sites.

Do you have any additional modules installed or java code anywhere thats not part of the standart distribution?

registered · Posted: Sun Nov 05, 2006 8:49 pm

I would upgrade -- if it were me -- to at least 2.5.02, if not the latest of 2.5.03.

Posted: Mon Nov 06, 2006 5:33 pm

This was Sent 242pl5. Apparently there were problems with this particular flood blocker which were worked on in subsequent patches.

Running 2.5.0.3 now and so far so good.

Posted: Mon Nov 06, 2006 6:34 pm

BTW, I also use this in my robots.txt to help out the search engines a bit (if they respect the crawl delay switch):

User-agent: *
Crawl-delay: 10

I had early on issues with either Google or Yahoo getting banned... cannot remember which, and this stopped it too.