51–60 of 246 posts
Is the Pi-Hole even reasonably effective these days? > Nearly 70% of smart TVs and 46% of game consoles were found to contain hardcoded DNS settings - allowing them to simply ignore your local network’s DNS server entirely. https://labzilla.io/blog/force-dns-pihole
Sounds like we also need a list of IPs to null route
Is the Pi-Hole even reasonably effective these days? > Nearly 70% of smart TVs and 46% of game consoles were found to contain hardcoded DNS settings - allowing them to simply ignore your local network’s DNS server entirely. https://labzilla.io/blog/force-dns-pihole
Is the Pi-Hole even reasonably effective these days? > Nearly 70% of smart TVs and 46% of game consoles were found to contain hardcoded DNS settings - allowing them to simply ignore your local network’s DNS server entirely. https://labzilla.io/blog/force-dns-pihole
When I bought my first smart TV (mainly due to lack of dumb screens), immediately grabbed a Pi-Hole and started blocking everything I could find.
Also, one of the only occurrences where I’m skeptical even updating the tv software.
Is the Pi-Hole even reasonably effective these days? > Nearly 70% of smart TVs and 46% of game consoles were found to contain hardcoded DNS settings - allowing them to simply ignore your local network’s DNS server entirely. https://labzilla.io/blog/force-dns-pihole
You can create port forward firewall rules to redirect any outbound DNS port 53 traffic. This will not work for DNS over HTTPS, which is going to be increasingly common for IoT I'd imagine. edit: method for this on pfSense: https://docs.netgate.com/pfsense/en/latest/recipes/dns-redir...
https://codeberg.org/unixsheikh/dohblockbuster https://openbsdrouterguide.net/#blocking-doh
"#secure.netflix.com" "#api-global.netflix.com" "#appboot.netflix.com" These are commented out, but did someone really think the app would still work after blocking these? I get blocking ads, but I don't understand the mindset of someone who wants "smart" features but still wants to block everything.
1. It's actually very difficult to buy a non-smart TV. They usually cost more. 2. The comments also serve as a "no really, don't block these" reminder to enthusiastic contributors.
Praise be the folks that curate these lists. Even without a pi-hole you can plug these into any firewall for your brand(s). More annoying is the 15 second "home menu" that pops up on my OLED every time it is turned on. I almost always forget to manually dismiss it before I set the remote down and there's no option I can find to disable it. I would pay a premium for a TV with no internet connection.
I can't be the only one that thinks this (DNS blocking) is an exceptionally poor solution to this problem. It's essentially whack-a-mole. You either A) don't allow your smart TV ip address to egress traffic to the internet or B) don't connect it at all. There are some domains in that list like the *.cloudfront.net that might change over time.
Earlier quoted context omitted.
Sounds like we also need a list of IPs to null route
The workaround is already in use for ad hosting - serve all the content from one domain (or an IP) with services natted behind that, so if you block it, nothing works.
Praise be the folks that curate these lists. Even without a pi-hole you can plug these into any firewall for your brand(s). More annoying is the 15 second "home menu" that pops up on my OLED every time it is turned on. I almost always forget to manually dismiss it before I set the remote down and there's no option I can find to disable it. I would pay a premium for a TV with no internet connection.