this post was submitted on 30 Jun 2023
15 points (85.7% liked)

Selfhosted

39942 readers
580 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

A few of my friends experienced the glory of PiHole in my home network and asked, if I could install such a thing in their networks as well.

Which I obviously could, but none of them are interested in updating/maintaining such a device. So I would like to collect some suggestions on how to deploy such a box with (ideally) zero interaction from my side until the end of times.

My hardware platform of choice would be a cheap thin client (Futro s920 or something like that) running Ubuntu with unattended updates enabled.

Pihole itself seem to offer an auto-updater, but I'm not sure how stable that runs in the long run - maybe Docker would be better suited here?

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

DO NOT run a public DNS resolver. It'll get used as part of a DNS amplification attack, and your system will be used to DDOS somebody else.

The only viable solutions here are to either have OPs friends VPN all traffic through OPs network (there might be a way to use split tunneling to reduce total traffic used, though I'm just spitballing here), to deploy hardware locally on their network, or to use a public solution. Everything else is going to be a security risk.

[–] francis 2 points 1 year ago (2 children)

Thanks for the explicit mention, I should have been less vague with my "planning the security aspects" comment. I was thinking firewall rules would mitigate that, but could moot if the friends are on a dynamic lease.

VPN is a bit of a non starter since that would require installing and running a VPN client 24/7 on all devices, else you're dropping in a site to site VPN device on the network... At that point you might as well cut out the extra complication and just run PiHole on that point.

I actually learned about public AdGuard servers in this thread! I'd definitely lean that way if I were OP (because I personally do not want to field "the internet is not working" calls in the middle of the night).

[–] DesertCreosote 1 points 1 year ago

No worries, I just wanted to make very sure that the risks for #1 were properly understood.

VPN might be able to work with split tunneling, but I haven't tried it myself. It'd probably be more complicated than it's worth!

I'd also lean towards the public AdGuard servers in this case, for the same reason! I'm happy to field certain calls from friends and family, but I don't want to get the "my internet isn't working!" calls at 2am-- I get enough of those from work! 😁