route: 185.175.11.0/24
origin: AS43203
mnt-by: rsaf-mnt
mnt-by: mcnetcz-mnt
created: 2018-03-01T18:41:08Z
last-modified: 2018-03-01T19:39:13Z
source: RIPE
notify: roman@paskov.cz
remarks: ****************************
remarks: * THIS OBJECT IS MODIFIED
remarks: * Please note that all data that is generally regarded as personal
remarks: * data has been removed from this object.
remarks: * To view the original object, please query the RIPE Database at:
remarks: * http://www.ripe.net/whois
remarks: ****************************
BlackList para blockear Proxys anonimous con pfblockerNG
I don't have any experience with these feeds for Proxy blocking... But there are some here (Search for "proxy"):
https://github.com/firehol/blocklist-ipsets
This is one example. Also make sure that you click "RAW" and use those URLs for the Source URL in pfBlockerNG.
https://raw.githubusercontent.com/firehol/blocklist-ipsets/master/proxylists.ipset
https://forum.netgate.com/search?term=https%20cert%20error&in=posts&matchWords=all&categories[]=62&sortBy=timestamp&sortDirection=desc&showAs=posts next time use the search option yourself.
I personally switched from Snort to Suricata for reasons mentioned here.
https://forum.netgate.com/topic/141946/to-snort-or-not-pfblocker/4
I didn't notice much difference in the GUI, configuration, or functionality aspect between the two. In terms of tuning rules, they seemed pretty much the same to me as well. In my opinion, once I figured out Snort the learning curve was not high for Suricata.
Just a quick follow up to my post to advise that my "problem" has not reoccurred since taking RonpfS advice to reduce the number of entries in my pfblockerNG block files.
Once again my thanks to all who took the trouble to respond.