Modify SQL query to use 'bips' table instead of 'bans' for the count #1077
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use bips as it has the list of all persisted banned IPs. This should fix the incorrect count of banned IPs in the dashboard
Description:
Update query used in swag-f2b.py to pull the ban count in the dashboard.
Benefits of this PR and context:
I believe this should fix issue #444
How Has This Been Tested?
I ran the query directly on the database directly first to ensure the results match what I see from fail2ban-client. I then updated the query in swag-f2b.py and checked the count in the dashboard.I run swag in a docker container in a debian 13 VM
Source / References:
#444