Val D.
Very Senior Member
This is the only downside on my current config. The Xeon X34xx range doesn't have AES-NI.
There is information posted in Netgate Blog about AES-NI: https://www.netgate.com/blog/more-on-aes-ni.html
Yes, good to have, but not critical. It is no longer a requirement for future pfSense releases, so your system should be good.
I am interested in pfBlockerNG but also concerned it would impact performance and throughput.
Your system is probably more loaded with traffic compared to mine (looking at all the gear in your signature). Test it, but I don't think you'll notice any difference on this hardware. My CPU is way overkill, it's actually >100% faster than Xeon X3430, but to see it coming close to 50% utilization I had to run OpenVPN AES-256 with speeds about 280Mbps, Suricata with hundreds of rules (testing, everything ETOpen available) on both WAN/LAN and pfBlockerNG with like 10 heavy lists (testing again, large aggregate lists like FireHOL, StevenBlack, etc.) on both IP and DNS all in the same time. This is with TurboBoost disabled @3.4GHz max clock speed. Far from a normal working setup, though. If I leave it with the settings above, plus blocking enabled in Suricata, I get a "user complaint" in next 30 seconds. After adjusting all the settings the way I need them (not all VPN traffic through the router, specific rules and lists only, etc., i.e. "wife safe settings"), I keep the CPU @1.6GHz through PowerD (minimum) and it still doesn't reach 50% CPU load. My CPU @1.6GHz is slower than X3430 @2.4GHz, so I believe you have more than enough room in processing power.
I run pfBlockerNG_devel version. It has some extra options and is easier to setup with blocking lists ready, sorted by category, provider, false positives reputation, update frequency, etc. You can match some Suricata rules with pfBlockerNG lists in the same category, if you like to. This is how I have it setup. No perfect match between the rules and the lists, as expected, but it works well.