3 ms·

I think it's just a tradeoff. I run Pihole and it does occasionally block things that I need, but it's rare. When it happens I log into the dashboard, look at w

I think it's just a tradeoff. I run Pihole and it does occasionally block things that I need, but it's rare. When it happens I log into the dashboard, look at what was recently blocked, and permanently unblock it if needed. On the plus side, fewer to no ads on all devices including mobiles.

ProllyInfamous 3y ago
For a sole user, yours is definitely a great way to economically utilize a single PiHole at home. A suggestion for tho$e with multiple users: set up multiple PiHoles on your same network, then have "blocking levels" which each user can set up, e.g: 192.168.0.2 x.x.x.3 x.x.x.4 x.x.x.5 x.x.x.n My DHCP auto-issues the "lowest level of blocking" PiHole to any client not specifying their own DNS (only 7 rules, mostly blocking pagead2 and doubleclick). Phones all point to a phone-specific local PiHole IP (which allows them to do phone-ier things). From there, users can block more ads simply by increasing the DNS IP by x.x.x.+1 [until shit stops working for them, then bump down 1]. For malingering DNS resolution issues, I'll sit down with the user/client and help them "massage the blocks" between x.x.x.n , but this is rare after the initial week or so of setup. This also allows individual clients to entirely bypass your PiHoles, simply by them manually setting their DNS to x.x.x.1 [i.e. their router's IP]. ---- YES I know that you can have a single PiHole resolve differently based on client IP, but my above solution allows for a much-simpler "levels of DNS protection" that most non-technical users can understand/modify, themselves. It is not inexpensive =D
- accrual 3y ago
  That's a slick solution, thanks for sharing! Pihole resource needs are pretty low so I could see easily running several in parallel on a Docker host.
  - ProllyInfamous 3y ago
    That'd probably be much less expensive than the four RaspberryPi3b+ fleet I assembled for an otherwise virtualizable solution.

ProllyInfamous 3y ago

For a sole user, yours is definitely a great way to economically utilize a single PiHole at home. A suggestion for tho$e with multiple users: set up multiple PiHoles on your same network, then have "blocking levels" which each user can set up, e.g: 192.168.0.2 x.x.x.3 x.x.x.4 x.x.x.5 x.x.x.n My DHCP auto-issues the "lowest level of blocking" PiHole to any client not specifying their own DNS (only 7 rules, mostly blocking pagead2 and doubleclick). Phones all point to a phone-specific local PiHole IP (which allows them to do phone-ier things). From there, users can block more ads simply by increasing the DNS IP by x.x.x.+1 [until shit stops working for them, then bump down 1]. For malingering DNS resolution issues, I'll sit down with the user/client and help them "massage the blocks" between x.x.x.n , but this is rare after the initial week or so of setup. This also allows individual clients to entirely bypass your PiHoles, simply by them manually setting their DNS to x.x.x.1 [i.e. their router's IP]. ---- YES I know that you can have a single PiHole resolve differently based on client IP, but my above solution allows for a much-simpler "levels of DNS protection" that most non-technical users can understand/modify, themselves. It is not inexpensive =D

accrual 3y ago
That's a slick solution, thanks for sharing! Pihole resource needs are pretty low so I could see easily running several in parallel on a Docker host.
- ProllyInfamous 3y ago
  That'd probably be much less expensive than the four RaspberryPi3b+ fleet I assembled for an otherwise virtualizable solution.