You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off thank you for this, I've got it up and running and already within 10 minutes it's blocked around 200 requests.
I had a quick question as the doc was just a tad unclear (to me). Along with this auto refreshing list of IPs, If I want to add my own custom list of IPs can I do that with the command mentioned under the "Usage" section?
sudo ipset add ufw-blocklist-ipsum a.b.c.d
The reason for my confusion is the way it's worded, it sounds like that command is only used for testing after doing a flush-all and once your testing is finished you'd restore the blocklist.
If I add manual entries using that command, will they stay, or would they be wiped when the cron grabbed the updated list once a day?
Would it be better to read in my own custom list using ufw's commands, something like:
while read line; do sudo ufw deny from $line; done < custom_block_list.txt
Void4ever
The text was updated successfully, but these errors were encountered:
First off thank you for this, I've got it up and running and already within 10 minutes it's blocked around 200 requests.
I had a quick question as the doc was just a tad unclear (to me). Along with this auto refreshing list of IPs, If I want to add my own custom list of IPs can I do that with the command mentioned under the "Usage" section?
sudo ipset add ufw-blocklist-ipsum a.b.c.d
The reason for my confusion is the way it's worded, it sounds like that command is only used for testing after doing a flush-all and once your testing is finished you'd restore the blocklist.
If I add manual entries using that command, will they stay, or would they be wiped when the cron grabbed the updated list once a day?
Would it be better to read in my own custom list using ufw's commands, something like:
while read line; do sudo ufw deny from $line; done < custom_block_list.txt
Void4ever
The text was updated successfully, but these errors were encountered: