Summary

Use RobustOS CLI ping to send network probes and traceroute to display the route toward a target. Connect to the CLI with an authorized account; see Get started with the RobustOS CLI.

Choose a target appropriate to the connection you want to check. Wait for the output and prompt before entering another command.

Command Table

Replace <host> with the target address or hostname, <if_name> with the source interface name, and <ip_addr> with the source IP address.

Examples

Ping an IPv4 address

This local-address example shows the command and response together:

# ping ip 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: seq=0 ttl=64 time=0.514 ms
64 bytes from 192.168.0.1: seq=1 ttl=64 time=0.307 ms
64 bytes from 192.168.0.1: seq=2 ttl=64 time=0.330 ms
64 bytes from 192.168.0.1: seq=3 ttl=64 time=0.306 ms
64 bytes from 192.168.0.1: seq=4 ttl=64 time=0.310 ms

--- 192.168.0.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.306/0.353/0.514 ms

The summary reports five packets transmitted and five received, with 0% packet loss. The round-trip line gives the minimum, average and maximum response times. Because the target is the router’s own address, this example does not test connectivity to another host or the internet.

Ping an IPv6 address

This example tests the device’s IPv6 loopback address:

# ping ipv6 ::1
PING ::1 (::1): 56 data bytes
64 bytes from ::1: seq=0 ttl=64 time=0.407 ms
64 bytes from ::1: seq=1 ttl=64 time=0.338 ms
64 bytes from ::1: seq=2 ttl=64 time=0.343 ms
64 bytes from ::1: seq=3 ttl=64 time=0.339 ms
64 bytes from ::1: seq=4 ttl=64 time=0.363 ms

--- ::1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.338/0.358/0.407 ms
#

Five replies were received. A successful loopback test does not establish that an external IPv6 route or host is reachable.

ARP mode: an error example

In this R5030 firmware 5.6.0 test, ARP mode returned an option error. The excerpt below omits the subsequent usage text:

# ping arp 192.168.0.2
arping: invalid option -- 'W'

This error is not a reachability result for the target. If the same error occurs, record the firmware version and contact Technical Support with the command and error output.

Trace an IPv4 route

This example traces the router’s own IPv4 address:

# traceroute ip 192.168.0.1
 traceroute to 192.168.0.1 (192.168.0.1), 30 hops max, 46 byte packets
 1  192.168.0.1  0.057 ms  0.057 ms  0.045 ms
#

The output shows a single hop to the local address. It does not show the route to an external host.

Trace an IPv6 route

This example traces the IPv6 loopback address:

# traceroute ipv6 ::1
 traceroute to ::1 (::1), 30 hops max, 72 byte packets
 1  ::1  0.054 ms  0.051 ms  0.042 ms
#

The output shows a single local hop; it does not confirm an external IPv6 route.

Specify the source interface

This local test specifies lan0:

# traceroute ip 192.168.0.1 interface lan0
 traceroute to 192.168.0.1 (192.168.0.1), 30 hops max, 46 byte packets
 1  192.168.0.1  0.038 ms  0.040 ms  0.038 ms
#

The command returned a local hop. This output alone does not confirm which interface carried the packets.

Specify the source address

This local test specifies the source IPv4 address:

# traceroute ip 192.168.0.1 source 192.168.0.1
 traceroute to 192.168.0.1 (192.168.0.1) from 192.168.0.1, 30 hops max, 46 byte packets
 1  192.168.0.1  0.046 ms  0.037 ms  0.140 ms
#

The header reports the source address. This example does not independently verify the source address on the wire.

Resolve a hop name

This local test requests name resolution:

# traceroute ip 192.168.0.1 resolve
 traceroute to 192.168.0.1 (192.168.0.1), 30 hops max, 46 byte packets
 1  router (192.168.0.1)  0.035 ms  0.034 ms  0.039 ms
#

The hop is displayed as router with its IP address. Results depend on name resolution available to the device.

Ping using the default mode

The default-mode command also sends IPv4 probes in this local test:

# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: seq=0 ttl=64 time=0.548 ms
64 bytes from 192.168.0.1: seq=1 ttl=64 time=0.294 ms
64 bytes from 192.168.0.1: seq=2 ttl=64 time=0.337 ms
64 bytes from 192.168.0.1: seq=3 ttl=64 time=0.305 ms
64 bytes from 192.168.0.1: seq=4 ttl=64 time=0.309 ms

--- 192.168.0.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.294/0.358/0.548 ms
#

The target is the router’s own address; this does not test an external path.

Trace IPv6 using a source interface

This local test specifies the loopback interface:

# traceroute ipv6 ::1 interface lo
 traceroute to ::1 (::1), 30 hops max, 72 byte packets
 1  ::1  0.093 ms  0.053 ms  0.056 ms
#

The returned hop is local. The actual packet interface was not independently verified.

Trace IPv6 using a source address

This local test specifies the loopback source:

# traceroute ipv6 ::1 source ::1
 traceroute to ::1 (::1) from ::1, 30 hops max, 72 byte packets
 1  ::1  0.108 ms  0.038 ms  0.047 ms
#

The header reports the source address; no packet capture was performed.

Trace IPv6 with name resolution

This local test requests name resolution:

# traceroute ipv6 ::1 resolve
 traceroute to ::1 (::1), 30 hops max, 72 byte packets
 1  ::1 (::1)  0.037 ms  0.035 ms  0.037 ms
#

The response shows the loopback address; it does not establish that external hostnames resolve.

Related information

• RobustOS CLI Status Command Reference
• RobustOS CLI Guide