OpenWRT Guest WiFi Email Capture: NoDogSplash vs a Managed Portal

If you have searched for "OpenWRT guest WiFi email capture," you are almost certainly technical, you like owning your stack, and you have probably already flashed OpenWRT onto a router or two. This post is an honest comparison of two routes to the same goal: a DIY build on OpenWRT with NoDogSplash, versus pointing OpenWRT at a managed external portal. No marketing fluff, just where each approach starts and stops.

What OpenWRT and NoDogSplash actually do

OpenWRT is open-source firmware that turns a supported router into a fully configurable Linux network device.

NoDogSplash is the classic captive portal daemon for OpenWRT. Its successor, openNDS, is the more actively maintained option today. Both do the same core job: when a new device joins the network, traffic is intercepted and the user is shown a splash page before being allowed through. That is the foundation of any captive portal.

NoDogSplash and openNDS are gateways. Out of the box they present a page and grant access. openNDS also ships a username and email login sequence (login_option_enabled set to 2) alongside its default click to continue page, and what happens with the details a guest enters is up to whatever you build behind the splash.

The DIY path: what it involves

To get from "splash page appears" to "I have a usable list of customer emails," a pure DIY OpenWRT build needs you to assemble several pieces yourself:

• A splash page with an email form, either written from scratch or started from openNDS's username and email theme.
• A backend to receive that form submission, validate it and store it somewhere (a database or a third-party form endpoint).
• The Forwarding Authentication Service (FAS) or binauth integration in openNDS so the gateway actually authorises the device after the form is submitted.
• An email platform wired in if you want to send welcome emails, offers or review requests.
• UK GDPR consent handling: a separate marketing opt-in, a privacy notice, and a stored record of when and how consent was given.
• Ongoing maintenance: firmware updates, certificate renewal, walled-garden rules so the form's own assets load, and fixes when an OS update changes captive-portal detection behaviour.

None of this is impossible. People do it. But it is a real project with a real maintenance burden, and the GDPR side in particular is easy to under-build, because consent records and retention are the parts a hobby project tends to skip.

Where DIY stops

The honest limits of a pure OpenWRT and NoDogSplash build, even a good one:

If your goal is purely a "click to accept and connect" gateway for a home or hobby network, a DIY build is genuinely a fine choice and you do not need anything else. If your goal is to capture customer data from guest WiFi and use that list to drive repeat visits, the gap above is the work you are signing up for.

The managed external portal path

The second route keeps the part OpenWRT is good at (intercepting connections) and hands off the part that is a project (capture, consent, email, reviews, analytics) to an external managed portal. The gateway redirects guests to the portal URL, the portal handles the branded page and everything behind it, then authorises the device back through the gateway.

Worth knowing if you came here as an OpenWRT enthusiast: CaptiFi itself runs on OpenWRT-based plug-and-play hardware. So the managed approach is OpenWRT with the marketing layer already built and maintained for you, without hand-rolling the FAS integration, the consent store and the email automation. CaptiFi also has setup guides for 9 vendor ecosystems, MikroTik, UniFi, Omada and Meraki among them, so you are not locked in.

Side-by-side comparison

Which should you choose?

Be honest about your goal:

• You want a learning project, a home gateway, or full control and you enjoy the build. Go DIY with openNDS. It is the right tool and you will learn a lot.
• You run a venue and want a list, reviews and repeat visits without becoming a part-time captive-portal maintainer. Use a managed external portal. You keep the OpenWRT foundation and skip the integration work and the GDPR risk of under-building consent.

For the venue use case, our guide on capturing emails from guest WiFi and our GDPR-compliant guest WiFi article cover the marketing and compliance sides in depth, and you can start a 30-day trial (you add a card to start) on the CaptiFi device, which is OpenWRT-based and comes on a refundable deposit, to see the managed path in practice.

Sources: openNDS, documentation overview and ThemeSpec script files, both read on 28 October 2026. The product names here belong to their owners; CaptiFi is not affiliated with or endorsed by them.