Once I installed the package, I was able to configure it by going to Diagnostics -> ntopng Settings. Per their package description, “ntopng (replaces ntop) is a network probe that shows network usage in a way similar to what top does for processes.” To test my feeds, I tried to visit an advertising site directly, and the router blocked my DNS request!Īs a bonus, I also setup ntopng for some basic visualization. Once I had my feeds selected, I added them to my new DNS Group. To fix this you will need to remove the block, clear the feeds, clear the caches, and possibly restart your router. If you do this (trust me, I did at first), then you will only block your access to the actual block list feeds in question. NOTE: Do not put a link to the Pi-hole ad block list directly, but rather to each individual entry. I started with a number of lists from the Pi-hole ad block list. Selecting the DNSBL Feeds menu option and clicking “Add” allowed me to create a new DNS Group with any number of block list feeds. With the basic settings in place, it was time to set up my actual block list! I enabled DNSBL, set my Virtual IP to 10.10.10.1, and kept my listening ports and interface default. I enabled the blocker, told the settings to persist, and set the CRON job to run every 3 hours.Īfter I enabled the blocker, I clicked on DNSBL to configure my block list.

Once I installed the plugin, I was able to configure it by going to Firewall -> pfBlockerNG. Manage IPv4/v6 List Sources into ‘Deny, Permit or Match’ formats.”

To quote their description, “pfBlockerNG is the Next Generation of pfBlocker. To start, I installed the pfBlockerNG package by going to System -> Package Manager -> Available Packages.

Cannot access ntopng