1
17.7 Legacy Series / pfBlockerNG on OPNsense
« on: December 30, 2017, 11:25:58 pm »
Hello OPNsense community!
For a customer i need to install a new gateway/firewall. I never heard of OPNsense before but i was pretty familiar with pfSense. I understand the reasons to fork the project and the more i read about it the more sense it makes.
But i have a problem with OPNsense that prevents me from using it in production.
In pfSense there was a plugin called pfBlockerNG. That plugins used a list of domains, resolved their ip adresses and added firewall rules for them.
I don't see a similar thing in OPNsense right now.
There is only domain based blocking by using a HTTP/HTTPS Proxy. I can't use that because not all devices in the network are configured to use a proxy nor i can force them to be.
While researching i found out about IPS and using "aliases" (https://forum.opnsense.org/index.php?topic=2137.msg6867#msg6867)
But i did not find the alias settings inside IPS.
Is there any way to achieve the same functionality in OPNsense?
Thank you for your time and effort.
For a customer i need to install a new gateway/firewall. I never heard of OPNsense before but i was pretty familiar with pfSense. I understand the reasons to fork the project and the more i read about it the more sense it makes.
But i have a problem with OPNsense that prevents me from using it in production.
In pfSense there was a plugin called pfBlockerNG. That plugins used a list of domains, resolved their ip adresses and added firewall rules for them.
I don't see a similar thing in OPNsense right now.
There is only domain based blocking by using a HTTP/HTTPS Proxy. I can't use that because not all devices in the network are configured to use a proxy nor i can force them to be.
While researching i found out about IPS and using "aliases" (https://forum.opnsense.org/index.php?topic=2137.msg6867#msg6867)
But i did not find the alias settings inside IPS.
Is there any way to achieve the same functionality in OPNsense?
Thank you for your time and effort.