Last month I took my Roku offline but let it connect to LAN so the Jellyfin app would work (for now until it gets too out of date probably). I knew Fox would fuck things up somehow and I was right sooner than expected.
As an aside, it’s still connected to my pihole and for about a week it tried to send logging data to 2 different websites every 3 seconds for around a week. It was funny seeing my blocked percentage at 91.5%, even funnier that it’s programmed to give up.
Last time I put a Roku behind DNS filtering it just started spamming it’s logging server because it couldn’t make contact. I ended up just letting it through instead of going through the hassle of spoofing a response to make it shut up.
Pi-hole at the time had a default limit of 1000 requests per minute before it would time-out requests from all clients for 60 seconds and I didn’t know how to change that. I’m using AGH now though.
Last month I took my Roku offline but let it connect to LAN so the Jellyfin app would work (for now until it gets too out of date probably). I knew Fox would fuck things up somehow and I was right sooner than expected.
As an aside, it’s still connected to my pihole and for about a week it tried to send logging data to 2 different websites every 3 seconds for around a week. It was funny seeing my blocked percentage at 91.5%, even funnier that it’s programmed to give up.
It probably gives up only not to accidentally DDOS their own telemetry servers
Or maybe it’s just a reaally slow exponential backoff
Linear backoff. Add one millisecond per retry.
Last time I put a Roku behind DNS filtering it just started spamming it’s logging server because it couldn’t make contact. I ended up just letting it through instead of going through the hassle of spoofing a response to make it shut up.
Why do that? It’s not hurting anything.
Pi-hole at the time had a default limit of 1000 requests per minute before it would time-out requests from all clients for 60 seconds and I didn’t know how to change that. I’m using AGH now though.