> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/telecom-references/developer-reference/toolpack-api/tbrouter.md).

# tbrouter

### Started By

tbrouter is a service spawned by the operating system.

### Role

tbrouter is an application that handles all IP traffic for LAN/WAN interfaces.

It is responsible for:

* Manage LAN/WAN IP interfaces
* Act as a firewall to protect against intrusion.
* Protects against DDoS

### High Availability

tbrouter is always active on each host it is running on.

### Resynchronization

Tbrouter will synchronize its configuration from tboamapp. This includes the configured interfaces, vlans and ACLs. Tbrouter will also synchronize RTP/RTCP resources from toolpack\_engine

### Particularities

Tbrouter is a special applications that takes control of CPU core of the servers it is running on. Normally two CPU cores are assigned to the Tbrouter application and these CPUs will show being used at 100%. So Tbrouter application will show 200% CPU usage with applications such as 'top'.

### Logs

The logs for the *T*ctrl tbrouter application as follows:

> \[InstallDir]/tbrouter /lib/tb/toolpack/tbrouter


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tmediadocs.telcobridges.com/telecom-references/developer-reference/toolpack-api/tbrouter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.