@jflsakfja:
Don't care about real time lookups, but a per minute lookup would be nice to stick into a variable. Just saying… ;)
Can't pfsense's existing setup be used for that? Since the majority will be doing their realtime lookups through unbound, it should be pretty fast, even when used in realtime, with regards to keeping up with traffic.
Not talking about a 10Gbps snort (don't even know if it can push up to that)/suricata looking up a billion IPv6 addresses. Talking about sticking an alias to suricata, having it look up a single (or few) hosts to allow for a VPN for example to be tightened down. Used with an allow only VPN access from this host suricata rule, for example. Yes that can be done with normal pfsense rules, but it's an example. :D
Sorry for taking over the thread Mr. Jingles, but I fixed it near the end ;D
I have considered perhaps leveraging the filterdns daemon and its alias tables within pfSense to allow some small level of FQDN support for pass list entries. It would take some significant mods to the way the old Spoink output plugin for Snort has been engineered. Today it reads a simple text file of IP addresses and stores them in a linked list in memory once at startup. Whenever a "block or no block" decision is required, that in-memory IP list is scanned to see if the source IP, destination IP or both are in the list. If true, the block is not inserted into the <snort2c>alias table in pf. Of course the "which IP to block" setting is also part of the logic.
Bill</snort2c>