-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Manually ban/unban IP #41
Comments
Hello @ADeeeee, Thanks for your interest in this Traefik plugin! That's because there is no current way to do that once traefik started. But you can manually whitelist or blacklist IP prior to starting the reverse proxy by doing something like :
|
Hi Tom, Thanks for the reply. I do have the whitelist already. Does it work if I edit the middleware by adding a banned IP in whitelist after the IP got banned? This would be a nice workaround if it does. --edited--
IP subnet range:
|
When you update the plugin configuration, Traefik reloads the plugin entirely. So no more banned IP. Thus, if you whitelist an IP, it should work right in your case.
No
Yes |
Hello Tom, I've tried it on Kubernetes recently and found few issues and situations:
Just FYI and I guess I will wait for the features and also the stable plugin environment in Traefik. This is very cool. I hope I will be back one day it matches my requirement. |
Hi @ADeeeee,
For now, we expect our users to know the risks and implications of a harsh f2b rule.
As I said, there is no current way to unblock IP addresses dynamically. Restarting Traefik should be enough to clear the blacklisted IP pool. |
Hi all,
I've searched for a while and it seems there's no description on the Internet or in README about how people ban or unban the IP addresses manually once it got banned via this middleware. I used this function sometimes when some allies got banned by accident or the fillter is just too strict.
My plan is using this middleware in my Kubernetes cluster with Traefik Ingress. Is there any way to do it? It'd be so helpful rather than only waiting it timed out.
e.g.
The way I use it via Ubuntu standalone:
fail2ban-client set [RULE-NAME] ban/ubanip [IP]
The text was updated successfully, but these errors were encountered: