doona
Interface tour
Demo
English

Interface tour

This page shows where things are in doona after you sign in: the four navigation sections, the top bar, and the tabs, detail panels and action menus inside a page. It also explains how Hold, Apply and Save differ, how to confirm that a change took effect, and how the layout changes on a phone.

In a window at least 1024 px wide, the sidebar lists the pages under four sections. Select a page name to open it.

Activity

  • Activity: outbound mode, download and upload rates, active connections, the current node, CPU, traffic, outbound usage, top devices and domains, memory and notifications.
  • System status: engine state, traffic counters, memory, datapath attachments and backend features, with Export state JSON.

Monitor

  • Connections: Traffic and Connections tabs. Select a connection to see its route and actions.
  • Routing log: Map and Records tabs.
  • DNS: Statistics, Resolution log, Cache and Query tabs, as far as the backend provides them.
  • Logs: the live engine log, with Level and Module filters, Pause, Clear and Export.
  • Events: backend state changes, with Export JSON.

Routing

  • Policies: Groups and Group membership tabs. Select nodes for a group or change its members.
  • Nodes: nodes and their subscriptions, usage and refresh. The Latency tab appears when the backend provides a node list.
  • Rules: Routing rules, DNS rules and Trace simulation tabs; the DNS rules tab appears only when the backend provides it.

Settings

  • Configuration: Modules, Quick setup, Sources and Validation tabs; Quick setup appears only when it is available.
  • Settings: the Backend, Backend options, Geodata, Appearance, Backend actions and About cards.

A page stays in the navigation when the backend does not provide it. Opening it shows This backend does not provide this page and a Back to activity button; see feature requirements.

Press ? to open Keyboard shortcuts. Press g and then a page letter within 800 ms to open that page, for example g r for Rules.

Use the top bar

  1. Select the backend indicator at the bottom of the sidebar. A popover shows the engine and version, the connection state (for example Connected or Sign-in required), the API, the Backend URL and the profile. Select Edit backend to open the Backend card on Settings, or About doona for version details.
  2. Select the search field, or press Ctrl K (⌘K on macOS). Type part of a page, tab, node, group or node source name, a live connection, a configuration file path or a rule expression. Select a result to open it.
  3. When rules are held, a check-mark button with the number of held rules appears. Its name is Apply (N), or Apply (N); writes F files when the rules go to more than one file. Select it to write every held rule; see the held list.
  4. Select Reload honk and confirm in the Reload honk? dialog. honk reads its configuration files again and reloads; held rules are not written. The button appears only when the backend offers a reload.
  5. Select Refresh, or press r, to read all displayed data from the backend again. A Data refreshed. toast confirms it. Refresh does not write anything and does not reload honk.
  6. Select the Theme button to switch between light and dark. When the theme follows the system, it switches to the opposite scheme; the next press returns to System. The Language and Palette menus sit beside it; Palette also holds the Wordmark choice.

Apply (N) and Reload honk wait for each other: while one runs, the other is disabled.

Use tabs, details and actions

  1. Select a tab under the page title to change the view within the page. The tab changes the view, not the page.
  2. Select a row on Connections, Routing log or DNS to open its details. In a window at least 1200 px wide, the details appear in a panel beside the list; in a narrower window they open in a drawer.
  3. Use the panel's one primary button for the main task. On a connection, this is Add rule.
  4. Open More actions (the vertical dots button) for the other commands. On a connection, these include Show matched rule, View flow, Trace this connection and Close connection; the destructive command is last.
  5. Close the panel with Close or Esc.

Hold, apply or save

  • Hold appears only in the Add rule dialog opened from observed traffic, such as a connection or a DNS record, where it is the highlighted button. Hold puts the rule in the held list without writing it. Held rules are written later with Apply (N) in the top bar or Apply held rules on the Rules page; see the held list. The Add rule dialog on the Rules page writes at once; see adding a rule.
  • Apply writes the change to the backend now. In the Add rule dialog opened from observed traffic, Apply writes that rule and reloads honk at once. Configuration uses Apply to write an edited source, and the Backend options card on Settings uses Apply for runtime changes that are not written to the configuration file; see editing a source and backend options.
  • Save stores a backend profile in this browser. Saving reloads the page to use the profile; see Settings.

Check that a change took effect

  1. Read the toast after the write. A rule write shows New rule is in effect, Rule change is in effect, or N rules are in effect after Apply (N).
  2. Read the toast detail: Existing connections keep their current route until they reconnect.
  3. To check the new route, open Connections and inspect a connection opened after the change.

If a write fails, the toast shows the reason, and held rules that were not written stay held. For a read-only configuration file, see troubleshooting.

Navigate on a phone

In a window narrower than 1024 px, the sidebar is replaced by a bottom bar and a page strip.

  1. Select Activity, Monitor, Routing or Settings in the bottom bar. Each section opens on the page you last visited in it during this browser session, or on its first page.
  2. Select a page in the strip above the content. When the pages do not fit, swipe the strip sideways; the current page stays in view.
  3. Open More options (the vertical dots button) in the top bar for the Language, Theme, Palette and Wordmark menus, Reload honk, and Backend. Backend opens the same popover as the sidebar indicator.
  4. Use the search button, Refresh and Apply (N) directly in the top bar; they stay outside the menu.
  5. In a page toolbar, the first action stays a button and the others move into More actions.

For installing honk and doona, see the installation guide; for the configuration file, see Configuration.

doona

doona documentation

English
doona documentationdoona is a static web UI for the native API that the daeuniverse engines share: honk today, dae once it implements the same contract. Requirements Install on Debian or UbuntuThis page installs doona from its .deb package and honk-core from the same doona release on Debian, Ubuntu and other APT-based systems. Install on Fedora or RHELThis page installs doona from its .rpm package and honk-core from the same doona release on Fedora, RHEL and other DNF-based systems. Install on Arch LinuxThis page installs doona from its .pkg.tar.zst package and honk-core from the same doona release on Arch Linux and other pacman-based systems. Install on GentooThis page installs doona with Portage from the ebuild in doona’s repository, and honk-core from the same doona release. Install on OpenWrtThis page installs doona and honk-core on OpenWrt 25.12 from the release archives. Install on other systemsThis page installs doona and honk-core from the release archives on a Linux system without a doona package, such as Alpine Linux. 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. First sign-inThis page opens doona in a browser, creates the administrator account and checks that doona shows the running honk. Interface tourThis page shows where things are in doona after you sign in: the four navigation sections, the top bar, and the tabs, detail panels and action menus inside a page. Watching trafficThis page covers the Activity hub (Activity and System status) and the Monitor hub (Connections, Routing log, DNS, Logs and Events). Routing, nodes and rulesThis page covers the Routing hub: the Policies, Nodes and Rules pages. Config and settingsThis page covers the Configuration page, where you read, validate and apply honk's configuration files. Common tasksThis page collects short procedures for frequent changes to routing, traffic inspection and honk maintenance. ConfigurationThe configuration is two files. FeaturesFirst confirm that the gateway carries traffic. Troubleshooting DevelopmentRead CONTRIBUTING.md before opening a pull request.