@mtarbox said in Ant-techs.is/ip-blocklists:

There is a better way to block youtube ads.

http://jasonhill.co.uk/pfsense/ytadblock.txt

YMMV

I have been using this list in pfBlockerNG almost since it was posted... the list is still there but it fails quite regularly since the owner put some cloudflare anti-ddos measures in place. The list still seems to be updated... it's still is under a pfSense directory... it's still accessible via a browser with patient human at the keyboard.
I've talked to Anthony and we've both tried to contact "Jason Hill" but with no joy.

Is Jason on the Forum? Does anyone know Jason? Does anyone have viable contact information?

Thanks in advance if you can help.

@chrcoluk said in How to force MaxMind update right now?:

So basically by mistake I just put my account ID in the license ID box and as a result have had no updates since Dec 2019.

This is now fixed, but does this mean I need to wait 3 weeks or I can I force an update?

To update Maxmind.com, enter the following at command prompt: php /usr/local/www/pfblockerng/pfblockerng.php dc

@viktor_g

Thanks - that helped.

I also uninstalled and reinstalled pfBlockerNG, and the feeds that were previously not updating (apart from the ones listed in the post that you linked to) are now updating. So problem solved for now I guess.

@johnpoz said in Streaming is being blocked on Roku:

You have no name on your views.. so yeah can see why it would balk at that.

access-control-view: <IP netblock> <view name> Set view for given access control element.

And you shouldn't have that 2nd server: in there either.

Wouldn't it be just easier to assign your roku a different dns, say 8.8.8.8 - not sure why your roku would need to resolve anything on your local network anyway.

Thank you all for the responses.

EDIT: I had to go back and edit my original reply. I realized I am forcing DNS requests over CloudFlare 1.1.1.2 and 1.1.1.1. I also have two NICs and two different LANS, 192.168.1.0 and 10.1.1.1

I changed the Resolver code:

server: access-control-view: 192.168.1.0/24 dnsbl #All devices on this subnet run through pfBlockerNG DNSBL access-control-view: 192.168.1.121/32 bypass #Roku IP is bypassing pfBlockerNG DNSBL view: name: "bypass" view-first: yes view: name: "dnsbl" view-first: yes include: /var/unbound/pfb_dnsbl.*conf

However, I am noticing that ads are allowed for everything on 10.1.1.1 unless I add

access-control-view: 10.1.1.1/24 dnsbl

and the full code looks like this:

server: #All devices on this subnet run through pfBlockerNG DNSBL access-control-view: 192.168.1.0/24 dnsbl access-control-view: 10.1.1.1/24 dnsbl #Roku IP is bypassing access-control-view: 192.168.1.121/32 bypass pfBlockerNG DNSBL view: name: "bypass" view-first: yes view: name: "dnsbl" view-first: yes include: /var/unbound/pfb_dnsbl.*conf

Apologies for the delay in responding, I never got any email notifications that I received responses to my original post. Weird.

This makes more sense than pfblocker being the issue. Another option would be to assign your phone(s) a static lease through DHCP and then create a rule which allows any traffic from that IP out from any port. I don't have Vonage, but in the office we have a different VOIP service and that's what I ended up doing. I followed all the documentation and opened all the ports they said were required and still had issues on some phones, so I got tired of that game. I added all phones to an alias and with one rule solved all those issues.

Thanks for fixing the cert. All good now. 👍

@pooperman Click on the : the '/' isn't allowed.

@netblues said in bbc_c2 fails to download:

mething was forgotten on the bbc site and now things are "fixed" .

https://www.reddit.com/r/pfBlockerNG/comments/i139ob/fyi_bambenek_feeds_gone_commercial/

@johnpoz
Green Lock was a figure of text so to speak, I have a grey lock to be accurate and thank you for your help.

@dsimmons1977 Well, that's unfortunate.

I'm running the pfBlockerNG-devel 2.2.5_33 if that helps.

My pleasure. 🙂

@CodingGenie NVM ALL GOOD FIXED IT! It won't let me delete the post.

Has it been released ? Last time I used pfblocker for a few month ago I didn't see any Regex blocking option.

Best Regards

@bmeeks Thank you bmeeks I am somewhat tech savvy but other times I am paint by number type guy I watched abut 6 different videos on how to setup pfblocker and not one of them had anything for putting in the settings for a preferred DNS when doing a static IP address on a computer and out of habit I put in opendns server IP

@bhjitsense said in Is my install of pfBlocker hosed?:

I found what was causing the issue.

The forum is good, because it makes you think... 😉

I found this answer elsewhere that will allow maintaining a proper whitelist instead of disabling the entire Top Spammers feed . "You can add Canonical, Inc's ASN to the IPv4 source list and permit outbound. It's AS41231.

In the IPv4 category, click the green Add button at the bottom. Click the Format pulldown and select ASN. Click the State pulldown and select ON. In Source, type in AS41231.

Under Settings, click the Action pulldown and select Permit Outbound. Under Update Frequency, select Weekly.

After you save it, force an Update or wait for it to run at the next scheduled time.

Many enterprises have at least one ASN, so I think it's a pretty good tool to use to automatically maintain an IP whitelist for each organization.

You can use https://bgp.he.net/ to search for ASNs.", /user/ontheroadtonull

@dgall P.S when I changed my computer ipaddress I cleaned the Cache cookies history and rebooted before retesting

@RonpfS
Got it, thanks

@securli said in Bug report: PfblockerNG add 1.1.1.1 when threat source input is empty:

@JeGr Thank you very much, this bug is so stupid, it should check the downloaded file is zero or not instead of random block an IP address.

That's what it does. But pf can't handle empty files/lists so it has to be at least one entry in it, that's why in the old version there was a default value - 1.1.1.1 - long before that IP was made a DNS service by Cloudflare and APNIC. That's why it was changed to 127.1.1.7 per (new) default.