doona
Common tasks
Demo
English

Common tasks

This page collects short procedures for frequent changes to routing, traffic inspection and honk maintenance. Each procedure states the result to expect and links to the section that describes the page in detail.

Send one site through a proxy from a live connection

  1. Open Monitor > Connections and select the Connections tab.
  2. Select a connection to the site. Its detail panel opens.
  3. In the detail panel, select Add rule. The Add rule dialog opens.
  4. Set Match by to Full domain.
  5. Set Outbound to the proxy group. The dialog shows the connection's current outbound and the rule preview.
  6. Check Insert. If the dialog says earlier rules may still match this traffic first, choose an earlier position.
  7. Select Apply to write the rule and reload now, or Hold to write it later with Apply (N) in the top bar.

After Apply, a notice says the new rule is in effect. In Rule mode, new connections that match use the new outbound unless an earlier rule matches them first; existing connections keep their route until they reconnect. The dialog has no Lock this outbound switch, so Global and Direct mode still override this rule; to keep the route in those modes, add the rule under Routing > Rules with Lock this outbound turned on. See the held list and the Add rule dialog.

Send a domain and its subdomains through a group

  1. Open Routing > Rules and select the Routing rules tab.
  2. Select Add rule. The Add rule dialog opens with Condition form set to Select.
  3. Set Match by to Domain suffix and enter the domain in Values. Separate several domains with commas.
  4. Set Outbound to the group.
  5. Turn on Lock this outbound if the rule must also apply in Global or Direct mode.
  6. Set Insert to a position before any rule that would match the same traffic first.
  7. Select Add rule in the dialog.

doona writes the rule to its source file and reloads. A notice says the new rule is in effect; existing connections keep their route until they reconnect. See Routing, nodes and rules.

Make a device bypass the proxy

The rule matches the device's source IP address, so the device needs a fixed address.

  1. Open Routing > Rules and select the Routing rules tab.
  2. Select Add rule. The Add rule dialog opens.
  3. Set Match by to Source IP and enter the device's IP address in Values.
  4. Set Outbound to direct.
  5. Turn on Lock this outbound so that Global mode does not override the rule.
  6. Set Insert to a position before any rule that would match this address first.
  7. Select Add rule in the dialog.

A notice says the new rule is in effect. New connections from that address go direct; existing connections keep their route until they reconnect. See Routing, nodes and rules.

Pick a group's node and return to automatic selection

  1. Open Routing > Policies and select the Groups tab.
  2. Find the group's card.
  3. Select a node in the card's node grid. A notice confirms the selection. If the node is pinned, the notice says the automatic policy is paused; otherwise it says whether existing connections were kept or interrupted.
  4. If the notice says the node is pinned and the automatic policy is paused, open the card's More actions menu and select Back to automatic to resume it.

After Back to automatic, a notice names the member the group now uses. See Routing, nodes and rules.

Add and refresh a subscription

  1. Open Routing > Nodes.
  2. Select Add subscription above the Sources table. A dialog opens.
  3. Enter Name and Subscription URL, then select Add.
  4. To refresh later, select the refresh button in the subscription's row of the Sources table.

After Add, doona selects the new row. If the backend can refresh subscriptions, doona refreshes it at once and the notice gives the node count or the failure. See Routing, nodes and rules.

Switch to global mode and choose an outbound

  1. Open Activity.
  2. On the Outbound mode card, select Global.
  3. On the Global mode outbound card, choose an outbound.
  4. Select Apply on the Outbound mode card.

doona writes the mode and outbound to the main configuration and reloads. A notice confirms the mode. See Watching traffic.

Find out why a connection took an outbound

  1. Open Monitor > Connections, select the Connections tab and select the connection.
  2. Read Outbound, Chain and Rule in the detail panel.
  3. To open the matched rule, open More actions in the detail panel and select Show matched rule. Routing > Rules opens with the rule selected.
  4. To test the route, open More actions and select Trace this connection. Trace simulation opens with the connection's details filled in.
  5. Select Run trace.

The trace simulates routing with the current configuration; it does not replay the connection. See Watching traffic and Routing, nodes and rules.

Check how a domain resolves

  1. Open Monitor > DNS and select the Query tab.
  2. Enter the domain in Domain, choose a Type and select Query.
  3. Read the result card: the cache status, State, Upstream, Route source, Route rule, Elapsed and the answers.
  4. To see earlier resolutions, select the Resolution log tab and select a row for its details.

See Watching traffic.

Update geodata

  1. Open Settings > Settings.
  2. If the page has a Geodata card, select Update now next to Status.
  3. Otherwise, go to the Backend actions card and select Update under Geodata.

The update downloads and verifies the files, replaces the existing ones and reloads the configuration. A notice says geodata was updated and reloaded, or that the update failed. The button is absent when the backend cannot update geodata on request. See Config and settings and Troubleshooting.

Reload honk after editing files outside doona

  1. In the top bar, select Reload honk. On a narrow screen, open More options and select Reload honk.
  2. In the Reload honk? dialog, select Reload honk.

honk reads its configuration files again and reloads. Held rules are not written. A setting that needs a restart does not take effect until honk restarts; see Configuration. The top bar is described in the Interface tour.

Resolve a file that changed on disk while you edited it

  1. Open Settings > Configuration and select the Sources tab.
  2. Choose the file in Source. If the file changed on disk after you started editing, an alert says so and Apply is disabled.
  3. To keep the change on disk, select Cancel. Your draft is discarded and the editor shows the file as it is now.
  4. To replace the change on disk with your draft, select Keep changes, then select Apply.

Keep changes does not merge the two versions; Apply writes your draft over the file. See Config and settings.

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.