> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/hera604/configure/basic-settings/routing.md).
# Routing
Open **Basic Settings > Routing > Active and static routes**. The **Active routes** table shows the routes currently installed on the router.
| Field | Description |
| ----------- | ------------------------------------------------------------------------------------------------ |
| Destination | Network or host reached by the route. |
| Netmask | Defines the range of destination addresses covered by the route. |
| Interface | Router interface used to send matching traffic. |
| Gateway | Next router to which matching traffic is sent. `0.0.0.0` indicates a directly connected network. |
| Cost | Route weight. A lower cost is preferred when otherwise equivalent routes exist. |
#### Configure static routes
Use the **Static routes** table to send traffic for a specific host or network through a chosen interface or gateway.
> **Important:** An incorrect static route can send traffic to the wrong interface or make a network unreachable. Confirm the destination, netmask, gateway, and interface before saving.
| Field | Example | Description |
| ----------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| Name | monitoring | Descriptive name for the route. |
| Destination | 192.168.55.0 | Network or host to which the route applies. |
| Netmask | 255.255.255.0 | Defines the destination range. Use `255.255.255.255` for one host. |
| Interface | `loopback`, `lan`, `cellpri`, or `ethwan` | Interface used to send matching traffic. |
| Gateway | IP address | Next router for the destination. Leave blank only when the deployment design specifies a directly connected route. |
| Cost | Number | Route weight used when more than one route can reach the same destination. Lower values are preferred. |
Use **Create** to add a route, **Remove** to delete one, and **Promote** to move a route higher in the displayed list. Select **Save** after making changes.
---
# 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://docs.eseye.com/hera604/configure/basic-settings/routing.md?ask=&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.
