Basics

App Tour

Understand where everyday Tunna work happens.

Updated 2026-06-02

Tunna is organized around three everyday work areas: Outbound for proxy nodes, Routing for traffic decisions, and Settings for app behavior. Imports, shares, QR scans, and paste actions may open Resources first so you can review what will be added before anything enters your setup.

Where to start

Outbound

The home for local nodes, subscription groups, latency, stats, and the current node selection.

Good fit You need to add a server, import a provider profile, pick the active node, run RTT checks, view node stats, use ZAP, share a node, or update a subscription group.

Not ideal You are deciding which websites or networks should use the node. That belongs in Routing.

Routing

The rulebook for traffic after it enters the tunnel.

Good fit You want everything proxied, selected sites proxied, trusted traffic sent direct, unwanted traffic blocked, or one destination pinned to a specific node.

Not ideal You are fixing a bad server profile. Confirm the node first in Outbound.

Settings

The app behavior and maintenance area.

Good fit You need tunnel startup behavior, subscriptions, assets, health checks, logs, shortcuts, resets, or support details.

Not ideal You only need to switch from one working node to another.

Everyday workflow

Use this order when you are setting up a profile, testing it, and then adding more automation.

Add or import material

Start in Outbound for nodes and subscriptions, or paste shared routing material from Routing. If Resources appears, review it before saving.
Pick a working node

Let RTT checks run, compare latency or stats, choose a node manually, or use ZAP after checks have enough recent results.
Choose routing behavior

Set the Default Route, then add specific rules for destinations that should use Proxy, Freedom, Blackhole, or one selected node.
Automate only after testing

Keep startup manual until the node and route plan work, then enable On-Demand or trusted networks if they match your use case.

Settings rows are grouped by visible headings

The Settings screen uses Network, General, and Misc as headings inside one page. They are not separate manual pages; each row below them opens its own view.

Network heading

Advanced traffic recognition and connection behavior.

Routing

Domain lookup strategy for rule matching.

Sniffing

Destination and application-protocol recognition.

Policy

Connection buffer and timing limits.

Protocol

Proxy multiplexing, Freedom behavior, and Blackhole defaults.

Observability

Health checks that keep node latency useful.

General heading

Everyday maintenance and automation.

Tunnel

Manual, Always On, On-Demand, trusted networks, network routing controls, and IPv6.

Assets

Reusable GeoSite and GeoIP records.

Subscriptions

Provider profiles and managed node lists.

Log

Diagnosis entries for short troubleshooting sessions.

Shortcuts

Automation commands and share links.

Misc heading

Version, support, reset, and support-only diagnostics.

About

Application version, Contact Support, and Community.

Reset

Danger Zone recovery for the system VPN profile and selected app settings.

Debug

Running configuration JSON for support-guided diagnosis.

How imports enter Tunna

Shared links, QR codes, scans, and paste actions do not silently overwrite your setup. Tunna opens Resources first when there is importable material to review.

Open, scan, or paste

Tunna can receive Tunna import links, QR scans, pasted node links, pasted subscription URLs, and shared rule or node links.
Check the Resources list

Nodes, rules, subscriptions, and asset-backed rules are listed separately. Duplicate warnings appear when Tunna recognizes an existing item.
Wait for fetches

Remote subscriptions and rules that need assets may fetch before Import is available. Failed or unfinished fetches should be reviewed before continuing.
Import only what you need

Select the resources you want, choose the routing target when Tunna asks, then import them into the app.