Firebog list O2 (Movistar, Spain), problem

[Bundy]

Apparently, without obeying many reasons, my IPS would be doing some kind of blocking of the Firebog lists, before everything worked very well, but perhaps this could have links with the issue of Cloudflare opening a legal case against "La Liga" for soccer events and illegal IPTV services, because many users have been affected in their personal services, projects, even the Telegram messaging app has been blocked during these global bans and little or no filtering.

I can't do a "pihole -g" or through the web interface without failing outgoing connections to lists like:

• https://v.firebog.net/hosts/static/w3kbl.txt
• https://v.firebog.net/hosts/Admiral.txt

Without being forced to make a VPN connection on my router, thank goodness I have a lifetime paid VPN service that works for this router, since neither by changing the pihole upstream DNS to Google (if this does anything) nor by clearing the DNS cache of browsers, or systems, nor even by configuring iptables to the outgoing firebog IP I can update normally.
Proof of this is that on the website: https://firebog.net/ I don't navigate to those URLs freely if I don't use a VPN plugin in Chrome.

I don't know if you have any suggestions in this case, I imagine the lists and pihole in general are not updated so often that this is needed regularly, but it would be nice if internet services were provided with absolute transparency, it's a shame.

Thanks anyway if you can't give me any additional help.

[chrislph]

Here's a way to get around it. Enable your VPN, either on the router or in Chrome, or even using your cell service as a data hotspot, and right-click all the files you want and save them in a folder on your computer. You can then turn the VPN off again or return from the hotspot back to your home network. So now you have the updated files on your computer.

Then activate a simple web server on your computer. To do this, on Linux or Mac running python3 (note you may need to prefix this with sudo, test it):

python3 -m http.server 80

On Windows you can use something like HFS, a free tiny web server that lets you run an internal webserver in a folder on your computer. Use that to share out your folder with the files in.

With that done, you can now access these files on your network by going to the relevant address in your browser, eg

http://192.168.x.x/adlist_file1.txt
http://192.168.x.x/adlist_file2.txt
etc

Finally, in Pi-hole, go to Adlists, remove the Firebog addresses and use your internal addresses instead. You only need to do this for those adlists where you have to use your VPN. Other adlists, which work normally, can be left as direct entries in Pi-hole.

So to update Gravity, you grab the latest adlists and put them in the folder, then turn on the internal webserver, then go to Pi-hole and go to Tools > Update Gravity. Pi-hole will essentially "download" the adlists from your computer instead of Firebog.

  [i] Target: http://192.168.1.10/local_example.txt
  [✓] Status: No changes detected
  [✓] Parsed 34 exact domains and 0 ABP-style domains (ignored 0 non-domain entries)

It's a little bit of messing around, but it keeps the VPN stuff away from Pi-hole and means you can use any method that works to get the files, eg browser tools, etc, which would not have worked with Pi-hole.

[Bundy]

I understand that Pi-Hole identifies local or internet lists because you edit how to get it, local or online, right? That is, once downloaded by hand and loaded on a server, Identify that you should get them from there every time you make a "pihole -g" or gravity in web version.

Thanks.

[Bucking_Horn]

We have received some reports of firebog lists being inaccessible recently, where a router/firewall turned out to be blocking access.

Are you perhaps using Ubiquiti/Unifi equipment, or does your router subscribe to a DoH IP blocklist?

[Bundy]

I don't use Ubitiqui products, but it seems that it was a temporary block, I don't know if yesterday there were any services involved like the football I was commenting on. Today everything seems to be working, impressive. And also in the link you provided me, the WhoIS of Firebog is shown to be hosted on Cloudflare... if you add 2+2, it equals 4, it was a network/operator thing, once again.