Yarik,
Yesterday using 0.5.4-5.14, valid ssh logins worked fine, and ssh
attacks were correctly prevented.
But upon restart, fail2ban failed to start. (I shutdown each night and
reboot each morning.)
/var/log/fail2ban:
2005-10-18 09:05:50,289 WARNING: Verbose level is 1
2005-10-18 09:05:50,297
On Tue, Oct 18, 2005 at 10:08:53AM -0400, Ralph Katz wrote:
Yesterday using 0.5.4-5.14, valid ssh logins worked fine, and ssh
attacks were correctly prevented.
Maybe fail2ban starts too soon?
That would be my guess too. fail2ban boots in rc2.d, so all relevant
modules should be loaded by
On 10/18/2005 02:24 PM, Yaroslav Halchenko wrote:
That would be my guess too. fail2ban boots in rc2.d, so all relevant
modules should be loaded by that time. I hope you don't use any
fast-boot tricks as to boot init scripts in parallel ()?
Plain vanilla sarge. No tweaks/tricks. Old PIII
On Tue, Oct 18, 2005 at 03:45:23PM -0400, Ralph Katz wrote:
As a non-programmer, I can't judge your proposed solution. Meanwhile
I'll check /var/log/fail2ban and restart fail2ban manually if needed
after each system reboot.
no need. for you if the cause is really missing iptables by the time
4 matches
Mail list logo
