Ah, so a DNS issue then? That would be unrelated to the auto firewall rule ordering you were seeing.

Steve

@gwaitsi
Have a look at https://www.reddit.com/r/pfBlockerNG/comments/jt9k89/pfblockerng_malwarebytes_telementery_increased/

https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#segmentation-fault-in-pkg

@Draco

Thanks I like the idea of puutin win update or global dns on a whitelist
Havnt come to my mind just yet
Thx

This worked. Thanks Ron

I add jasonhill's to a online doc and provided it as feed list.

Thanks both

Excellent. I just re-enabled all the feeds and the whitelisting seems to be working.

Thanks!
Matt

@sreeram
I don't use it, but I suspect you're right.

The DNS-BL VIP uses 10.10.10.1 by default. It looks like you're already using a subnet containing that so you need to change the default value there to something you're not using before it can start.

Steve

Yeah, probably not the best idea but it works. Im thinking to run a hotspot and dont want to find myself feeding bots.

I'll get that done this evening or tomorrow morning. I guess it goes without saying it's not a wide spread problem but something out of wack with my config. That you sir!

@trilobite
Yea, I use about 1/2 the feeds in Malicious_2, basically chose the ones that give the least grief. Frankly, relying on lists that someone else decides on will always get some domains blocked that you want. Between being choosy (yea this takes time to tweak) with what lists I use, maintaining white lists and setting the TOP1M whitelist to the top 5k, I rarely have an issue. None of this is turn-key it is all trial and error and frankly never ends. Lists go from good to bad and vice versa, lists go away and new lists popup. I peak in there every week or two to validate that the lists I chose are still 'live' and being maintained.

Yes very simple, configure cloud DNS ip's on the general setup screen under "dns server settings"

Then go to services -> dns resolver.

Tick the box next to "dns query forwarding"

Save, apply, done.

I read your post, checkpointed my VM and upgraded pfB. Saw the same thing. Rolled back, Maxmind back. Rolled forward, Maxmind still there... Huh. Rolled back, upgraded pfB again, Maxmind there. Maybe try dumping browser cache or rebooting pfSense. All I got.

If you set pfBlocker to "native alias" instead of block, that will just create an alias and you can create your own block/allow rules however you want them.

@provels I'm using the free version so I don't really have any active scanning going on. I think I'll stick with just not having it running at the moment, but that's not a bad idea.