Apologies if this should be posted somewhere else.

I have had this TV for about 7 years and have never had this pop up before. About a month ago, I bought a router that uses OpenWRT. With that, I setup up Adguard and specifically one of the lists that is supposed to block devices from phoning home.

Am I nuts thinking that this pop up is due to the TV not being able to offload what has been recorded? How would I check that?

you are viewing a single comment's thread
view the rest of the comments
[–] 17 points 1 day ago* (last edited 1 day ago) (4 children)

About a month ago, I bought a router that uses OpenWRT. With that, I setup up Adguard and specifically one of the lists that is supposed to block devices from phoning home.

How would I check that?

AdGuard used DNS to enforce its blocklists, you can setup your own DNS sinkhole server on your network relatively easily, point your devices to it, and view what servers your devices on your network are connecting to.

  • source
  • hideshow 4 child comments
  • [–] 21 points 1 day ago

    Yup. And it’s worth noting that my two smart TVs are the noisiest devices on my network, by far. Like it’s not even close. In a heavy day of doing nothing but doomscrolling and casual browsing, my phone may get 1700-2000 blocked requests. My smart TVs typically hit 5500-6000 blocked requests each.

    Which, when you do the math, comes out to a failed request every ~15 seconds. Which means they’re probably attempting to reach the server, getting blocked, timing out after ~15 seconds, and then retrying. If they were logging each failed attempt as an error and never purging their old logs, I can see how it would slowly but surely fill their storage space.

  • source
  • parent
  • [–] 5 points 15 hours ago (2 children)

    This may work today, but it take very little effort for the TV manufacturers to default to DNS over HTTPS to bypass these DNS based filtering. I'd recommend keeping TV's off the network completely. I wish the DRM mafia weren't keeping open competitors away. There's no reason we should have privacy respecting TV boxes, except that the power is in the streaming platform companies hands, and they don't want to enable anything even slightly open.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 15 hours ago

    Owning (owning) your router/firewall makes this harder for them to bypass. Block all DNS outbound, allow only from Pihole (or other private DNS server), redirect all DNS to Pihole. The machines you don't/can't own will think they're reaching out to external DNS but the replies come from Pihole. I haven't dug too far into whether this works if they force DNS over HTTPS. Is that not 853/tls?! My convoluted and possibly placebo setup.

    I suppose there are plenty of ways around this. My config is port based, so if they change ports or run a tunnel through something my Pihole doesn't block... Sigh. Yeah, just don't connect these crap boxes up to the network in the first place.

  • source
  • parent
  • [–] 2 points 6 hours ago

    Block all other DNS by port and IP both from everything by pi-hole. Even if they hardcode 1.1.1.1 or Quad9 or Google or whatever, it would be exceedingly difficult to reach an IP address that is forbidden on the network at the router level. HTTPS will just fail (and likely fall back to network DNS settings as it should).

  • source
  • parent