151–160 of 211 posts
Earlier quoted context omitted.
Some people like to watch YouTube on their TV
I watch YouTube on my TV. Using Firefox, with uBlock Origin. We have a laptop plugged into the TV, with a bluetooth keyboard. It is a vastly superior experience to any smart TV I have ever seen.
Earlier quoted context omitted.
With pi-hole, you can also block telemetry from smart devices (TVs, dish washers and stuff), and if you run it on a VPN that your phone is connected to, you can also block ads and tracking in phone apps. As mentioned in the article, pi-hole complements a browser ad block, doesn't replace it.
I just don't connect those devices to any internet.
Earlier quoted context omitted.
I watch YouTube on my TV. Using Firefox, with uBlock Origin. We have a laptop plugged into the TV, with a bluetooth keyboard. It is a vastly superior experience to any smart TV I have ever seen.
And also more than most people want to have setup in the living room. My wife would rather have ads on YouTube occasionally than an ugly computer plugged in all the time. It’s also more difficult to deal with than a remote you can work one handed.
Disclaimer: The below is not a complaint about the pi-hole itself, but the ways in which companies integrate ads into their online presence. I've found my complaint about having a pi-hole is there are a number of services I use that expect/depend on ads existing in order to function. Things like, some shows on paramount+ (as an example) will fail to play (hang indefinitely) if an ad hasn't run before one of their sho…
To fix that you just need to look through the logs through the native pi-hole UI and whitelist those domains which cause friction with your browsing habits. The google sponsored search issue was one I also fixed quite quickly. As for the others those services depend on, again you just need to find them and whitelist them which isn't too tricky to do. Unfortunately pi-hole won't stop everything.
Earlier quoted context omitted.
Your comment makes no sense. The DoH providers can still log requests and sell them. DoH protects against intermediaries spying on your requests and potentially forging responses. Exactly the same as HTTPS. Sending anything in clear text over the internet in 2025 is criminally negligent.
HTTPS is not necessary to encrypt DNS traffic. DNS-over-TLS exists, but it has much less traction compared to DNS-over-HTTPS. I am guessing the reason is that HTTPS traffic all goes through port 443, so "censorship" of DNS becomes tricky, since DNS traffic becomes a bit harder to distinguish from ordinary web traffic. Encapsulating DNS packets in HTTP payloads still feels a bit strange to me. Reminds me a bit of DOCS…
I run PiHole for years in my home network, I cannot live without it. With the years, I have made small changes to increase my control over it. I have a recursive DNS setup, PiHole filters everything, and what is left is processed locally via Unbound which in turn, contacts the 13 root nameservers for DNS resolution. I don't use any third party DNS. Add PiHole/Unbound caching capabilities, surfing on the internet is b…
I want to know how to become a Pollack painting.
I run PiHole for years in my home network, I cannot live without it. With the years, I have made small changes to increase my control over it. I have a recursive DNS setup, PiHole filters everything, and what is left is processed locally via Unbound which in turn, contacts the 13 root nameservers for DNS resolution. I don't use any third party DNS. Add PiHole/Unbound caching capabilities, surfing on the internet is b…
How? I can see you only allowing some ports through the firewall, but presumably TCP 443 is one of those. According to Cloudflare [0] DoH uses that. What if Samsung uses that, or figures DoT on port 443 works better? Do you only allow specific destinations for these devices?
I actually use a similar setup, only I removed pihole and just use some lists in my opnsense's unbound (didn't notice much difference).
My "smart" TV is pretty awful, so it's just unplugged (which makes it dumb, so now I love it). I've tried putting it on a dedicated VLAN with no internet access so I could try using the built-in Chromecast functionality – didn't have much luck. I've set up the mDNS repeater and allowed ports through, but that doesn't seem enough.
[0] https://developers.cloudflare.com/1.1.1.1/encryption/dns-ove...
Earlier quoted context omitted.
If you're really serious about DNS interception, you'd setup something where a) you stop accepting A lookups, because it's 2025 and IPv4 only is dead (let's pretend anyway) b) for each AAAA lookup, return a new IPv6 address that you'll NAT to the real address (you can use this for NAT64 if you want to let clients connect to IPv4 hosts). Then only let clients connect to these IPv6 addresses you setup. If someone smugg…
> for each AAAA lookup, return a new IPv6 address that you'll NAT to the real address (you can use this for NAT64 if you want to let clients connect to IPv4 hosts) We employ exactly this technique for our Android firewall app. It can do IPv4 (by mapping hash(domain) name onto RFC6598 reserved subnet [0]) as number of unique AAAA/A requests on a client seldom exceeds 35k/mo! Another (simpler) control we offer users is…
This sounds good, and I've wondered how I could implement such a thing.
However, with the clearly hostile approach all IoT appliances are taking, I wonder if they'll actually fall back to a "degraded" (for them) config with the network-provided DNS, or whether they'll just fail and complain the network is broken or something.