RESOLVED: pfblockerng never installed shows in config.xml???
-
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
every tracking url that in the above database is related to website tracking
If I have never used or want to use package pfblocking why does it show up in my config.xml?? did not approve of this.
-
You are seeing that list in the config? I don't see it in your screenshot.
If you have that pfBlocker in the config it must have been installed at some point. The config is not removed by default when you uninstall it.
-
S stephenw10 moved this topic from Problems Installing or Upgrading pfSense Software on
-
@stephenw10 That's really weird right, let me show the config that has it, I really have never installed it not even once.
-
-
@stephenw10 Is there a way to manually remove it?
-
I installed it it has many settings. keep shows off but on in config.xml I hardset off ran rm /tmp/config.cache and reset and uninstalled. Interesting right? It's gone now. Thanks for reply
-
You can just remove all the pfBlocker config if you don't have it installed.
If you run the setup wizard when it's installed it will add adblocking unless you choose not to.
-
Seems possible.
Based on other posts you've made, in regards to things like shalla list and other items as recently as early November, you have previously had pfblocker installed.
Then you likely uninstalled it either with or without "keep". This was likely done while pfb was on a version prior to the current one.
@JonathanLee said in pfblockerng never installed shows in config.xml???:
I installed it it has many settings
If I am reading the post correctly, you installed it today again (right?) and would have got the _7 revision, then you uninstalled with keep turned off.. is that correct?
the one and only line that change from _6 to _7 has everything to do with the config path being in the wrong format in the older versions...
- config_set_path('system','earlyshellcmd', + config_set_path('system/earlyshellcmd',you would have had different code ...
-
@jrey O yeah I remember that years ago. It keep the settings that long WOW.
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
That list just grows and grows, even with CCPA and GDPR, should some of the privacy abusers have been fined by now? This is unreal the amount of tracking and privacy issues.
CCPA and GDPR was suppose to start to get rid of some of this, and protect the consumers privacy rights. This list is massive now, at least pfSense cares. But WOW have you looked at the size of that list now?
-
Old config is gone this is fixed
-
@JonathanLee said in pfblockerng never installed shows in config.xml???:
is gone this is fixed
glad you got it sorted.
But your comment on Shalla list wasn't that long ago, in early November, when you commented about a list you use instead as I recall. So the assumption I made was that you simply had used pfb before, and not so long ago. Likely uninstalled it, then reinstalled it today with different code and got different "better" results.
did not approve of this.
honestly that ^^ was funny. and actually you kinda did...
"on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE"
-
@jrey What funny is it listed 10.0.0.1:8081 in the config for it, that is the guest wifi and I didn't have that enabled back then I didn't even have the compex card. Weird
-
@JonathanLee said in RESOLVED: pfblockerng never installed shows in config.xml???:
What funny is it listed 10.0.0.1:8081 in the config for it
That could be the DNSBL webserver IP address and port. By default it's 10.10.10.1 but you can change that.
-
@stephenw10 thanks to explain how that works. I was amazed about how much old items are listed in that config.xml file I never had pfblocker set to save configuration and but in the config.xml it was set to save. When I reinstalled it to remove it it still was set to not safe, I had to manually set to no and it finally removed it.
