On Wed, Mar 31, 2021 at 11:13:51AM -0000, Michael van Elst wrote: > That's the more logical way. blocklistd works as designed and the login > failures trigger an entry in the blocklist. If you don't want to block > specific IPs, allow them by a specific rule, then it's also more clear > what is allowed and what is not by looking at a single place.
Thanks. Here the IP to whitelist is dynamic. I can arrange to put it in a file, but it may change and the file will be modified accordingly. What's a good way out to handle this? -- Mayuresh
