Manual Pages

Table of Contents


na_traceroute6 - print the route IPv6 packets take to a network node


traceroute [ -dlnrv ] [ -f first_hop ] [ -m max_hops ] [ -p port ] [ -q nqueries ] [ -s src_addr ] [ -g gateway ] [ -w wait ] host [ data_size ]


The traceroute6 utility uses the IPv6 protocol hop limit field to elicit an ICMPv6 TIME_EXCEEDED response from each gateway along the path to some host.

The only mandatory parameter is the destination host name or IPv6 address. The default probe datagram carries 12 bytes of payload, in addition to the IPv6 header. The size of the payload can be specified by giving a length (in bytes) after the destination host name.

Other options are:

Debug mode.


Specify how many hops to skip in trace.


Specify intermediate gateway ( traceroute6 uses routing header).

Print both host hostnames and numeric addresses. Normally traceroute6 prints only hostnames if -n is not specified, and only numeric addresses if -n is specified.


Specify maximum hoplimit, up to 255. The default is 30 hops.

Do not resolve numeric address to hostname.


Set UDP port number to port.


Set the number of probe per hop count to nqueries.

Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-attached network, an error is returned.


src_addr specifies the source IPv6 address to be used.

Be verbose.


Specify the delay time between probes.

This program prints the route to the given destination and the round-trip time to each gateway, in the same manner as traceroute.

Here is a list of possible annotations after the roundtrip time for each gateway:

Destination Unreachable - No Route to Host.

Destination Unreachable - Administratively Prohibited.

Destination Unreachable - Not a Neighbour.

!A Destination Unreachable - Address Unreachable.

This is printed if the hop limit is <= 1 on a port unreachable message. This means that the packet got to the destination, but that the reply had a hop limit that was just large enough to allow it to get back to the source of the traceroute6. This was more interesting in the IPv4 case, where some IP stack bugs could be identified by this behavior.

This program is intended for use in network testing, measurement and management. It should be used primarily for manual fault isolation. Because of the load it could impose on the network, it is unwise to use traceroute6 during normal operations or from automated scripts.


When run from a vfiler context, (e.g. via the vfiler run command), traceroute6 operates on the concerned vfiler.


na_traceroute(1), na_ping6(1), na_ping(1), na_netstat(1), na_vfiler(1)

Table of Contents