Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/KevinCruz-cell/Redes-de-comunicaciones-/llms.txt

Use this file to discover all available pages before exploring further.

The static routes panel lets you manage persistent routes in your router’s network configuration. Both IPv4 (route) and IPv6 (route6) route types are supported. All changes are written to UCI and committed with uci commit network, making them survive reboots. Navigate to /router3/rutas to open the panel. An active session is required — unauthenticated requests are redirected to /login.

​
Route data structure

Routes are stored as anonymous UCI lists under the network package. The controller parses them using parseRutas(), which reads UCI output matching network.@route[n].* or network.@route6[n].*. Each route is represented as: 
{
  "id": "0",
  "interface": "wan",
  "target": "10.0.0.0",
  "gateway": "192.168.1.1",
  "metric": "0",
  "mtu": "1500",
  "table": "main",
  "type": "unicast",
  "source": "",
  "onlink": "0",
  "netmask": "255.255.255.0"
}
The netmask field is present only on IPv4 routes. IPv6 routes use CIDR notation in the target field instead.

​
Route fields

FieldRequiredIPv4IPv6Description
InterfaceYesYesYesUCI interface name traffic exits through (e.g. wan, lan)
Target (destination)YesYesYesDestination network address
NetmaskYesYesNoSubnet mask for the destination (e.g. 255.255.255.0)
GatewayYesYesYesNext-hop IP address
MetricNoYesYesRoute preference; lower values are preferred (default: 0)
MTUNoYesYesMaximum transmission unit for this route (default: 1500)
Routing tableNoYesYesKernel routing table (default: main)
TypeNoYesYesRoute type: unicast, local, broadcast, blackhole, unreachable, prohibit
SourceNoYesYesPreferred source address for packets matching this route
OnlinkNoYesYesFlag indicating the gateway is directly reachable on the link (no ARP needed)

​
Adding a route

1

Open the add form

Click Add route on the /router3/rutas page and choose IPv4 or IPv6.
2

Fill in the required fields

Enter at minimum: interface, target (destination network), gateway, and — for IPv4 — the netmask.
3

Configure optional fields

Set metric, MTU, routing table, type, source address, and the onlink flag if needed for your topology.
4

Submit

Click Add. The controller appends a new UCI section and commits:
uci add network route
uci set network.@route[-1].interface='wan'
uci set network.@route[-1].target='10.0.0.0'
uci set network.@route[-1].netmask='255.255.255.0'
uci set network.@route[-1].gateway='192.168.1.1'
uci set network.@route[-1].metric='10'
uci set network.@route[-1].mtu='1500'
uci set network.@route[-1].table='main'
uci set network.@route[-1].type='unicast'
uci commit network
For an IPv6 route, route is replaced by route6 and no netmask is set.

​
Updating a route

1

Click Edit

Click the Edit button next to the route you want to change.
2

Modify the fields

Update any field. If you clear the source address or uncheck onlink, those UCI keys are deleted.
3

Submit

Click Update. The controller uses the route’s array index (id) to address the correct UCI section:
uci set network.@route[0].interface='lan'
uci set network.@route[0].target='172.16.0.0'
uci set network.@route[0].netmask='255.255.0.0'
uci set network.@route[0].gateway='192.168.10.254'
uci -q del network.@route[0].source
uci -q del network.@route[0].onlink
uci commit network

​
Deleting a route

Click the Delete button next to the route you want to remove. The controller finds the route by matching both target and gateway values, resolves the array index, and runs: 
uci delete network.@route[<id>]
uci commit network
Deleting the wrong route can disrupt connectivity. Verify the target and gateway shown in the row before confirming the deletion.

​
UCI representation

The routes section of /etc/config/network looks like this after adding two IPv4 routes: 
config route
        option interface 'wan'
        option target '10.0.0.0'
        option netmask '255.255.255.0'
        option gateway '192.168.1.1'
        option metric '0'

config route
        option interface 'lan'
        option target '172.16.0.0'
        option netmask '255.255.0.0'
        option gateway '192.168.10.254'
        option metric '10'
        option table 'main'
IPv6 routes use config route6 blocks and omit the netmask option.
Static routes configured here are stored in UCI and survive reboots. They are separate from the routes shown on the dashboard’s routing table panel, which reflects the live kernel routing table via ip route show.

Dashboard

View the live kernel routing table alongside system metrics

Network interfaces

Manage the interfaces that static routes reference

Build docs developers (and LLMs) love

Get started for freeTalk to us