Question for the #selfhosting hivemind -- I would really like to manage DHCP on my home network (for netbooting, controlling DNS etc) but unlike with previous ISPs I've had this is NOT POSSIBLE via the modem/router I have from Virgin (UK); the settings are very limited. The only option seems to be changing the router to operate in "modem" mode and then essentially handling firewall / routing / DHCP etc externally. I'm trying to figure out the best way to do this given some constraints. 1/?

* I don't really want to use a ton of power / have a lot of bulky devices. It seems annoying to have to have a discrete router, wireless AP and switch.

* I don't really want to have to manage tons of advanced features, or need 2.5gpbs + speeds, hardware VPN, traffic shaping, VLANs etc.

* I wonder if the answer might be to virtualize a router OS / Appliance on my proxmox box but that seems kinda dangerous? And I guess I'd still need a switch + Wireless AP?

2/?

Has anyone navigated these waters before?

It's annoying that the modem/router is SO close to what I need but in order to, eg, make my devices pick up a local pi-hole instance automatically I'd need to invest in a few hundred pounds of hardware and increase my power bills 😕

Any advice? 3/3

@heavyimage

I can tell you what I did, take what you want or not, but I ended up with a much superior setup.

I set my ISP router in bridge mode so, like you said, it just functions as the modem.

I got a mini PC with 2 network interfaces. On that, I run Proxmox, OpenWRT in a VM, and Docker in an LXC where I run pihole, unbound, Nginx Proxy Manager, a few other services. So this is my router, DNS, DHCP, etc.

In another place in my home I installed an Omada EAP. Wifi coverage is much better.

@skylark13 Thanks for taking the time to reply. I think one would definitely get much better performance / control out of your setup and I think I might eventually do something like this if I buy a place. But in my little flat, this is overkill and I'd rather do something with fewer bits of hardware.

@heavyimage

For me, the benefits are better control over my services, pihole blocking stuff, and the mini PC uses very little power. And for WiFi, I could not put my ISP router in an optimal location, so now my Wifi is much better since it's a separate box.

Downsides are more maintenance and slight downtime when I update pihole or OpenWRT. I could mitigate that with a second Proxmox node I think. Not sure it's worth the hassle.

I went with OpenWRT after trying OpnSense and being overwhelmed.

@skylark13 Agreed on all points. OPNSense looks very overwelming, agreed.

@heavyimage

Yeah. OpenWRT by nature is much closer to what a home user is used to with commercial routers. I have it running Wireguard and a DDNS updater as well, so that's cool. But I wanted pihole and unbound for DNS filtering because I prefer the interface and reporting, so I disabled OpenWRT's DNS functionality.

I understand your reticence to have as many moving parts. I just like to tinker, and so far it's gone well, my other users (my family) also commented on the improved WiFi 😁

@skylark13 that must feel so good! One day!

@heavyimage @skylark13

You could also get one single juicy router and run openwrt+adguardhome+maybe some container if needed. GL.inet are relatively cheaper.

@infodon @heavyimage For me, splitting the router and WiFi access point made sense because of how my house is laid out. But yeah, that's not going to be the case for everyone and there are some pretty good DIY router options out there.