Skip to content
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

fail2ban #2

Open
bnkcrypt opened this issue Nov 16, 2017 · 3 comments
Open

fail2ban #2

bnkcrypt opened this issue Nov 16, 2017 · 3 comments

Comments

@bnkcrypt
Copy link

Hi I like your project would like to know does it work in Active - Active or master -slave

@buanzo
Copy link
Owner

buanzo commented Jan 5, 2018

In a cluster of N nodes (that all run fail2ban), you need:

ONE publisher.
N monitors
N subscribers

The monitor MONITORS /var/log/fail2ban.log and sends Ban/UnBans to publisher. Subscribers receive what the Publisher broadcast.

Does that answer your qyestion? Because standard active/passive master/slave does not really 'fit' into fail2ban architecture.

@m-ueberall
Copy link

For the record–in case you wondered whether it's possible to have more than one publisher (e.g., for redundancy purposes): Yes it is, but you'll need to modify the code accordingly (see https://stackoverflow.com/q/6700149/6145758).

@buanzo
Copy link
Owner

buanzo commented Nov 1, 2018

For the record–in case you wondered whether it's possible to have more than one publisher (e.g., for redundancy purposes): Yes it is, but you'll need to modify the code accordingly (see https://stackoverflow.com/q/6700149/6145758).

This is a great tip. I hope to integrate the support someday. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants