this post was submitted on 07 Sep 2024
26 points (96.4% liked)

Selfhosted

40184 readers
579 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
 

I'm looking at getting a gateway device to replace the ISP router that sits between the internet connection and the mesh WiFi.

I am running pi-hole on a (very old) raspberry pi, but I know some gateways get quite fancy so I'm wondering if it's possible to have pi-hole on the gateway itself, to run as DNS and DHCP servers?

Other things I'm looking for in a gateway are VPN as a client (preferably Wireguard) and PoE ports for cameras.

If it's possible to host something like pi-hole directly on the gateway then hardware recommendations are appreciated!

you are viewing a single comment's thread
view the rest of the comments
[–] hungover_pilot@lemmy.world 6 points 2 months ago* (last edited 2 months ago) (3 children)

Most of the more advanced gateways have some sort of DNS filtering built in. Opnsense has an adguard plugin, pfsense has pfblocker-ng, openwrt has a few different options, Unifi and mikrotik both have solutions too I think. Usually you can just load the same block list that pihole uses into the filtering software and you are good to go.

If you want the most flexibility and want to use the same hardware for both gateway/DNS and want to try out different DNS/router solutions a hypervisor would give you the most options. But it would also be the most complicated.

[–] Dave@lemmy.nz 1 points 2 months ago (2 children)

One of the things I use pi-hole for is to set customer DNS entries so anyone on the network will be redirected directly to the self hosted services when the type in the appropriate domain name. So it's not just about the filtering (which I also want), but also the (network wide) custom DNS entries.

I'm also happy with simple. I'm not overly against keeping the pi-hole and gateway separate but was just wanting to know if combining them would be an option (which is sounds like it is, but not super easy).

[–] hungover_pilot@lemmy.world 2 points 2 months ago* (last edited 2 months ago) (1 children)

Both opnsense and pfsense allow custom DNS entries so you still have that as an option. Probably the other options do too but you'll just have to verify.

But if you want to keep it simple I would just keep the pihole as a separate device. A lot of the built in options aernt quite as easy to setup and don't have the best UI compared to pihole IMO.

[–] Dave@lemmy.nz 1 points 2 months ago

Thanks, yeah I will consider the options. Would be nice to have it in one as the raspberry pi is aging (it's an original model B) and the gateway should be plenty powerful enough to run it, plus it would rule out the pi-hole to router connection as a possible reason for the unstable network.