doona
First sign-in
Demo
English
First sign-in

First sign-in

This page opens doona in a browser, creates the administrator account and checks that doona shows the running honk. honk must be running, as Service management leaves it.

This page covers the standard edition; for doona lite, see doona lite.

Before you start

  • A computer or phone on the LAN, or the gateway itself. honk accepts the administrator setup only from loopback, private or link-local addresses.
  • The listen address from Minimal configuration, such as 192.168.1.1:9527.

1. Open doona

Open this address in the browser, with your address in place of 192.168.1.1:

http://192.168.1.1:9527/ui/

doona finds honk’s API at the same address and saves it as its backend. If no administrator exists, it opens Create the administrator.

Administrator setup with username, password and confirmation fields

Use the three icons at the upper right to change Language, Palette and Color scheme before signing in. The sign-in form is one centered card on every screen size. With a Glass palette, a custom wallpaper also appears behind the card.

The sign-in card over the Glass wallpaper

2. Create the administrator

  1. Enter a Username: letters, digits, _, . and -, 1 to 64 characters.
  2. Enter a Password of 8 to 128 characters, and the same password under Confirm password.
  3. Select Create and sign in.

doona signs you in and opens the Activity page. honk keeps the account in its state database, /var/lib/honk/state/honk.db (/etc/honk/data/state/honk.db on OpenWrt). From now on the page is titled Sign in and asks for this username and password.

The password session is kept in this browser and shared by all tabs on this origin. Closing a tab or the browser does not end it; sign-out, honk’s 401 response or deleting the profile clears it. honk limits sessions to 12 hours and forgets them when it restarts.

3. Check System status

Select System status in the side navigation. On a phone, select Activity in the bottom bar, then System status in the page strip. With honk running, it shows:

  • Running at the top of the page.
  • The Engine card: under Engine, honk and its version; under API, daeuniverse/native v1 (draft); under Build, the honk commit and the build target you installed.
  • The Backend features card, listing what this honk provides, such as Connections, Logs and Configuration.

The backend indicator opens a popover with the honk version and connection state. Traffic counters stay at 0 until traffic passes through honk.

Setup is complete. To route LAN devices, add nodes and rules, see Configuration and Features.

If it doesn’t work

You see Cause and fix
The browser cannot connect honk is not running, or the address differs from listen. Check step 3 of Service management and curl http://192.168.1.1:9527/api on the gateway. A firewall on the gateway can also block port 9527.
This honk build has no native API The installed honk-core lacks the native API. Install the build from the doona release; see honk version.
The backend accepts administrator setup only from loopback, private or link-local addresses. The browser reached honk from a public address. Open doona from a device on the LAN, or on the gateway itself.
The username or password is incorrect. Enter them again. To replace a forgotten administrator, stop honk, run sudo /usr/local/bin/honk-core admin reset (without sudo in a root shell; on OpenWrt, /usr/bin/honk-core --data-dir /etc/honk/data admin reset), then start honk; the setup page opens again.
Token required instead of the setup page api.dae sets secret instead of password_auth: true. Enter that secret as the token, or change api.dae as in Minimal configuration and restart honk.

Token sign-in with the Token field, show/hide control and Connect button

Enter the backend secret in Token, use the show/hide control to check it, then select Connect. doona saves the Token in the current browser's connection profile.

For more, see Sign-in problems.

doona

doona documentation

English
doona documentationFor a direct-only first run, follow Quick start. Quick startStart the standard edition of doona with a direct-only honk configuration, sign in, and verify traffic from the gateway itself. Standard edition and doona liteThe standard edition manages configuration and observes traffic. Requirements Install on Debian or UbuntuInstall doona from the doona-web .deb package and honk-core from the same release on Debian, Ubuntu or another APT-based system. Install on Fedora or RHELInstall doona from its .rpm package and honk-core from the same release on Fedora, RHEL or another DNF-based system. Install on Arch LinuxInstall doona from its .pkg.tar.zst package and honk-core from the same release on Arch Linux or another pacman-based system. Install on GentooInstall doona with Portage from the repository's ebuild in a local ebuild repository, and honk-core from the same release. Install on OpenWrtInstall doona from a release package or archive and honk-core from the same release on OpenWrt 25.12. Install on other systemsInstall doona and honk-core from release archives on an x86_64 or aarch64 Linux system that meets the kernel requirements below. Installation detailsInstall honk, write its configuration, then install doona and start honk. Minimal configurationThis page writes the smallest honk configuration that starts honk and serves doona, then checks it by starting honk by hand. Service managementThis page runs honk as a systemd or OpenWrt procd service: it creates the service once, then lists the commands that start, stop, restart and reload honk and read its log. Route your first connectionContinue from Quick start, with honk running and your administrator signed in. First sign-inThis page opens doona in a browser, creates the administrator account and checks that doona shows the running honk. Interface tourUse the navigation to open a page, the top bar to search or refresh, and the page tabs to change views. Watching trafficUse Activity and System status to read engine health, and Connections, Routing log and DNS to inspect traffic. Routing, nodes and rulesPolicies manages group selection and membership. Config and settingsConfiguration reads, validates and applies honk's configuration files. Common tasksThis page covers the standard edition; for doona lite, see doona lite. FeaturesFor each feature’s prerequisites and disabled-action explanations, see Feature requirements. doona litedoona lite edits honk configuration through a smaller interface for beginners. Connect doona liteConnect doona lite to the honk native API, or open the demo without a backend. Common tasks in doona liteUse doona lite to import resources and edit honk configuration. ConfigurationUse this reference for honk's DAE settings exposed by doona, their defaults, and their application paths. What doona can changedoona changes configuration sources, runtime state, persistent geodata settings, and browser preferences through different controls. Feature requirementsFind your standard-edition feature in the table, then use its section to check prerequisites and enable it. Troubleshooting DevelopmentRead CONTRIBUTING.md before opening a pull request.