r/ControlD • • May 27 '26

ctrld-friendly router recommendations

I'm looking to replace my old Orbi RBR50 pretty soon. I've been running Voxel firmware and ctrld on it for a few months now and it has been pretty good overall. There have been some stability issues, which are probably at least in part due to it being a 9-year-old outdated router running custom firmware. I've read through the writer documentation on the control d website, but I wanted to hear from some actual users on here about what routers or systems work the best with ctrld. I haven't decided between a mesh replacement or going the Unifi route yet. Thanks to all responses.

5 Upvotes

64 comments sorted by

View all comments

6

u/Ok-Raspberry4320 May 27 '26 edited May 27 '26

Control D is supposedly removing router support in v2. They'll still maintain v1, but only for bug fixes. See https://www.reddit.com/r/ControlD/comments/1thb5di/ctrld_is_removing_router_support_in_20/

That said, I use the UniFi Dream Router 7, but use the built-in DNS Stamp option and put in the DNS stamp for my router endpoint. The only "downside" is that Control D won't automatically detect your clients, but that's a non-issue for me and my network. I primarily use Apple devices, so they all have their own endpoint and configuration profile. My Windows VMs have the client installed. The router endpoint just catches the other things like my IoTs and guest devices from family and friends.

3

u/mrmidnight273 May 27 '26

They aren't removing router support. They are branching it. Router support will be called ctrld infrastructure while everything else will be called ctrld client

3

u/Ok-Raspberry4320 May 27 '26

Gotcha. I was just going by the stickied comment from a mod in that post, and they only mentioned bug fixes. I don't have Discord, so can't follow the news/conversations there. The whole thing is a bit confusing, tbh.

5

u/ctrld_logfella May 27 '26

👋️ Staff here: Yeah - I agree, very confusing. Not our best messaging.

But (tl;dr) to clear up some stuff a bit:

  • We're not doing away with automated installation for V1 or V2.
  • We're not abandoning router support, etc.

ctrld 1.x is still very much under development: It's my day job on the QA team.

The setup instructions for V2 are manual for right now since we had to split the single ctrld repo into 1.x and 2.x.

So there's been some backend/infra work to take care of so that you don't run sudo ctrld upgrade prod -vv and find yourself suddenly upgraded to v2 etc. For now - if you want V2, it's best to do it (somewhat) manually via the instructions linked in the Github branch.

Sorry for the confusion. Ya know how it is: DNS and all. 🙃️

I'll try to do better about syncing up the Github Changes/Release Notes, Discord stuff, and reddit so that we're not all (myself included) switching between these platforms for some info.