-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bearDropper not actually banning attackers? #10
Comments
I have more proof from today that bearDropper is actually not working ...
|
I've just noticed the same on my system. It was working until recently but definitely not now. Sadly, I think this project is abandoned as it's not been updated in 2+ years :-( |
is there an alternative? |
I've tested this a few days ago and it was working fine. Maybe it's something about your setup. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have been running bearDropper for ages, as part of David's build of LEDE, but now looking into the Logs , it actually doesn't seen to be blocking the offending IP's.
My current configuration has this section:
This LEDE Version from David's 502 builds:
Lede SNAPSHOT, r7093-4fdc6ca31b
And the latest bearDropper version.
And I found this in the log today:
See that the "ban rule" was inserted twice ( instead of just once?) , but the offending IP kept trying after that ? It all happened within 2 seconds... maybe this is just a syslogd delay in the messages?
@robzr , can you take a look?
BTW: iptables -L has the ban rule on it .
The text was updated successfully, but these errors were encountered: