> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Routing

> How to set the main output, conditional branches and cascades between nodes in Flow.

Routing determines where the traffic goes after the input or transit node. The main path is given by the normal link between the blocks. The additional branch is created by the second link with the condition.

> [!NOTE]
>
> For whom: Panel Administrator, SRE. Required Rights: Managing Flow.

## Default exit

A normal input or transit unit can have one exit without conditions. It is used for all traffic that has not got into the conventional branch.

Possible exits:

* **Internet** - direct output
* **Transit Node** is the next managed server bridge in the cascade.
* **External transit node** is an external server bridge over the VLESS key;
* **WARP** – Exit via Cloudflare WARP
* **External proxy** - exit through a given proxy;
* **Blackhole**: Discard traffic.

## Conditions of communication

There's no separate "Rule Rule" block, so you can take some of the traffic in a different way.

1. Create an additional connection from the input or transit node to the desired output;
2. Open the communication parameters;
3. add conditions;
4. Save and check the circuit.

The types of conditions available depend on the configuration and may include:

* domain or suffix;
* IP address or CIDR;
* category `geosite`;
* category `geoip`;
* category **GeoAssets GeoSite** from the selected profile and GeoSet;
* category **GeoAssets GeoIP** from the selected profile and GeoSet;
* protocol;
* port;
* Input tag.

Several values within the same condition form a list of matches. Check the combination of conditions in the JSON Preview before applying.

> [!WARNING]
>
> The `geosite` or `geoip` field accepts a category name rather than a regular domain or IP address.

### Embedded Categories and GeoAssets

Categories `geoip` and `geosite` read from the corresponding files on the node. Do not consider any category available just because its name is entered in the rule: use the designer directory and check for the right set on all nodes where the rule is executed.

V. **Infrastructure by GeoAssets** Create profiles and GeoSet, assign them to the right nodes and sync them. One node can have multiple profiles. The same files with the same data are combined; conflicting versions block sync before sending the task to the agent. [GeoAssets](https://docs.axottle.com/en/operations/geo-assets.md).

Difference between types of conditions:

* **GeoSite / GeoIP** use categories from the Remnawave Node base files.
* **GeoAssets GeoSite / GeoAssets GeoIP** first offer to select a profile and GeoSet Axottle, and then the category found inside the selected file.

## Transit node

The transit node is an Axottle-managed server bridge that has its own config and a physical node binding, and it takes the traffic from the previous site and transmits it further.

An example of a cascade:

`Gateway → Входная нода → Транзитная нода → Internet`

Transit nodes can be multiple if the topology and configuration are tested. Transit can do the same thing as the input node: any number of conditional branches plus one common output, and "YouTube through a proxy, the rest directly" is collected on it in the same way, the rules are laid down in its own profile.

It is impossible to build a ring: a transit, closed on itself or on the previous site, is not drawn on the canvas, is not saved and is not compiled.

## Reused transit

For Pool Node, the route continues through the graph of the selected pool. The internal Internet completes the branch, and Continue Flow uses the connections outside the Pool Node. For conditional internal continuation, only one unconditional next block is allowed outside; conditions on both sides of this boundary are not maintained. [Transit pools](https://docs.axottle.com/en/connection-units/transit-pools.md).

## Address from which the node comes out

If a node has multiple addresses, the one from which it goes to the Internet is not given here, but the role of the address in the node card. [Network addresses](https://docs.axottle.com/en/nodes/network.md#роли-вход-и-выход).

One limitation that's important to keep in mind when assembling a circuit is that a block that has an address in the circuit must contain exactly one physical node. A bunch is compiled into one config for all of its nodes, and the address that one of them has for the rest is a command that they can't execute, and the compiler rejects that pattern with an explanation.

## External transit node

An external transit node is a ready-made server-bridge outside the current Flow. Axottle does not deploy its own managed config on it: the operator transfers the VLESS key, and the panel creates an outbound connection to this server.

Such a block is suitable when you need to continue the cascade through an existing external server. It is not just an exit point: it is a separate transit area with its own address, transport and security parameters.

The panel disassembles from the `vless://` key:

* UUID;
* host and port;
* transport;
* TLS or REALITY;
* SNI;
* Additional parameters of the selected transport.

After an external transit node, the traffic enters the Internet.

## Example of a conditional branch

Let the main traffic go directly, and the selected domains go through WARP:

1. connect the input node to **Internet** without the condition;
2. Add communication from the input node to the **WARP**;
3. set the second connection condition by domain;
4. Save, compile and check the JSON Preview.
5. Apply the pattern.

## Verification

> [!TIP]
>
> Routing is configured correctly when conventional input and transit blocks do not have ambiguous default outputs, all conditional connections have a purpose, and the compilation and linter pass without blocking errors.

After application, open the **Health** tab and make sure that all sections of the desired path are available.

## Rollback

* Before applying, press **Reset draft**.
* After application, go back to the previous working version of Flow.

## Typical errors

> [accordion] Two exits without conditions.
>
> Leave one main, and in the second connection set a condition.

> [accordion] Domain or IP is listed as a geo-category
>
> Transfer the value to the "Domain" or "IP/CIDR" condition. `geosite` and `geoip` specify the category name.

> [accordion] The Wrong Key to External Transit
>
> The key should start with `vless://` and contain the UUID, host, and mandatory parameters of the selected security mode.

Related pages: [ Constructor ](https://docs.axottle.com/en/connection-units/constructor.md), [ Diagnostics and samples ](https://docs.axottle.com/en/connection-units/diagnostics.md), [ Lifecycle and versions ](https://docs.axottle.com/en/connection-units/lifecycle.md).

Check the availability of features in the installed version in the panel.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.