FixItInPost
New Around Here
Hi, I just wanted to share some info about my recent battling with Roku, in case it's helpful to anyone else. I mention (below) an SNBforums thread that helped me resolve this, and I want to thank two posters there (Crimliar and drinkingbird) who gave enough info to help me solve my problem. I hope sharing my experience can pay it forward by helping someone else.
I'm running Merlin with Skynet and Diversion. Months ago, my Roku suddenly started having on-screen ads again. I figured out that I had some local devices (including the Roku) repeatedly hitting 8.8.8.8 and 8.8.4.4 and ignoring my ad-blocker. Seems that some companies started hard-coding DNS servers in firmware, using DOT or DOH to bypass DNS Director. So I used Skynet to just block those IPs. Any device hard-coded to those DNS servers would fail to connect, fall back to router-assigned DNS, and ad-blocking worked again. And all was good.
Until Roku got wise.
Last night, Roku pushed a new update that bricked my Roku. It was in Recovery Mode this morning and wouldn't finish recovery. I had to hard reset it, then redoing setup I got "cannot connect to the Internet." Like before, nothing I did with DNS Director affected the Roku. While flailing for answers, I disabled Skynet, and suddenly the Roku worked ... with ads. I eventually got the Roku to work with Skynet enabled, by unbanning 8.8.8.8 and 8.8.4.4. Those blocks were the problem. If the Roku couldn't reach those IPs, it became a pumpkin, until they were unblocked. And while they were unblocked ... I got ads.
I theorized that if the Roku thought it could connect to those IPs, it would work again. So, I went looking for the easiest way to just reroute those IPs to a local IP. Unsurprisingly, Google found me an on-point SNBForums thread, where someone had a similar problem and the same idea:
I tried the above, replacing the 192.168.*.* IP with my own router's LAN IP, and eureka! The Roku works, and ad-blocking works! And nothing on my local network should ever need to access those DNS servers instead of mine, so, I think I'm good again.
For now, until Roku figures out how to bypass this.
I'm running Merlin with Skynet and Diversion. Months ago, my Roku suddenly started having on-screen ads again. I figured out that I had some local devices (including the Roku) repeatedly hitting 8.8.8.8 and 8.8.4.4 and ignoring my ad-blocker. Seems that some companies started hard-coding DNS servers in firmware, using DOT or DOH to bypass DNS Director. So I used Skynet to just block those IPs. Any device hard-coded to those DNS servers would fail to connect, fall back to router-assigned DNS, and ad-blocking worked again. And all was good.
Until Roku got wise.
Last night, Roku pushed a new update that bricked my Roku. It was in Recovery Mode this morning and wouldn't finish recovery. I had to hard reset it, then redoing setup I got "cannot connect to the Internet." Like before, nothing I did with DNS Director affected the Roku. While flailing for answers, I disabled Skynet, and suddenly the Roku worked ... with ads. I eventually got the Roku to work with Skynet enabled, by unbanning 8.8.8.8 and 8.8.4.4. Those blocks were the problem. If the Roku couldn't reach those IPs, it became a pumpkin, until they were unblocked. And while they were unblocked ... I got ads.
I theorized that if the Roku thought it could connect to those IPs, it would work again. So, I went looking for the easiest way to just reroute those IPs to a local IP. Unsurprisingly, Google found me an on-point SNBForums thread, where someone had a similar problem and the same idea:
The only way to stop my main TV from performing certain shenanigans is to use the following:
View attachment 47642
So this takes any requests for Google's DNS and redirects them to my Raspberry Pi at 192.168.127.5
Not fully what the OP is looking for...
I tried the above, replacing the 192.168.*.* IP with my own router's LAN IP, and eureka! The Roku works, and ad-blocking works! And nothing on my local network should ever need to access those DNS servers instead of mine, so, I think I'm good again.
For now, until Roku figures out how to bypass this.