Routing Rules

Create practical rules for websites, networks, ports, protocols, and asset lists.

326 words 2 min
Routing RulesAssetsOn-DemandSearch en

A routing rule is a named decision with one or more real traffic conditions. The Rule Set is processed from top to bottom. Move specific rules above broader rules, because the first matching unpaused rule wins and the lower rules are not considered for that traffic.

A good rule has a purpose, a target, and a place

  1. Name the purpose

    Use names like Work Direct, Streaming Proxy, or Tracker Block so the list stays readable.



  2. Choose the outcome

    Pick Proxy, Freedom, Blackhole, or a specific proxy node from the Outbound menu.



  3. Add focused conditions

    Start with one domain, IP, port, protocol, or asset record before combining many conditions.



  4. Place it carefully

    Specific rules should sit above broad rules because the first match wins.

General Settings

Rule Edit starts with the fields that make the rule readable in the list and decide what happens when it matches.

Use these cards as a map of the visible labels in this view. Each card names one field, control, or status item and explains what it is for before you change it or rely on it.

Name

Name is the label shown in the Rule Set. If you leave it blank, Tunna uses the rule's default name. A clear name is still worth adding when the rule will be shared or revisited later.

Readable names

Use names that describe intent, such as Work Direct, Streaming Proxy, or Tracker Block.

Outbound

Outbound is the rule outcome. The menu includes Proxy, Freedom, and Blackhole, followed by individual proxy nodes. Proxy means the currently selected node in Outbound; a specific node keeps this rule tied to that node even when the selected node changes.

Proxy

Use the current outbound node.

Freedom or Blackhole

Send matching traffic direct or drop it.

Specific proxy node

Send only this rule's traffic through a chosen node from the proxy-node list.