janbar / ipfilter Goto Github PK

I want to request a few changes to the module to make it more flexible in AnyCast networks or services running with multiple instances.

1. Database reload
   -> Seems like the database itself only reloads when we are adding new IPs via the CLI in the server itself. If we run some sort of FileServer that syncs the database to multiple instances, the database will not reload since we are not doing changes via CLI, a command for a database reload (or automatic reloads) could fix this problem.

2. Database flexibility
   -> Imagining that we are building multiple databases, where we will store different values like Low Threats, Medium Threats, and High Threats, we would require multiple commands like the "deny, allow" ones and more variables, a flexible database would let us doing more than "allow and deny" for these cases.

Any of these would be possible?

Best Regards!

After compiling ipfilter I get on console that ngx_http_ipfilter_module.so has been generated on the obj of the path that I choose, but the file is never generated.

Wouldn't be more flexible if the NGINX module is separated from the ipfilter itself and we compile NGINX directly with it? Like testcookie or other modules.

Pretty nice module, but there is a question that remains in my head after reading the documentation:

1. Will each connection lead to a database lookup or are those maintained in some sort of caching?
2. Did any benchmark was done over the module?

Being that, obviously, for users who aim to build their databases this module has very potential for future usage, therefore I would request some kind of features such as:

1. Database reload: Such as the MaxMind module (geoip2), an auto reload time can be set, where, it will verify if the database has any change and apply those changes if they exist (See: https://github.com/leev/ngx_http_geoip2_module "auto_reload")
2. IP found behavior: Bringing flexibility to this database means, we can have a few other uses for the database such as databases where we enable Captchas if the IP is found on the database, to bring flexibility, in this case, the information (1 if found, 0 if not) could be saved into a variable that we could access (It's important that the "ipfilter_denied_url" keeps existing and it brings also some flexibility).

Those are both features that could be discussed, do you have some platform such as Skype, Telegram, Slack, or Discord where I could reach you to discuss further details?

Thank you!