Use the RobustOS command-line interface (CLI) to view route information reported by the device.

Before you begin

Connect to the device CLI using an authorized account. See Get started with the RobustOS CLI for SSH instructions.

Display route status

Syntax

At the device CLI prompt, enter:

status route

Result

On the R5030, the output can include a route_table section. Route entries can show destination, netmask, gateway, interface and metric fields. The routes shown depend on the device's current configuration and network state.

Example output

The following example is based on output from an R5030 running RobustOS 5.6.0. The network addresses and route values are from this example and can differ on your device.

interfaces = "wwan lan0"
enable = false
route_table {
    id = 1
    destination = 0.0.0.0
    netmask = 0.0.0.0
    gateway = 100.65.4.190
    interface = wwan
    metric = 0
}
route_table {
    id = 2
    destination = 100.65.4.188
    netmask = 255.255.255.252
    gateway = 0.0.0.0
    interface = wwan
    metric = 0
}
route_table {
    id = 3
    destination = 192.168.0.0
    netmask = 255.255.255.0
    gateway = 0.0.0.0
    interface = lan0
    metric = 0
}

Read the example routes

The three entries in the example report the following:

1. Default route: Entry 1 has destination 0.0.0.0 and netmask 0.0.0.0. It reports 100.65.4.190 as the gateway and wwan as the interface.
2. Cellular network route: Entry 2 reports destination 100.65.4.188 with netmask 255.255.255.252 and interface wwan. This destination and mask describe the 100.65.4.188/30 network. The reported gateway is 0.0.0.0.
3. LAN network route: Entry 3 reports destination 192.168.0.0 with netmask 255.255.255.0 and interface lan0. This destination and mask describe the 192.168.0.0/24 network. The reported gateway is 0.0.0.0.

These addresses and interfaces are specific to this example. Your device may report different values.

For each route, destination and netmask identify the destination network, gateway shows the gateway value reported for the entry, interface names the interface, and metric shows its route metric. In this example, the second and third entries report a gateway of 0.0.0.0.

This command displays status; it does not add or remove a route. A displayed entry alone does not confirm that traffic reaches its destination.

Check for an expected route

1. Run status route and find the route_table entries.
2. Compare each entry's destination and netmask with the network you expect. For example, the LAN entry above reports 192.168.0.0 with mask 255.255.255.0, which describes 192.168.0.0/24.
3. Check the reported interface and gateway against your network configuration and expected route. A route can cover a destination without having the same address as that destination.
4. If an expected entry is missing or its fields differ, review the relevant interface and routing configuration and the current network state. A displayed entry alone does not confirm that traffic reaches its destination.

Related information

• RobustOS CLI Guide
• Find the device model and firmware version