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

Selfhosted

40211 readers
1416 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
[–] CameronDev@programming.dev 12 points 2 months ago (1 children)

Openwrt can run Adguard, and as long as your gateway can run docker, you can probably get pihole working.

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

Thanks, so what I should look for is a gateway running OpenWRT, which can run docker?

[–] CameronDev@programming.dev 9 points 2 months ago (2 children)

I think its better to keep your gateway basic, and run extra services on a separate raspi or similar. Let your router/gateway focus on routing packets.

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

I'm not overly against keeping them separate. It's just I have a lot of stuff piling up and consolidating would have been nice 😆

[–] DarkDarkHouse@lemmy.sdf.org 3 points 2 months ago (1 children)

Agreed. I would also reconsider ditching the ISP router. You can still connect your gateway to it, and having the ISP device on premises can mean they might not blame your equipment for a line issue.

[–] Dave@lemmy.nz 5 points 2 months ago* (last edited 2 months ago)

It's a little bit more complicated than I made out. For one, the network is super unstable and restarting the ISP router seems to fix it. I want to replace the router to test the theory that it's the problem.

Secondly, this is a bring your own router to the ISP situation, but the router came from another ISP, but they are all the same ISP in the end because one company owns a whole bunch of ISPs and sends the same router to all the customers of all the child companies. Long story short, it's the router they would have issued to me, but they didn't, because a different subsidiary sent it to me before I changed ISPs to take advantage of a special because I live in a country where the lines are open and anyone can start an ISP using the existing lines but if you get big enough to be competition then the big company will buy you out and pretend it's still a separate company. But if it doesn't work well then it's up to me to solve unless I am willing to pay the ~$10USD for them to send me the ISP router that is supported by them but it will be the same cheap router as I already have. Ok that's not a very short story but that's why it was easier to just call it an ISP router 😆

[–] tired_n_bored@lemmy.world 2 points 2 months ago

Yes you can install Docker on OpenWrt but do your own research as if I remember correctly you have to thinker with it