Live data from Hacker News

Blocky – a DNS proxy and ad-blocker for the local network

0xerr0r.github.io

51–60 of 110 posts

Re: Blocky – a DNS proxy and ad-blocker for the local network

#51
post #21

My problem with network-level adblockers, also PiHole is that they break a lot of services (yeah it's mostly sloppy or malicious intent from service provider but still). On a browser you can quickly disable uBlock for that site, it is much more tedious for these services - also because it's not even clear that the filtering is causing the problem, also because it maybe someone else on the network experiencing the pro…

I have a silly "trick" for this. In Firefox you can add a SOCKS5 proxy and click "Proxy DNS with SOCKS5 proxy". This bypasses the system DNS. So for example, if you make a container with this, then you can just quickly open the URL that's blocked in the other container and it will bypass the network-level DNS adblock. There are other ways to do it without a container, I'm sure, maybe with an add-on/toggle or somethin…

That's a clever trick. It's also pretty trivial to set up a SOCKS5 proxy with Shadowsocks if it's desirable to keep that DNS resolution local.

Re: Blocky – a DNS proxy and ad-blocker for the local network

#52

My problem with network-level adblockers, also PiHole is that they break a lot of services (yeah it's mostly sloppy or malicious intent from service provider but still). On a browser you can quickly disable uBlock for that site, it is much more tedious for these services - also because it's not even clear that the filtering is causing the problem, also because it maybe someone else on the network experiencing the pro…

I use a quick setting to quickly switch between ad blocking dns and normal dns for bad websites or captive portal. https://f-droid.org/en/packages/com.jpwolfso.privdnsqt/

Pretty cool. If you have adguard home and google assistant, you have access to a switch that can enable/disable adguard home protection. So with the homeassistant app you can add that as a quick tile as well. The only caveat is that this will disable it across all devices.

Re: Blocky – a DNS proxy and ad-blocker for the local network

#53

> Blocking of ... response IP addresses (against IP lists) So blocky can block IP addresses? If so it's more powerful than traditional DNS blockers like Pi-Hole and AdGuard Home. > Logging of DNS queries per day / per client in CSV format or MySQL/MariaDB/PostgreSQL database May want to include a time series database, like InfluxDB For those needing layer 7 control, https://github.com/andybalholm/redwood is a nice Go…

> May want to include a time series database, like InfluxDB

Seems to have native support for Prometheus, so that seems to be the TSDB to use for the project. That said, if you're at the point where your record density takes advantage of the benefits of a time series DB vs a well indexed RDBMS, I'd also imagine that you're beyond the scope of this little service.

Re: Blocky – a DNS proxy and ad-blocker for the local network

#54

Can't block Youtube shorts with these DNS adblockers, I know I can use browser extensions on a computer (and I do), but I really want to block shorts on iOS/Android apps. Tried the squid https proxy rabbit hole, but could not get it to work with mobile devices. Any hints?

Just don't go to the shorts section? Or are you talking about the ads in the shorts section?

The shorts section on mobile is kinda inbetween all other videos. If you don't pay attention you can end up on one quite easily...

And then it's back to doom scrolling

Re: Blocky – a DNS proxy and ad-blocker for the local network

#55

My problem with network-level adblockers, also PiHole is that they break a lot of services (yeah it's mostly sloppy or malicious intent from service provider but still). On a browser you can quickly disable uBlock for that site, it is much more tedious for these services - also because it's not even clear that the filtering is causing the problem, also because it maybe someone else on the network experiencing the pro…

I have a handful of different wifi SSIDs set up on my network at home to help with this, some route their DNS queries through a pihole instance and others (say, without the “AB” for ‘adblock’ suffix on their ssid names), don’t. Each ssid is their own vlan and each has their own dhcp listening that doles out the pihole instance address on the Adblock-enabled nets.

It’s easy enough to just connect to a different ssid if I see anything breaking, but it’s rare enough that I keep it connected to the pihole/adblock network at all times. Works super well.

Re: Blocky – a DNS proxy and ad-blocker for the local network

#56
post #50

My problem with network-level adblockers, also PiHole is that they break a lot of services (yeah it's mostly sloppy or malicious intent from service provider but still). On a browser you can quickly disable uBlock for that site, it is much more tedious for these services - also because it's not even clear that the filtering is causing the problem, also because it maybe someone else on the network experiencing the pro…

It's not that tedious. In adguard home you have a switch on/off in the web UI. You can also expose that switch to homeassistant. And there are some other good ideas in this thread as well for android and ios.

After disabling it on the UI, your device may still cache the DNS records for a few minutes. There's no immediate feedback on whether disabling adblocking changed anything. It is extremely tedious especially for non-technical users, and adds "tech-support" burden to their technical friend/family who set it up in the first place.

Re: Blocky – a DNS proxy and ad-blocker for the local network

#57

My problem with network-level adblockers, also PiHole is that they break a lot of services (yeah it's mostly sloppy or malicious intent from service provider but still). On a browser you can quickly disable uBlock for that site, it is much more tedious for these services - also because it's not even clear that the filtering is causing the problem, also because it maybe someone else on the network experiencing the pro…

I created a bit.ly link that points to http://yourpiholehost/admin/api.php?disable=300&auth=api_key Bookmark it for myself and other people in the house and then turn it off for five mins whenever there is an issue.

Would be fun to hook this up to one of those IoT Amazon buttons.

Re: Blocky – a DNS proxy and ad-blocker for the local network

#58

Earlier quoted context omitted.

I created a bit.ly link that points to http://yourpiholehost/admin/api.php?disable=300&auth=api_key Bookmark it for myself and other people in the house and then turn it off for five mins whenever there is an issue.

Would be fun to hook this up to one of those IoT Amazon buttons.

Home Assistant can definitely do this. I just now successfully got my HA connected to an Aqara Zigbee button (which, hilariously, only briefly functioned when I was using it with Aqara's garbage hub).

Re: Blocky – a DNS proxy and ad-blocker for the local network

#59

Earlier quoted context omitted.

What annoyed me the most is actually clicking on ads from Google Search. Sometime I searched a product and I couldn't clicked on the first result because they are advertisements.

Honestly, I love this aspect of my Pihole. Stops Google stealing those pennies from the businesses who were already gonna be the #1 result anyways.

The "sponsored ads on your own name" extortion racket really is the worst.

Re: Blocky – a DNS proxy and ad-blocker for the local network

#60
post #21

My problem with network-level adblockers, also PiHole is that they break a lot of services (yeah it's mostly sloppy or malicious intent from service provider but still). On a browser you can quickly disable uBlock for that site, it is much more tedious for these services - also because it's not even clear that the filtering is causing the problem, also because it maybe someone else on the network experiencing the pro…

I have a silly "trick" for this. In Firefox you can add a SOCKS5 proxy and click "Proxy DNS with SOCKS5 proxy". This bypasses the system DNS. So for example, if you make a container with this, then you can just quickly open the URL that's blocked in the other container and it will bypass the network-level DNS adblock. There are other ways to do it without a container, I'm sure, maybe with an add-on/toggle or somethin…

How are you using a different proxy per container tab? I've tried FoxyProxy but it leaked DNS requests through the local network resolver even with SOCKS5 proxies.
Post reply on HN