Table of Contents
na_ping6 - Sends ICMPv6 ECHO_REQUEST packets to network
ping6 [ -HnNqvwW ] [ -b sockbufsize ] [ -c count ] [ -i
interface ] [ -I interval ] [ -l preload ] [ -p pattern ]
-S sourceaddr [ -d datasize ] [ -h hoplimit ] [ hops... ]
ping6 uses the ICMPv6 protocol's mandatory
ICMP6_ECHO_REQUEST datagram to elicit an ICMP6_ECHO_REPLY
from a host or gateway. ICMP6_ECHO_REQUEST datagrams
("pings") have an IPv6 header, and ICMPv6 header formatted
as documented in RFC2463.
Set socket buffer size.
Stop after sending (and receiving) count
Specifies the number of data bytes to be sent. The
default is 56, which translates into 64 ICMP data
bytes when combined with the 8 bytes of ICMP header
data. You may need to specify -b as well to extend
socket buffer size.
- Specifies to try reverse-lookup of IPv6 addresses.
The ping6 command does not try reverse-lookup
unless the option is specified.
Set the IPv6 hoplimit.
Source packets with the given interface address.
This flag applies if the ping destination is a multicast
address, or link-local/site-local unicast
Wait interval seconds between sending each packet.
The default is to wait for one second between each
If preload is specified, ping sends that many packets
as fast as possible before falling into its
normal mode of behavior.
- Numeric output only. No attempt will be made to
lookup symbolic names for host addresses.
- Probe node information multicast group
(ff02::2:xxxx:xxxx). host must be string hostname
of the target (must not be a numeric IPv6 address).
Node information multicast group will be computed
based on given host and will be used as the final
destination. Since node information multicast
group is a link-local multicast group, destination
link needs to be specified by -i option.
You may specify up to 16 "pad" bytes to fill out
the packet you send. This is useful for diagnosing
data-dependent problems in a network. For example,
"-p ff" will cause the sent packet to be filled
with all ones.
- Quiet output. Nothing is displayed except the summary
lines at startup time and when finished.
Specifies the source address of request packets.
The source address must be one of the unicast
addresses of the sending node. If the outgoing
interface is specified by the -i option as well,
sourceaddr needs to be an address assigned to the
- Verbose output. Received ICMP packets other than
ECHO_RESPONSE are listed.
- Generate ICMPv6 Node Information FQDN query, rather
than echo-request. Option -d has no effect if -w is
hops IPv6 addresses for intermediate nodes, which will
be put into type 0 routing header.
- Same as -w , but with old packet format based on 03
draft. This option is present for backward compatibility.
Option -d has no effect if -w is specified.
IPv6 address of the final destination node.
When using ping6 for fault isolation, it should first be
run on the local host, to verify that the local network
interface is up and running. Then, hosts and gateways
further and further away should be "pinged". Round-trip
times and packet loss statistics are computed. If duplicate
packets are received, they are not included in the
packet loss calculation, although the round trip time of
these packets is used in calculating the round-trip time
statistics. When the specified number of packets have
been sent (and received) or if the program is terminated
with a SIGINT, a brief summary is displayed, showing the
number of packets sent and received, and the minimum, maximum,
mean, and standard deviation of the round-trip
This program is intended for use in network testing, measurement
and management. Because of the load it can impose
on the network, it is unwise to use ping6 during normal
operations or from automated scripts.
na_netstat(1) na_ping(1) na_routed(1) na_traceroute(1)
There have been many discussions on why we separate ping6
and ping. Some people have argued that it would be more
convenient to unify the ping command for both IPv4 and
From a developer's point of view: Since the underlying API
is totally different between IPv4 and IPv6, we would end
up having two types of code base. There would actually be
less benefit to unify the two commands into a single command
from the developer's standpoint.
From an operator's point of view: Unlike ordinary network
applications like remote login tools, we are usually aware
of address family when using network management tools. We
do not just want to know the reachability of the host, but
want to know the reachability of the host via a particular
network protocol such as IPv6. Thus, even if we had a
unified ping command for both IPv4 and IPv6, we would usually
type a -6 or -4 option (or something like those) to
specify the particular address family. This essentially
means that we have two different commands.
Table of Contents