On Thu, Aug 25, 2005 at 03:00:37PM +0200, Daniel Gubser wrote: > Here is a quick answer from Mike Rash: > > > try executing "psad -F" before starting psad. I > > think the reason psad could not add the blocking rule is because > > the IP is already blocked. Psad may have lost track of the IP > > because of a bug with the auto-blocking time outs. Executing > > "psad -F" should restore things to normal. Note that the > > upcoming psad-1.4.3 release should have much improved auto- > > blocking capabilities.
It's probably exactly what you expected, but here's the output anyway: # psad -F [+] Flushing Netfilter IPT_AUTO_CHAIN chains... [+] Flushed: PSAD_BLOCK_INPUT. > Does this solve your problem (psad -F)? It doesn't. :-( BTW there have been cases in the past where things did work. Is it possible that somehow it matters whether PSAD_BLOCK_INPUT already contains a blocking rule or not? Jeroen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
