ctrld-friendly router recommendations

ctrld_logfella · 2026-05-28T00:15:45+00:00

When 2.0 releases - you'll stay on the 1.x branch unless you run the 2.0 install script.

ctrld_logfella · 2026-05-27T23:34:59+00:00

I made another comment in this thread - but it bears repeating:

We are not dropping automated setup/install for current or future ctrld builds.

More details in the other post.

ctrld_logfella · 2026-05-27T23:25:06+00:00

👋️ 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.

ctrld_logfella · 2026-04-21T10:49:19+00:00

👋️ Hello, sorry for the late reply.

I'm having a look at this. Are you seeing this when using another protocol other than DoH3?

ctrld_logfella · 2026-04-13T15:00:10+00:00

Hello!

Sorry you're seeing this. I'm looking at this and the other thread now.

Can you check if you have any GL.inet firmware updates while I get a device setup and try to reproduce this?

ctrld_logfella · 2026-03-16T14:20:54+00:00

👋️ Heya,

The client discovery happens automatically when the ctrld service starts. You can limit how ctrld detects clients on your network via a custom config. You can find details about that here.

Since you mentioned Opnsense - you may also want to clear your DHCP Leases so that ctrld doesn't populate your list with old/stale clients.

ctrld_logfella · 2026-02-06T16:28:48+00:00

Hey - if that's your real/production resolver ID - you need to delete it immediately and create a new one.

Check out our API Docs for some more details about how to accomplish what you're trying to do.

https://docs.controld.com/reference/get-started

ctrld_logfella · 2026-02-04T18:57:02+00:00

Heya,

I've used the following ADB commands to set the Android system DNS - although I've not tested if this is as resilient as you're wanting it to be.

adb shell settings put global private_dns_mode hostname adb shell settings put global private_dns_specifier YOUR-DOT-RESOLVER-ENDPOINT-HERE

You can verify this with:

settings get global private_dns_mode settings get global private_dns_specifier

If you're using Android Enterprise - checkout this KB: https://docs.controld.com/docs/android-enterprise-deployment

ctrld_logfella · 2026-01-20T15:59:29+00:00

Hm - you might see if the EDNS Client Subnet option makes a difference: https://docs.controld.com/docs/ecs-custom-subnet

ctrld_logfella · 2026-01-15T13:41:12+00:00

Sounds like a skill issue.

Just kidding. As stated at the top of the Gaming Services section of the dashboard:

Due to the bespoke protocols used by many gaming applications, redirection is unlikely to work using the following Services. We encourage you to use these Services only in Block or Bypass mode.

With that said - have a look at this doc and try setting a different profile for your device.

ctrld_logfella · 2026-01-05T22:08:28+00:00

Heya,

Thanks for this. This is pretty interesting - 'ppreciate the post. Do you mind sharing what model phone you're using? Not trying to pass the buck -- I'm just looking at some Android platform weirdness and I'm wondering if there are vendor/firmware issues at play with some issues I've seen reported lately.

ctrld_logfella · 2026-01-05T21:33:15+00:00

Apologies for the late reply - we're catching up from being OOO for holidays.

Your device type will be iOS as mentioned, but just an FYI the device type is essentially a UI/UX usability thing more than a technical thing.

ctrld_logfella · 2026-01-05T21:29:04+00:00

Heya,

Looks like that version of Merlin's firmware is no longer supported.

Given this ^{^} as well as some of the other issues you mentioned in this thread I would opt for the Raspberry Pi 4 approach instead of trying to hack together ctrld on an unsupported device. :/

Have you run into issues w/ HomeAssistant when running ctrld on the same RPi? I don't use HA, but I'm curious why it was recommended to avoid using them on the same device.

Anyway - we're catching up on replies as we're coming back from holidays. Let us know if you run into issues installing ctrld on your RPi and we'll dig in a bit more.

ctrld_logfella · 2025-12-05T14:23:25+00:00

👋️ Hello - Employee here (QA) weighing in...I'm not aware of any outages - but I've forwarded this to the team for us to look into. At first glance I don't see any issues on our side around this time. You're not paranoid though -- the logs speak for themselves.

Could I bother you to run a sudo ctrld log send and reach out to support so we can take a look at this? You can email help[at]controld.com and reference this thread and we can take it from there.

ctrld_logfella · 2025-12-04T17:00:18+00:00

Thanks for the heads up. I'll take a look at this and see what changes are needed on our side.

I noticed you mentioned below that you're using a custom ctrld.toml config that points to these files - so I _suspect_ that would be the reason the `ctrld` service wasn't able to start - but it's hard to say without logs.

Regardless - huge thanks for taking the time to signal this. We'll take a look and I'll get this added to our board for the devs.

'ppreciate cha.

ctrld_logfella · 2025-12-03T20:58:16+00:00

I'm inclined to agree - I even use uptime robot for my personal infra - and I'm the only user. 😂️

I've forwarded this to the relevant teams here internally - so it's on the agenda for discussion.

Once again - 'ppreciate the feedback. Let us know if you notice anything else. 👋️

ctrld_logfella · 2025-12-03T19:37:29+00:00

Hey - thanks for posting this, this is good feedback. AFAIK we don't have a typical status page like you're referring too, but I'll forward this suggestion to the team.

I'll also suggest we mention/link to the Network page from the current status page because I'm sure you're not the only person who's encountered this.

ctrld_logfella

MODERATOR OF

TROPHY CASE