Suricata / PfBlockerNG list conflict
There seems to be some conflict between the IPs that Suricata blocks using ETOpen and Snort VRT and those in the lists for PfBlockerNG.
Has anyone else seen this?
For IP blocking, best to use one or the other… No need to duplicate efforts...
So I'd recommend to remove the IP Rules (ie: ET Block) from the IDS and adding those feeds to pfBlockerNG...
isra last edited by
I created a custom aliases to IPv4.
I wish one of the internal lanip, it was not locked by pfblockerng.
I tried several solutions without success.
Can you help me in solving this puzzle? :D
thank you so much