Yeah I run diversion and skynet on my Asus ac1900p running asuswrt-merlin. Been like that for a couple years now. It's great. Stuff like this should just run in the router if ya can.
Setting up a Pi Hole made my home network faster
221–230 of 249 posts
Re: Setting up a Pi Hole made my home network faster
#222I ran Pi Hole (and AdguardHome) for years, but eventually just upgraded to NextDNS instead. It works almost the same (minus the DHCP stuff), but instead of just working on your LAN, it works on every device all the time.
It works with any device you can install it on but not for example on cheap tv sticks, smart devices and other IoT stuff which still may be infested with adware phoning home every second. I’ve been using pi-hole at home and NextDNS/VPN outside as they’re more complementary than overlapping.
Re: Setting up a Pi Hole made my home network faster
#223What if I told you, todays ads model is huge spam network?
Re: Setting up a Pi Hole made my home network faster
#224I know some folks are anti Ubiquiti Unifi on here, but you can run pihole (along with a bunch of other stuff) right on a UDM/UDM-Pro. IMO it makes the most sense to run this on the router, and you can run it in a docker container. If you're looking for a fun hour or two project, check out: https://github.com/boostchicken-dev/udm-utilities/tree/maste...
I'm afraid to ask, but why are people anti ubiquity? I freaking love my udm-pro and am waiting for their cams to come back in stock so I can ditch my nests.
>waiting for their cams to come back in stock
https://discord.gg/ubiquitiinstock
I've scored a few Protect items via alerts here, but be prepared to be patient.
Re: Setting up a Pi Hole made my home network faster
#225I was excited to try this once as a weekend project. Got it all set up and working so my desktop sent DNS through the Pi. Then went to set the router to use it instead, and it was a no-go. Comcast routers don't allow you to change the DNS settings. Of course I could've bought a new router and set that up to work between the Pi and the Comcast one, but that was more than I wanted to put into it. Now I have a different…
I'd highly recommend going the network-wide route with router DNS settings. You might have some luck finding a pi here: https://rpilocator.com/ .
I set up a Pi-hole for my home network easy enough on a Fritzbox router, with the Pi-hole as DNS. I've since gone a step further, and now use the Pi-hole for DHCP too. The router now just routes.
Re: Setting up a Pi Hole made my home network faster
#226I ran Pi Hole (and AdguardHome) for years, but eventually just upgraded to NextDNS instead. It works almost the same (minus the DHCP stuff), but instead of just working on your LAN, it works on every device all the time.
It works with any device you can install it on but not for example on cheap tv sticks, smart devices and other IoT stuff which still may be infested with adware phoning home every second. I’ve been using pi-hole at home and NextDNS/VPN outside as they’re more complementary than overlapping.
I have my router hand out NextDNS resolvers per subnet, so that each VLAN uses a different NextDNS configuration. I use the NextDNS CLI[1], so i can take advantage of local DNS caching while at the same time using NextDNS.
Re: Setting up a Pi Hole made my home network faster
#227Won't be long now until IoT and other crap-ware devices catch on to this trend and start hard-coding DNS servers in code, or worse, using DNS encryption to avoid this sort of routine blocking by end-users. I wonder how people are thinking about solving this problem.
Have your gateway/firewall block all traffic from the LAN IP of the device from exiting the LAN. If it's running on Win/Mac/Linux/Android/iOS, block the app from talking to the gateway, or even the entire LAN.
That's what I do with my printer. I love the company (Brother) and they make IMO the best printers and MFPs but I am quite paranoid already and I just block any WAN traffic. The printer is (and should be) really only used from the LAN anyway.
Re: Setting up a Pi Hole made my home network faster
#228Earlier quoted context omitted.
Yeah, Krebs published this updated take: "On Wednesday, a former Ubiquiti developer was arrested and charged with stealing data and trying to extort his employer while pretending to be a whistleblower. "Federal prosecutors say Nickolas Sharp, a senior developer at Ubiquiti, actually caused the “breach” that forced Ubiquiti to disclose a cybersecurity incident in January."
No matter how good your security is, a rogue employee with high-level access will always be a threat. Since they now have experience with this situation, I trust that Ubiquiti has dedicated more resources to preventing both employee sabotage and external breaches. This also shows that not every breach is what it seems, and investigating fully before publicly disclosing can sometimes help prevent disinformation. The “…
Yeah, reminiscent of the (apocryphal?) story of the stuntplane mechanic whose negligence almost cost the pilot his life; assuming he'd be fired, the mechanic was shocked when the pilot said he was now the only mechanic allowed to touch his plane, bc he knew, with certainty, there'd never be another such mishap.
Re: Setting up a Pi Hole made my home network faster
#229This article didn't actually test their network's latency / throughput before and after this. I don't think ads / metrics passively use a ton of bandwidth no I doubt the author's claims.
Have you read about the subject or measured it on your own?
Use the networking section of the developer tools in your browser. On a mainstream site I was just visiting, the page itself was about 50 kilobytes and it downloaded just under 3 megabytes of ad and tracking JS.
Re: Setting up a Pi Hole made my home network faster
#230Earlier quoted context omitted.
Actually no. By blocking 53 at your router to anything except your pihole, even a hard-coded IP like 8888 is blocked.
You'd have to do packet inspection. Otherwise a hostile hardware manufacturer could just run their DNS on a non-standard port.
Perhaps, but blocking 53 is better than not, IMHO. I've seen devices fall back once blocked to a hard-coded dns, so it works today. DoH is another that devices will eventually employ, so that's another whack-a-mole situation.