mirror of
https://git.rtems.org/rtems-libbsd/
synced 2025-06-30 04:08:00 +08:00
commands ping/ping6: Add initial ports of FreeBSD ping and pin6 ports
These compile but need to have an RTEMS specific main and use the reentrant getopt.
This commit is contained in:
Joel Sherrill
parent
b4cf93e3ad
commit
1f877f9d52
@ -66,8 +66,7 @@ C_FILES += lib/libc/net/map_v4v6.c
|
|||||||
C_FILES += lib/libc/net/rcmd.c
|
C_FILES += lib/libc/net/rcmd.c
|
||||||
C_FILES += lib/libc/net/recv.c
|
C_FILES += lib/libc/net/recv.c
|
||||||
C_FILES += lib/libc/net/send.c
|
C_FILES += lib/libc/net/send.c
|
||||||
# iovec redefined between RTEMS and FreeBSD
|
C_FILES += lib/libc/resolv/herror.c
|
||||||
# C_FILES += lib/libc/resolv/herror.c
|
|
||||||
C_FILES += lib/libc/resolv/res_comp.c
|
C_FILES += lib/libc/resolv/res_comp.c
|
||||||
C_FILES += lib/libc/resolv/res_data.c
|
C_FILES += lib/libc/resolv/res_data.c
|
||||||
C_FILES += lib/libc/resolv/res_debug.c
|
C_FILES += lib/libc/resolv/res_debug.c
|
||||||
@ -86,6 +85,10 @@ C_FILES += lib/libc/string/strsep.c
|
|||||||
C_FILES += rtems/rtems-net-setup.c
|
C_FILES += rtems/rtems-net-setup.c
|
||||||
C_FILES += rtems/syslog.c
|
C_FILES += rtems/syslog.c
|
||||||
|
|
||||||
|
# ping command sources
|
||||||
|
C_FILES += commands/sbin/ping/ping.c
|
||||||
|
C_FILES += commands/sbin/ping6/ping6.c
|
||||||
|
|
||||||
C_O_FILES = $(C_FILES:%.c=%.o)
|
C_O_FILES = $(C_FILES:%.c=%.o)
|
||||||
C_D_FILES = $(C_FILES:%.c=%.d)
|
C_D_FILES = $(C_FILES:%.c=%.d)
|
||||||
|
|
||||||
|
|||||||
554
freebsd-userspace/commands/sbin/ping/ping.8
Normal file
554
freebsd-userspace/commands/sbin/ping/ping.8
Normal file
@ -0,0 +1,554 @@
|
|||||||
|
.\" Copyright (c) 1985, 1991, 1993
|
||||||
|
.\" The Regents of the University of California. All rights reserved.
|
||||||
|
.\"
|
||||||
|
.\" Redistribution and use in source and binary forms, with or without
|
||||||
|
.\" modification, are permitted provided that the following conditions
|
||||||
|
.\" are met:
|
||||||
|
.\" 1. Redistributions of source code must retain the above copyright
|
||||||
|
.\" notice, this list of conditions and the following disclaimer.
|
||||||
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
||||||
|
.\" notice, this list of conditions and the following disclaimer in the
|
||||||
|
.\" documentation and/or other materials provided with the distribution.
|
||||||
|
.\" 4. Neither the name of the University nor the names of its contributors
|
||||||
|
.\" may be used to endorse or promote products derived from this software
|
||||||
|
.\" without specific prior written permission.
|
||||||
|
.\"
|
||||||
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
||||||
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
||||||
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
||||||
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
||||||
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
||||||
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
||||||
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
||||||
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
||||||
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
||||||
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||||
|
.\" SUCH DAMAGE.
|
||||||
|
.\"
|
||||||
|
.\" @(#)ping.8 8.2 (Berkeley) 12/11/93
|
||||||
|
.\" $FreeBSD$
|
||||||
|
.\"
|
||||||
|
.Dd April 4, 2006
|
||||||
|
.Dt PING 8
|
||||||
|
.Os
|
||||||
|
.Sh NAME
|
||||||
|
.Nm ping
|
||||||
|
.Nd send
|
||||||
|
.Tn ICMP ECHO_REQUEST
|
||||||
|
packets to network hosts
|
||||||
|
.Sh SYNOPSIS
|
||||||
|
.Nm
|
||||||
|
.Op Fl AaDdfnoQqRrv
|
||||||
|
.Op Fl c Ar count
|
||||||
|
.Op Fl G Ar sweepmaxsize
|
||||||
|
.Op Fl g Ar sweepminsize
|
||||||
|
.Op Fl h Ar sweepincrsize
|
||||||
|
.Op Fl i Ar wait
|
||||||
|
.Op Fl l Ar preload
|
||||||
|
.Op Fl M Cm mask | time
|
||||||
|
.Op Fl m Ar ttl
|
||||||
|
.Op Fl P Ar policy
|
||||||
|
.Op Fl p Ar pattern
|
||||||
|
.Op Fl S Ar src_addr
|
||||||
|
.Op Fl s Ar packetsize
|
||||||
|
.Op Fl t Ar timeout
|
||||||
|
.Op Fl W Ar waittime
|
||||||
|
.Op Fl z Ar tos
|
||||||
|
.Ar host
|
||||||
|
.Nm
|
||||||
|
.Op Fl AaDdfLnoQqRrv
|
||||||
|
.Op Fl c Ar count
|
||||||
|
.Op Fl I Ar iface
|
||||||
|
.Op Fl i Ar wait
|
||||||
|
.Op Fl l Ar preload
|
||||||
|
.Op Fl M Cm mask | time
|
||||||
|
.Op Fl m Ar ttl
|
||||||
|
.Op Fl P Ar policy
|
||||||
|
.Op Fl p Ar pattern
|
||||||
|
.Op Fl S Ar src_addr
|
||||||
|
.Op Fl s Ar packetsize
|
||||||
|
.Op Fl T Ar ttl
|
||||||
|
.Op Fl t Ar timeout
|
||||||
|
.Op Fl W Ar waittime
|
||||||
|
.Op Fl z Ar tos
|
||||||
|
.Ar mcast-group
|
||||||
|
.Sh DESCRIPTION
|
||||||
|
The
|
||||||
|
.Nm
|
||||||
|
utility uses the
|
||||||
|
.Tn ICMP
|
||||||
|
.No protocol Ap s mandatory
|
||||||
|
.Tn ECHO_REQUEST
|
||||||
|
datagram to elicit an
|
||||||
|
.Tn ICMP ECHO_RESPONSE
|
||||||
|
from a host or gateway.
|
||||||
|
.Tn ECHO_REQUEST
|
||||||
|
datagrams
|
||||||
|
.Pq Dq pings
|
||||||
|
have an IP and
|
||||||
|
.Tn ICMP
|
||||||
|
header, followed by a
|
||||||
|
.Dq struct timeval
|
||||||
|
and then an arbitrary number of
|
||||||
|
.Dq pad
|
||||||
|
bytes used to fill out the packet.
|
||||||
|
The options are as follows:
|
||||||
|
.Bl -tag -width indent
|
||||||
|
.It Fl A
|
||||||
|
Audible.
|
||||||
|
Output a bell
|
||||||
|
.Tn ( ASCII
|
||||||
|
0x07)
|
||||||
|
character when no packet is received before the next packet
|
||||||
|
is transmitted.
|
||||||
|
To cater for round-trip times that are longer than the interval
|
||||||
|
between transmissions, further missing packets cause a bell only
|
||||||
|
if the maximum number of unreceived packets has increased.
|
||||||
|
.It Fl a
|
||||||
|
Audible.
|
||||||
|
Include a bell
|
||||||
|
.Tn ( ASCII
|
||||||
|
0x07)
|
||||||
|
character in the output when any packet is received.
|
||||||
|
This option is ignored
|
||||||
|
if other format options are present.
|
||||||
|
.It Fl c Ar count
|
||||||
|
Stop after sending
|
||||||
|
(and receiving)
|
||||||
|
.Ar count
|
||||||
|
.Tn ECHO_RESPONSE
|
||||||
|
packets.
|
||||||
|
If this option is not specified,
|
||||||
|
.Nm
|
||||||
|
will operate until interrupted.
|
||||||
|
If this option is specified in conjunction with ping sweeps,
|
||||||
|
each sweep will consist of
|
||||||
|
.Ar count
|
||||||
|
packets.
|
||||||
|
.It Fl D
|
||||||
|
Set the Don't Fragment bit.
|
||||||
|
.It Fl d
|
||||||
|
Set the
|
||||||
|
.Dv SO_DEBUG
|
||||||
|
option on the socket being used.
|
||||||
|
.It Fl f
|
||||||
|
Flood ping.
|
||||||
|
Outputs packets as fast as they come back or one hundred times per second,
|
||||||
|
whichever is more.
|
||||||
|
For every
|
||||||
|
.Tn ECHO_REQUEST
|
||||||
|
sent a period
|
||||||
|
.Dq .\&
|
||||||
|
is printed, while for every
|
||||||
|
.Tn ECHO_REPLY
|
||||||
|
received a backspace is printed.
|
||||||
|
This provides a rapid display of how many packets are being dropped.
|
||||||
|
Only the super-user may use this option.
|
||||||
|
.Bf -emphasis
|
||||||
|
This can be very hard on a network and should be used with caution.
|
||||||
|
.Ef
|
||||||
|
.It Fl G Ar sweepmaxsize
|
||||||
|
Specify the maximum size of
|
||||||
|
.Tn ICMP
|
||||||
|
payload when sending sweeping pings.
|
||||||
|
This option is required for ping sweeps.
|
||||||
|
.It Fl g Ar sweepminsize
|
||||||
|
Specify the size of
|
||||||
|
.Tn ICMP
|
||||||
|
payload to start with when sending sweeping pings.
|
||||||
|
The default value is 0.
|
||||||
|
.It Fl h Ar sweepincrsize
|
||||||
|
Specify the number of bytes to increment the size of
|
||||||
|
.Tn ICMP
|
||||||
|
payload after
|
||||||
|
each sweep when sending sweeping pings.
|
||||||
|
The default value is 1.
|
||||||
|
.It Fl I Ar iface
|
||||||
|
Source multicast packets with the given interface address.
|
||||||
|
This flag only applies if the ping destination is a multicast address.
|
||||||
|
.It Fl i Ar wait
|
||||||
|
Wait
|
||||||
|
.Ar wait
|
||||||
|
seconds
|
||||||
|
.Em between sending each packet .
|
||||||
|
The default is to wait for one second between each packet.
|
||||||
|
The wait time may be fractional, but only the super-user may specify
|
||||||
|
values less than 1 second.
|
||||||
|
This option is incompatible with the
|
||||||
|
.Fl f
|
||||||
|
option.
|
||||||
|
.It Fl L
|
||||||
|
Suppress loopback of multicast packets.
|
||||||
|
This flag only applies if the ping destination is a multicast address.
|
||||||
|
.It Fl l Ar preload
|
||||||
|
If
|
||||||
|
.Ar preload
|
||||||
|
is specified,
|
||||||
|
.Nm
|
||||||
|
sends that many packets as fast as possible before falling into its normal
|
||||||
|
mode of behavior.
|
||||||
|
Only the super-user may use this option.
|
||||||
|
.It Fl M Cm mask | time
|
||||||
|
Use
|
||||||
|
.Dv ICMP_MASKREQ
|
||||||
|
or
|
||||||
|
.Dv ICMP_TSTAMP
|
||||||
|
instead of
|
||||||
|
.Dv ICMP_ECHO .
|
||||||
|
For
|
||||||
|
.Cm mask ,
|
||||||
|
print the netmask of the remote machine.
|
||||||
|
Set the
|
||||||
|
.Va net.inet.icmp.maskrepl
|
||||||
|
MIB variable to enable
|
||||||
|
.Dv ICMP_MASKREPLY .
|
||||||
|
For
|
||||||
|
.Cm time ,
|
||||||
|
print the origination, reception and transmission timestamps.
|
||||||
|
.It Fl m Ar ttl
|
||||||
|
Set the IP Time To Live for outgoing packets.
|
||||||
|
If not specified, the kernel uses the value of the
|
||||||
|
.Va net.inet.ip.ttl
|
||||||
|
MIB variable.
|
||||||
|
.It Fl n
|
||||||
|
Numeric output only.
|
||||||
|
No attempt will be made to lookup symbolic names for host addresses.
|
||||||
|
.It Fl o
|
||||||
|
Exit successfully after receiving one reply packet.
|
||||||
|
.It Fl P Ar policy
|
||||||
|
.Ar policy
|
||||||
|
specifies IPsec policy for the ping session.
|
||||||
|
For details please refer to
|
||||||
|
.Xr ipsec 4
|
||||||
|
and
|
||||||
|
.Xr ipsec_set_policy 3 .
|
||||||
|
.It Fl p Ar pattern
|
||||||
|
You may specify up to 16
|
||||||
|
.Dq pad
|
||||||
|
bytes to fill out the packet you send.
|
||||||
|
This is useful for diagnosing data-dependent problems in a network.
|
||||||
|
For example,
|
||||||
|
.Dq Li \-p ff
|
||||||
|
will cause the sent packet to be filled with all
|
||||||
|
ones.
|
||||||
|
.It Fl Q
|
||||||
|
Somewhat quiet output.
|
||||||
|
.No Don Ap t
|
||||||
|
display ICMP error messages that are in response to our query messages.
|
||||||
|
Originally, the
|
||||||
|
.Fl v
|
||||||
|
flag was required to display such errors, but
|
||||||
|
.Fl v
|
||||||
|
displays all ICMP error messages.
|
||||||
|
On a busy machine, this output can be overbearing.
|
||||||
|
Without the
|
||||||
|
.Fl Q
|
||||||
|
flag,
|
||||||
|
.Nm
|
||||||
|
prints out any ICMP error messages caused by its own ECHO_REQUEST
|
||||||
|
messages.
|
||||||
|
.It Fl q
|
||||||
|
Quiet output.
|
||||||
|
Nothing is displayed except the summary lines at startup time and
|
||||||
|
when finished.
|
||||||
|
.It Fl R
|
||||||
|
Record route.
|
||||||
|
Includes the
|
||||||
|
.Tn RECORD_ROUTE
|
||||||
|
option in the
|
||||||
|
.Tn ECHO_REQUEST
|
||||||
|
packet and displays
|
||||||
|
the route buffer on returned packets.
|
||||||
|
Note that the IP header is only large enough for nine such routes;
|
||||||
|
the
|
||||||
|
.Xr traceroute 8
|
||||||
|
command is usually better at determining the route packets take to a
|
||||||
|
particular destination.
|
||||||
|
If more routes come back than should, such as due to an illegal spoofed
|
||||||
|
packet, ping will print the route list and then truncate it at the correct
|
||||||
|
spot.
|
||||||
|
Many hosts ignore or discard the
|
||||||
|
.Tn RECORD_ROUTE
|
||||||
|
option.
|
||||||
|
.It Fl r
|
||||||
|
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.
|
||||||
|
This option can be used to ping a local host through an interface
|
||||||
|
that has no route through it
|
||||||
|
(e.g., after the interface was dropped by
|
||||||
|
.Xr routed 8 ) .
|
||||||
|
.It Fl S Ar src_addr
|
||||||
|
Use the following IP address as the source address in outgoing packets.
|
||||||
|
On hosts with more than one IP address, this option can be used to
|
||||||
|
force the source address to be something other than the IP address
|
||||||
|
of the interface the probe packet is sent on.
|
||||||
|
If the IP address
|
||||||
|
is not one of this machine's interface addresses, an error is
|
||||||
|
returned and nothing is sent.
|
||||||
|
.It Fl s Ar packetsize
|
||||||
|
Specify the number of data bytes to be sent.
|
||||||
|
The default is 56, which translates into 64
|
||||||
|
.Tn ICMP
|
||||||
|
data bytes when combined
|
||||||
|
with the 8 bytes of
|
||||||
|
.Tn ICMP
|
||||||
|
header data.
|
||||||
|
Only the super-user may specify values more than default.
|
||||||
|
This option cannot be used with ping sweeps.
|
||||||
|
.It Fl T Ar ttl
|
||||||
|
Set the IP Time To Live for multicasted packets.
|
||||||
|
This flag only applies if the ping destination is a multicast address.
|
||||||
|
.It Fl t Ar timeout
|
||||||
|
Specify a timeout, in seconds, before ping exits regardless of how
|
||||||
|
many packets have been received.
|
||||||
|
.It Fl v
|
||||||
|
Verbose output.
|
||||||
|
.Tn ICMP
|
||||||
|
packets other than
|
||||||
|
.Tn ECHO_RESPONSE
|
||||||
|
that are received are listed.
|
||||||
|
.It Fl W Ar waittime
|
||||||
|
Time in milliseconds to wait for a reply for each packet sent.
|
||||||
|
If a reply arrives later, the packet is not printed as replied, but
|
||||||
|
considered as replied when calculating statistics.
|
||||||
|
.It Fl z Ar tos
|
||||||
|
Use the specified type of service.
|
||||||
|
.El
|
||||||
|
.Pp
|
||||||
|
When using
|
||||||
|
.Nm
|
||||||
|
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
|
||||||
|
.Dq 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
|
||||||
|
.Dv SIGINT ,
|
||||||
|
a brief summary is displayed, showing the number of packets sent and
|
||||||
|
received, and the minimum, mean, maximum, and standard deviation of
|
||||||
|
the round-trip times.
|
||||||
|
.Pp
|
||||||
|
If
|
||||||
|
.Nm
|
||||||
|
receives a
|
||||||
|
.Dv SIGINFO
|
||||||
|
(see the
|
||||||
|
.Cm status
|
||||||
|
argument for
|
||||||
|
.Xr stty 1 )
|
||||||
|
signal, the current number of packets sent and received, and the
|
||||||
|
minimum, mean, and maximum of the round-trip times will be written to
|
||||||
|
the standard error output.
|
||||||
|
.Pp
|
||||||
|
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
|
||||||
|
.Nm
|
||||||
|
during normal operations or from automated scripts.
|
||||||
|
.Sh ICMP PACKET DETAILS
|
||||||
|
An IP header without options is 20 bytes.
|
||||||
|
An
|
||||||
|
.Tn ICMP
|
||||||
|
.Tn ECHO_REQUEST
|
||||||
|
packet contains an additional 8 bytes worth of
|
||||||
|
.Tn ICMP
|
||||||
|
header followed by an arbitrary amount of data.
|
||||||
|
When a
|
||||||
|
.Ar packetsize
|
||||||
|
is given, this indicated the size of this extra piece of data
|
||||||
|
(the default is 56).
|
||||||
|
Thus the amount of data received inside of an IP packet of type
|
||||||
|
.Tn ICMP
|
||||||
|
.Tn ECHO_REPLY
|
||||||
|
will always be 8 bytes more than the requested data space
|
||||||
|
(the
|
||||||
|
.Tn ICMP
|
||||||
|
header).
|
||||||
|
.Pp
|
||||||
|
If the data space is at least eight bytes large,
|
||||||
|
.Nm
|
||||||
|
uses the first eight bytes of this space to include a timestamp which
|
||||||
|
it uses in the computation of round trip times.
|
||||||
|
If less than eight bytes of pad are specified, no round trip times are
|
||||||
|
given.
|
||||||
|
.Sh DUPLICATE AND DAMAGED PACKETS
|
||||||
|
The
|
||||||
|
.Nm
|
||||||
|
utility will report duplicate and damaged packets.
|
||||||
|
Duplicate packets should never occur when pinging a unicast address,
|
||||||
|
and seem to be caused by
|
||||||
|
inappropriate link-level retransmissions.
|
||||||
|
Duplicates may occur in many situations and are rarely
|
||||||
|
(if ever)
|
||||||
|
a good sign, although the presence of low levels of duplicates may not
|
||||||
|
always be cause for alarm.
|
||||||
|
Duplicates are expected when pinging a broadcast or multicast address,
|
||||||
|
since they are not really duplicates but replies from different hosts
|
||||||
|
to the same request.
|
||||||
|
.Pp
|
||||||
|
Damaged packets are obviously serious cause for alarm and often
|
||||||
|
indicate broken hardware somewhere in the
|
||||||
|
.Nm
|
||||||
|
packet's path (in the network or in the hosts).
|
||||||
|
.Sh TRYING DIFFERENT DATA PATTERNS
|
||||||
|
The
|
||||||
|
(inter)network
|
||||||
|
layer should never treat packets differently depending on the data
|
||||||
|
contained in the data portion.
|
||||||
|
Unfortunately, data-dependent problems have been known to sneak into
|
||||||
|
networks and remain undetected for long periods of time.
|
||||||
|
In many cases the particular pattern that will have problems is something
|
||||||
|
that does not have sufficient
|
||||||
|
.Dq transitions ,
|
||||||
|
such as all ones or all zeros, or a pattern right at the edge, such as
|
||||||
|
almost all zeros.
|
||||||
|
It is not
|
||||||
|
necessarily enough to specify a data pattern of all zeros (for example)
|
||||||
|
on the command line because the pattern that is of interest is
|
||||||
|
at the data link level, and the relationship between what you type and
|
||||||
|
what the controllers transmit can be complicated.
|
||||||
|
.Pp
|
||||||
|
This means that if you have a data-dependent problem you will probably
|
||||||
|
have to do a lot of testing to find it.
|
||||||
|
If you are lucky, you may manage to find a file that either
|
||||||
|
cannot
|
||||||
|
be sent across your network or that takes much longer to transfer than
|
||||||
|
other similar length files.
|
||||||
|
You can then examine this file for repeated patterns that you can test
|
||||||
|
using the
|
||||||
|
.Fl p
|
||||||
|
option of
|
||||||
|
.Nm .
|
||||||
|
.Sh TTL DETAILS
|
||||||
|
The
|
||||||
|
.Tn TTL
|
||||||
|
value of an IP packet represents the maximum number of IP routers
|
||||||
|
that the packet can go through before being thrown away.
|
||||||
|
In current practice you can expect each router in the Internet to decrement
|
||||||
|
the
|
||||||
|
.Tn TTL
|
||||||
|
field by exactly one.
|
||||||
|
.Pp
|
||||||
|
The
|
||||||
|
.Tn TCP/IP
|
||||||
|
specification recommends setting the
|
||||||
|
.Tn TTL
|
||||||
|
field for
|
||||||
|
.Tn IP
|
||||||
|
packets to 64, but many systems use smaller values
|
||||||
|
.No ( Bx 4.3
|
||||||
|
uses 30,
|
||||||
|
.Bx 4.2
|
||||||
|
used 15).
|
||||||
|
.Pp
|
||||||
|
The maximum possible value of this field is 255, and most
|
||||||
|
.Ux
|
||||||
|
systems set
|
||||||
|
the
|
||||||
|
.Tn TTL
|
||||||
|
field of
|
||||||
|
.Tn ICMP ECHO_REQUEST
|
||||||
|
packets to 255.
|
||||||
|
This is why you will find you can
|
||||||
|
.Dq ping
|
||||||
|
some hosts, but not reach them with
|
||||||
|
.Xr telnet 1
|
||||||
|
or
|
||||||
|
.Xr ftp 1 .
|
||||||
|
.Pp
|
||||||
|
In normal operation
|
||||||
|
.Nm
|
||||||
|
prints the ttl value from the packet it receives.
|
||||||
|
When a remote system receives a ping packet, it can do one of three things
|
||||||
|
with the
|
||||||
|
.Tn TTL
|
||||||
|
field in its response:
|
||||||
|
.Bl -bullet
|
||||||
|
.It
|
||||||
|
Not change it; this is what
|
||||||
|
.Bx
|
||||||
|
systems did before the
|
||||||
|
.Bx 4.3 tahoe
|
||||||
|
release.
|
||||||
|
In this case the
|
||||||
|
.Tn TTL
|
||||||
|
value in the received packet will be 255 minus the
|
||||||
|
number of routers in the round-trip path.
|
||||||
|
.It
|
||||||
|
Set it to 255; this is what current
|
||||||
|
.Bx
|
||||||
|
systems do.
|
||||||
|
In this case the
|
||||||
|
.Tn TTL
|
||||||
|
value in the received packet will be 255 minus the
|
||||||
|
number of routers in the path
|
||||||
|
.Em from
|
||||||
|
the remote system
|
||||||
|
.Em to
|
||||||
|
the
|
||||||
|
.Nm Ns Em ing
|
||||||
|
host.
|
||||||
|
.It
|
||||||
|
Set it to some other value.
|
||||||
|
Some machines use the same value for
|
||||||
|
.Tn ICMP
|
||||||
|
packets that they use for
|
||||||
|
.Tn TCP
|
||||||
|
packets, for example either 30 or 60.
|
||||||
|
Others may use completely wild values.
|
||||||
|
.El
|
||||||
|
.Sh EXIT STATUS
|
||||||
|
The
|
||||||
|
.Nm
|
||||||
|
utility exits with one of the following values:
|
||||||
|
.Bl -tag -width indent
|
||||||
|
.It 0
|
||||||
|
At least one response was heard from the specified
|
||||||
|
.Ar host .
|
||||||
|
.It 2
|
||||||
|
The transmission was successful but no responses were received.
|
||||||
|
.It any other value
|
||||||
|
An error occurred.
|
||||||
|
These values are defined in
|
||||||
|
.In sysexits.h .
|
||||||
|
.El
|
||||||
|
.Sh SEE ALSO
|
||||||
|
.Xr netstat 1 ,
|
||||||
|
.Xr ifconfig 8 ,
|
||||||
|
.Xr routed 8 ,
|
||||||
|
.Xr traceroute 8
|
||||||
|
.Sh HISTORY
|
||||||
|
The
|
||||||
|
.Nm
|
||||||
|
utility appeared in
|
||||||
|
.Bx 4.3 .
|
||||||
|
.Sh AUTHORS
|
||||||
|
The original
|
||||||
|
.Nm
|
||||||
|
utility was written by
|
||||||
|
.An Mike Muuss
|
||||||
|
while at the US Army Ballistics
|
||||||
|
Research Laboratory.
|
||||||
|
.Sh BUGS
|
||||||
|
Many Hosts and Gateways ignore the
|
||||||
|
.Tn RECORD_ROUTE
|
||||||
|
option.
|
||||||
|
.Pp
|
||||||
|
The maximum IP header length is too small for options like
|
||||||
|
.Tn RECORD_ROUTE
|
||||||
|
to be completely useful.
|
||||||
|
.No There Ap s
|
||||||
|
not much that can be done about this, however.
|
||||||
|
.Pp
|
||||||
|
Flood pinging is not recommended in general, and flood pinging the
|
||||||
|
broadcast address should only be done under very controlled conditions.
|
||||||
|
.Pp
|
||||||
|
The
|
||||||
|
.Fl v
|
||||||
|
option is not worth much on busy hosts.
|
||||||
1732
freebsd-userspace/commands/sbin/ping/ping.c
Normal file
1732
freebsd-userspace/commands/sbin/ping/ping.c
Normal file
File diff suppressed because it is too large
Load Diff
532
freebsd-userspace/commands/sbin/ping6/ping6.8
Normal file
532
freebsd-userspace/commands/sbin/ping6/ping6.8
Normal file
@ -0,0 +1,532 @@
|
|||||||
|
.\" $KAME: ping6.8,v 1.58 2003/06/20 12:00:22 itojun Exp $
|
||||||
|
.\"
|
||||||
|
.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
|
||||||
|
.\" All rights reserved.
|
||||||
|
.\"
|
||||||
|
.\" Redistribution and use in source and binary forms, with or without
|
||||||
|
.\" modification, are permitted provided that the following conditions
|
||||||
|
.\" are met:
|
||||||
|
.\" 1. Redistributions of source code must retain the above copyright
|
||||||
|
.\" notice, this list of conditions and the following disclaimer.
|
||||||
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
||||||
|
.\" notice, this list of conditions and the following disclaimer in the
|
||||||
|
.\" documentation and/or other materials provided with the distribution.
|
||||||
|
.\" 3. Neither the name of the project nor the names of its contributors
|
||||||
|
.\" may be used to endorse or promote products derived from this software
|
||||||
|
.\" without specific prior written permission.
|
||||||
|
.\"
|
||||||
|
.\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
|
||||||
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
||||||
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
||||||
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
|
||||||
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
||||||
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
||||||
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
||||||
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
||||||
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
||||||
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||||
|
.\" SUCH DAMAGE.
|
||||||
|
.\"
|
||||||
|
.\" $FreeBSD$
|
||||||
|
.\"
|
||||||
|
.Dd April 20, 2010
|
||||||
|
.Dt PING6 8
|
||||||
|
.Os
|
||||||
|
.Sh NAME
|
||||||
|
.Nm ping6
|
||||||
|
.Nd send
|
||||||
|
.Tn ICMPv6 ECHO_REQUEST
|
||||||
|
packets to network hosts
|
||||||
|
.Sh SYNOPSIS
|
||||||
|
.Nm
|
||||||
|
.\" without ipsec, or new ipsec
|
||||||
|
.Op Fl DdfHmnNoqrRtvwW
|
||||||
|
.\" old ipsec
|
||||||
|
.\" .Op Fl ADdEfmnNqRtvwW
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl a Ar addrtype
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl b Ar bufsiz
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl c Ar count
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl g Ar gateway
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl h Ar hoplimit
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl I Ar interface
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl i Ar wait
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl l Ar preload
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.\" new ipsec
|
||||||
|
.Op Fl P Ar policy
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl p Ar pattern
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl S Ar sourceaddr
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Fl s Ar packetsize
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Op Ar hops ...
|
||||||
|
.Ek
|
||||||
|
.Bk -words
|
||||||
|
.Ar host
|
||||||
|
.Ek
|
||||||
|
.Sh DESCRIPTION
|
||||||
|
The
|
||||||
|
.Nm
|
||||||
|
utility uses the
|
||||||
|
.Tn ICMPv6
|
||||||
|
protocol's mandatory
|
||||||
|
.Tn ICMP6_ECHO_REQUEST
|
||||||
|
datagram to elicit an
|
||||||
|
.Tn ICMP6_ECHO_REPLY
|
||||||
|
from a host or gateway.
|
||||||
|
.Tn ICMP6_ECHO_REQUEST
|
||||||
|
datagrams (``pings'') have an IPv6 header,
|
||||||
|
and
|
||||||
|
.Tn ICMPv6
|
||||||
|
header formatted as documented in RFC2463.
|
||||||
|
The options are as follows:
|
||||||
|
.Bl -tag -width Ds
|
||||||
|
.\" old ipsec
|
||||||
|
.\" .It Fl A
|
||||||
|
.\" Enables transport-mode IPsec authentication header
|
||||||
|
.\" (experimental).
|
||||||
|
.It Fl a Ar addrtype
|
||||||
|
Generate ICMPv6 Node Information Node Addresses query, rather than echo-request.
|
||||||
|
.Ar addrtype
|
||||||
|
must be a string constructed of the following characters.
|
||||||
|
.Bl -tag -width Ds -compact
|
||||||
|
.It Ic a
|
||||||
|
requests unicast addresses from all of the responder's interfaces.
|
||||||
|
If the character is omitted,
|
||||||
|
only those addresses which belong to the interface which has the
|
||||||
|
responder's address are requests.
|
||||||
|
.It Ic c
|
||||||
|
requests responder's IPv4-compatible and IPv4-mapped addresses.
|
||||||
|
.It Ic g
|
||||||
|
requests responder's global-scope addresses.
|
||||||
|
.It Ic s
|
||||||
|
requests responder's site-local addresses.
|
||||||
|
.It Ic l
|
||||||
|
requests responder's link-local addresses.
|
||||||
|
.It Ic A
|
||||||
|
requests responder's anycast addresses.
|
||||||
|
Without this character, the responder will return unicast addresses only.
|
||||||
|
With this character, the responder will return anycast addresses only.
|
||||||
|
Note that the specification does not specify how to get responder's
|
||||||
|
anycast addresses.
|
||||||
|
This is an experimental option.
|
||||||
|
.El
|
||||||
|
.It Fl b Ar bufsiz
|
||||||
|
Set socket buffer size.
|
||||||
|
.It Fl c Ar count
|
||||||
|
Stop after sending
|
||||||
|
(and receiving)
|
||||||
|
.Ar count
|
||||||
|
.Tn ECHO_RESPONSE
|
||||||
|
packets.
|
||||||
|
.It Fl D
|
||||||
|
Disable IPv6 fragmentation.
|
||||||
|
.It Fl d
|
||||||
|
Set the
|
||||||
|
.Dv SO_DEBUG
|
||||||
|
option on the socket being used.
|
||||||
|
.\" .It Fl E
|
||||||
|
.\" Enables transport-mode IPsec encapsulated security payload
|
||||||
|
.\" (experimental).
|
||||||
|
.It Fl f
|
||||||
|
Flood ping.
|
||||||
|
Outputs packets as fast as they come back or one hundred times per second,
|
||||||
|
whichever is more.
|
||||||
|
For every
|
||||||
|
.Tn ECHO_REQUEST
|
||||||
|
sent a period
|
||||||
|
.Dq \&.
|
||||||
|
is printed, while for every
|
||||||
|
.Tn ECHO_REPLY
|
||||||
|
received a backspace is printed.
|
||||||
|
This provides a rapid display of how many packets are being dropped.
|
||||||
|
Only the super-user may use this option.
|
||||||
|
.Bf -emphasis
|
||||||
|
This can be very hard on a network and should be used with caution.
|
||||||
|
.Ef
|
||||||
|
.It Fl g Ar gateway
|
||||||
|
Specifies to use
|
||||||
|
.Ar gateway
|
||||||
|
as the next hop to the destination.
|
||||||
|
The gateway must be a neighbor of the sending node.
|
||||||
|
.It Fl H
|
||||||
|
Specifies to try reverse-lookup of IPv6 addresses.
|
||||||
|
The
|
||||||
|
.Nm
|
||||||
|
utility does not try reverse-lookup unless the option is specified.
|
||||||
|
.It Fl h Ar hoplimit
|
||||||
|
Set the IPv6 hoplimit.
|
||||||
|
.It Fl I Ar interface
|
||||||
|
Source packets with the given interface address.
|
||||||
|
This flag applies if the ping destination is a multicast address,
|
||||||
|
or link-local/site-local unicast address.
|
||||||
|
.It Fl i Ar wait
|
||||||
|
Wait
|
||||||
|
.Ar wait
|
||||||
|
seconds
|
||||||
|
.Em between sending each packet .
|
||||||
|
The default is to wait for one second between each packet.
|
||||||
|
This option is incompatible with the
|
||||||
|
.Fl f
|
||||||
|
option.
|
||||||
|
.It Fl l Ar preload
|
||||||
|
If
|
||||||
|
.Ar preload
|
||||||
|
is specified,
|
||||||
|
.Nm
|
||||||
|
sends that many packets as fast as possible before falling into its normal
|
||||||
|
mode of behavior.
|
||||||
|
Only the super-user may use this option.
|
||||||
|
.It Fl m
|
||||||
|
By default,
|
||||||
|
.Nm
|
||||||
|
asks the kernel to fragment packets to fit into the minimum IPv6 MTU.
|
||||||
|
The
|
||||||
|
.Fl m
|
||||||
|
option
|
||||||
|
will suppress the behavior in the following two levels:
|
||||||
|
when the option is specified once, the behavior will be disabled for
|
||||||
|
unicast packets.
|
||||||
|
When the option is more than once, it will be disabled for both
|
||||||
|
unicast and multicast packets.
|
||||||
|
.It Fl n
|
||||||
|
Numeric output only.
|
||||||
|
No attempt will be made to lookup symbolic names from addresses in the reply.
|
||||||
|
.It Fl N
|
||||||
|
Probe node information multicast group
|
||||||
|
.Pq Li ff02::2:xxxx:xxxx .
|
||||||
|
.Ar 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
|
||||||
|
.Ar host ,
|
||||||
|
and will be used as the final destination.
|
||||||
|
Since node information multicast group is a link-local multicast group,
|
||||||
|
outgoing interface needs to be specified by
|
||||||
|
.Fl I
|
||||||
|
option.
|
||||||
|
.It Fl o
|
||||||
|
Exit successfully after receiving one reply packet.
|
||||||
|
.It Fl p Ar pattern
|
||||||
|
You may specify up to 16
|
||||||
|
.Dq pad
|
||||||
|
bytes to fill out the packet you send.
|
||||||
|
This is useful for diagnosing data-dependent problems in a network.
|
||||||
|
For example,
|
||||||
|
.Dq Li \-p ff
|
||||||
|
will cause the sent packet to be filled with all
|
||||||
|
ones.
|
||||||
|
.\" new ipsec
|
||||||
|
.It Fl P Ar policy
|
||||||
|
.Ar policy
|
||||||
|
specifies IPsec policy to be used for the probe.
|
||||||
|
.It Fl q
|
||||||
|
Quiet output.
|
||||||
|
Nothing is displayed except the summary lines at startup time and
|
||||||
|
when finished.
|
||||||
|
.It Fl r
|
||||||
|
Audible.
|
||||||
|
Include a bell
|
||||||
|
.Tn ( ASCII
|
||||||
|
0x07)
|
||||||
|
character in the output when any packet is received.
|
||||||
|
.It Fl R
|
||||||
|
Audible.
|
||||||
|
Output a bell
|
||||||
|
.Tn ( ASCII
|
||||||
|
0x07)
|
||||||
|
character when no packet is received before the next packet
|
||||||
|
is transmitted.
|
||||||
|
To cater for round-trip times that are longer than the interval
|
||||||
|
between transmissions, further missing packets cause a bell only
|
||||||
|
if the maximum number of unreceived packets has increased.
|
||||||
|
.It Fl S Ar sourceaddr
|
||||||
|
Specifies the source address of request packets.
|
||||||
|
The source address must be one of the unicast addresses of the sending node,
|
||||||
|
and must be numeric.
|
||||||
|
.It Fl s Ar packetsize
|
||||||
|
Specifies the number of data bytes to be sent.
|
||||||
|
The default is 56, which translates into 64
|
||||||
|
.Tn ICMP
|
||||||
|
data bytes when combined
|
||||||
|
with the 8 bytes of
|
||||||
|
.Tn ICMP
|
||||||
|
header data.
|
||||||
|
You may need to specify
|
||||||
|
.Fl b
|
||||||
|
as well to extend socket buffer size.
|
||||||
|
.It Fl t
|
||||||
|
Generate ICMPv6 Node Information supported query types query,
|
||||||
|
rather than echo-request.
|
||||||
|
.Fl s
|
||||||
|
has no effect if
|
||||||
|
.Fl t
|
||||||
|
is specified.
|
||||||
|
.It Fl v
|
||||||
|
Verbose output.
|
||||||
|
.Tn ICMP
|
||||||
|
packets other than
|
||||||
|
.Tn ECHO_RESPONSE
|
||||||
|
that are received are listed.
|
||||||
|
.It Fl w
|
||||||
|
Generate ICMPv6 Node Information DNS Name query, rather than echo-request.
|
||||||
|
.Fl s
|
||||||
|
has no effect if
|
||||||
|
.Fl w
|
||||||
|
is specified.
|
||||||
|
.It Fl W
|
||||||
|
Same as
|
||||||
|
.Fl w ,
|
||||||
|
but with old packet format based on 03 draft.
|
||||||
|
This option is present for backward compatibility.
|
||||||
|
.Fl s
|
||||||
|
has no effect if
|
||||||
|
.Fl w
|
||||||
|
is specified.
|
||||||
|
.It Ar hops
|
||||||
|
IPv6 addresses for intermediate nodes,
|
||||||
|
which will be put into type 0 routing header.
|
||||||
|
.It Ar host
|
||||||
|
IPv6 address of the final destination node.
|
||||||
|
.El
|
||||||
|
.Pp
|
||||||
|
When using
|
||||||
|
.Nm
|
||||||
|
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
|
||||||
|
.Dq 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
|
||||||
|
.Dv SIGINT ,
|
||||||
|
a brief summary is displayed, showing the number of packets sent and
|
||||||
|
received, and the minimum, mean, maximum, and standard deviation of
|
||||||
|
the round-trip times.
|
||||||
|
.Pp
|
||||||
|
If
|
||||||
|
.Nm
|
||||||
|
receives a
|
||||||
|
.Dv SIGINFO
|
||||||
|
(see the
|
||||||
|
.Cm status
|
||||||
|
argument for
|
||||||
|
.Xr stty 1 )
|
||||||
|
signal, the current number of packets sent and received, and the
|
||||||
|
minimum, mean, maximum, and standard deviation of the round-trip times
|
||||||
|
will be written to the standard output in the same format as the
|
||||||
|
standard completion message.
|
||||||
|
.Pp
|
||||||
|
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
|
||||||
|
.Nm
|
||||||
|
during normal operations or from automated scripts.
|
||||||
|
.\" .Sh ICMP PACKET DETAILS
|
||||||
|
.\" An IP header without options is 20 bytes.
|
||||||
|
.\" An
|
||||||
|
.\" .Tn ICMP
|
||||||
|
.\" .Tn ECHO_REQUEST
|
||||||
|
.\" packet contains an additional 8 bytes worth of
|
||||||
|
.\" .Tn ICMP
|
||||||
|
.\" header followed by an arbitrary amount of data.
|
||||||
|
.\" When a
|
||||||
|
.\" .Ar packetsize
|
||||||
|
.\" is given, this indicated the size of this extra piece of data
|
||||||
|
.\" (the default is 56).
|
||||||
|
.\" Thus the amount of data received inside of an IP packet of type
|
||||||
|
.\" .Tn ICMP
|
||||||
|
.\" .Tn ECHO_REPLY
|
||||||
|
.\" will always be 8 bytes more than the requested data space
|
||||||
|
.\" (the
|
||||||
|
.\" .Tn ICMP
|
||||||
|
.\" header).
|
||||||
|
.\" .Pp
|
||||||
|
.\" If the data space is at least eight bytes large,
|
||||||
|
.\" .Nm
|
||||||
|
.\" uses the first eight bytes of this space to include a timestamp which
|
||||||
|
.\" it uses in the computation of round trip times.
|
||||||
|
.\" If less than eight bytes of pad are specified, no round trip times are
|
||||||
|
.\" given.
|
||||||
|
.Sh DUPLICATE AND DAMAGED PACKETS
|
||||||
|
The
|
||||||
|
.Nm
|
||||||
|
utility will report duplicate and damaged packets.
|
||||||
|
Duplicate packets should never occur when pinging a unicast address,
|
||||||
|
and seem to be caused by
|
||||||
|
inappropriate link-level retransmissions.
|
||||||
|
Duplicates may occur in many situations and are rarely
|
||||||
|
(if ever)
|
||||||
|
a good sign, although the presence of low levels of duplicates may not
|
||||||
|
always be cause for alarm.
|
||||||
|
Duplicates are expected when pinging a broadcast or multicast address,
|
||||||
|
since they are not really duplicates but replies from different hosts
|
||||||
|
to the same request.
|
||||||
|
.Pp
|
||||||
|
Damaged packets are obviously serious cause for alarm and often
|
||||||
|
indicate broken hardware somewhere in the
|
||||||
|
.Nm
|
||||||
|
packet's path
|
||||||
|
(in the network or in the hosts).
|
||||||
|
.Sh TRYING DIFFERENT DATA PATTERNS
|
||||||
|
The
|
||||||
|
(inter)network
|
||||||
|
layer should never treat packets differently depending on the data
|
||||||
|
contained in the data portion.
|
||||||
|
Unfortunately, data-dependent problems have been known to sneak into
|
||||||
|
networks and remain undetected for long periods of time.
|
||||||
|
In many cases the particular pattern that will have problems is something
|
||||||
|
that does not have sufficient
|
||||||
|
.Dq transitions ,
|
||||||
|
such as all ones or all zeros, or a pattern right at the edge, such as
|
||||||
|
almost all zeros.
|
||||||
|
It is not
|
||||||
|
necessarily enough to specify a data pattern of all zeros (for example)
|
||||||
|
on the command line because the pattern that is of interest is
|
||||||
|
at the data link level, and the relationship between what you type and
|
||||||
|
what the controllers transmit can be complicated.
|
||||||
|
.Pp
|
||||||
|
This means that if you have a data-dependent problem you will probably
|
||||||
|
have to do a lot of testing to find it.
|
||||||
|
If you are lucky, you may manage to find a file that either
|
||||||
|
cannot
|
||||||
|
be sent across your network or that takes much longer to transfer than
|
||||||
|
other similar length files.
|
||||||
|
You can then examine this file for repeated patterns that you can test
|
||||||
|
using the
|
||||||
|
.Fl p
|
||||||
|
option of
|
||||||
|
.Nm .
|
||||||
|
.Sh EXIT STATUS
|
||||||
|
The
|
||||||
|
.Nm
|
||||||
|
utility returns 0 on success (the host is alive),
|
||||||
|
2 if the transmission was successful but no responses were received,
|
||||||
|
any other non-zero value if the arguments are incorrect or
|
||||||
|
another error has occured.
|
||||||
|
.Sh EXAMPLES
|
||||||
|
Normally,
|
||||||
|
.Nm
|
||||||
|
works just like
|
||||||
|
.Xr ping 8
|
||||||
|
would work; the following will send ICMPv6 echo request to
|
||||||
|
.Li dst.foo.com .
|
||||||
|
.Bd -literal -offset indent
|
||||||
|
ping6 -n dst.foo.com
|
||||||
|
.Ed
|
||||||
|
.Pp
|
||||||
|
The following will probe hostnames for all nodes on the network link attached to
|
||||||
|
.Li wi0
|
||||||
|
interface.
|
||||||
|
The address
|
||||||
|
.Li ff02::1
|
||||||
|
is named the link-local all-node multicast address, and the packet would
|
||||||
|
reach every node on the network link.
|
||||||
|
.Bd -literal -offset indent
|
||||||
|
ping6 -w ff02::1%wi0
|
||||||
|
.Ed
|
||||||
|
.Pp
|
||||||
|
The following will probe addresses assigned to the destination node,
|
||||||
|
.Li dst.foo.com .
|
||||||
|
.Bd -literal -offset indent
|
||||||
|
ping6 -a agl dst.foo.com
|
||||||
|
.Ed
|
||||||
|
.Sh SEE ALSO
|
||||||
|
.Xr netstat 1 ,
|
||||||
|
.Xr icmp6 4 ,
|
||||||
|
.Xr inet6 4 ,
|
||||||
|
.Xr ip6 4 ,
|
||||||
|
.Xr ifconfig 8 ,
|
||||||
|
.Xr ping 8 ,
|
||||||
|
.Xr routed 8 ,
|
||||||
|
.Xr traceroute 8 ,
|
||||||
|
.Xr traceroute6 8
|
||||||
|
.Rs
|
||||||
|
.%A A. Conta
|
||||||
|
.%A S. Deering
|
||||||
|
.%T "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification"
|
||||||
|
.%N RFC2463
|
||||||
|
.%D December 1998
|
||||||
|
.Re
|
||||||
|
.Rs
|
||||||
|
.%A Matt Crawford
|
||||||
|
.%T "IPv6 Node Information Queries"
|
||||||
|
.%N draft-ietf-ipngwg-icmp-name-lookups-09.txt
|
||||||
|
.%D May 2002
|
||||||
|
.%O work in progress material
|
||||||
|
.Re
|
||||||
|
.Sh HISTORY
|
||||||
|
The
|
||||||
|
.Xr ping 8
|
||||||
|
utility appeared in
|
||||||
|
.Bx 4.3 .
|
||||||
|
The
|
||||||
|
.Nm
|
||||||
|
utility with IPv6 support first appeared in the WIDE Hydrangea IPv6
|
||||||
|
protocol stack kit.
|
||||||
|
.Pp
|
||||||
|
IPv6 and IPsec support based on the KAME Project
|
||||||
|
.Pq Pa http://www.kame.net/
|
||||||
|
stack was initially integrated into
|
||||||
|
.Fx 4.0 .
|
||||||
|
.Sh BUGS
|
||||||
|
The
|
||||||
|
.Nm
|
||||||
|
utility
|
||||||
|
is intentionally separate from
|
||||||
|
.Xr ping 8 .
|
||||||
|
.Pp
|
||||||
|
There have been many discussions on why we separate
|
||||||
|
.Nm
|
||||||
|
and
|
||||||
|
.Xr ping 8 .
|
||||||
|
Some people argued that it would be more convenient to uniform the
|
||||||
|
ping command for both IPv4 and IPv6.
|
||||||
|
The followings are an answer to the request.
|
||||||
|
.Pp
|
||||||
|
From a developer's point of view:
|
||||||
|
since the underling raw sockets 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 uniform the two commands
|
||||||
|
into a single command from the developer's standpoint.
|
||||||
|
.Pp
|
||||||
|
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 to the host, but want to know the
|
||||||
|
reachability to the host via a particular network protocol such as
|
||||||
|
IPv6.
|
||||||
|
Thus, even if we had a unified
|
||||||
|
.Xr ping 8
|
||||||
|
command for both IPv4 and IPv6, we would usually type a
|
||||||
|
.Fl 6
|
||||||
|
or
|
||||||
|
.Fl 4
|
||||||
|
option (or something like those) to specify the particular address family.
|
||||||
|
This essentially means that we have two different commands.
|
||||||
2817
freebsd-userspace/commands/sbin/ping6/ping6.c
Normal file
2817
freebsd-userspace/commands/sbin/ping6/ping6.c
Normal file
File diff suppressed because it is too large
Load Diff
@ -100,10 +100,12 @@ do
|
|||||||
cp ${src}/${f} ${dest}/${d}
|
cp ${src}/${f} ${dest}/${d}
|
||||||
done <<EOF
|
done <<EOF
|
||||||
include/db.h
|
include/db.h
|
||||||
|
include/err.h
|
||||||
include/ifaddrs.h
|
include/ifaddrs.h
|
||||||
include/netconfig.h
|
include/netconfig.h
|
||||||
include/nsswitch.h
|
include/nsswitch.h
|
||||||
include/resolv.h
|
include/resolv.h
|
||||||
|
include/sysexit.h
|
||||||
include/res_update.h
|
include/res_update.h
|
||||||
include/rpc/auth.h
|
include/rpc/auth.h
|
||||||
include/rpc/auth_unix.h
|
include/rpc/auth_unix.h
|
||||||
@ -243,6 +245,7 @@ net/if_types.h
|
|||||||
net/in.h
|
net/in.h
|
||||||
net/route.h
|
net/route.h
|
||||||
netinet/in.h
|
netinet/in.h
|
||||||
|
netinet/icmp6.h
|
||||||
sys/socket.h
|
sys/socket.h
|
||||||
sys/sysctl.h
|
sys/sysctl.h
|
||||||
EOF
|
EOF
|
||||||
|
|||||||
68
freebsd-userspace/include/err.h
Normal file
68
freebsd-userspace/include/err.h
Normal file
@ -0,0 +1,68 @@
|
|||||||
|
/*-
|
||||||
|
* Copyright (c) 1993
|
||||||
|
* The Regents of the University of California. All rights reserved.
|
||||||
|
*
|
||||||
|
* Redistribution and use in source and binary forms, with or without
|
||||||
|
* modification, are permitted provided that the following conditions
|
||||||
|
* are met:
|
||||||
|
* 1. Redistributions of source code must retain the above copyright
|
||||||
|
* notice, this list of conditions and the following disclaimer.
|
||||||
|
* 2. Redistributions in binary form must reproduce the above copyright
|
||||||
|
* notice, this list of conditions and the following disclaimer in the
|
||||||
|
* documentation and/or other materials provided with the distribution.
|
||||||
|
* 3. All advertising materials mentioning features or use of this software
|
||||||
|
* must display the following acknowledgement:
|
||||||
|
* This product includes software developed by the University of
|
||||||
|
* California, Berkeley and its contributors.
|
||||||
|
* 4. Neither the name of the University nor the names of its contributors
|
||||||
|
* may be used to endorse or promote products derived from this software
|
||||||
|
* without specific prior written permission.
|
||||||
|
*
|
||||||
|
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
||||||
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
||||||
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
||||||
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
||||||
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
||||||
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
||||||
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
||||||
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
||||||
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
||||||
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||||
|
* SUCH DAMAGE.
|
||||||
|
*
|
||||||
|
* @(#)err.h 8.1 (Berkeley) 6/2/93
|
||||||
|
* $FreeBSD$
|
||||||
|
*/
|
||||||
|
|
||||||
|
#ifndef _ERR_H_
|
||||||
|
#define _ERR_H_
|
||||||
|
|
||||||
|
/*
|
||||||
|
* Don't use va_list in the err/warn prototypes. Va_list is typedef'd in two
|
||||||
|
* places (<machine/varargs.h> and <machine/stdarg.h>), so if we include one
|
||||||
|
* of them here we may collide with the utility's includes. It's unreasonable
|
||||||
|
* for utilities to have to include one of them to include err.h, so we get
|
||||||
|
* __va_list from <sys/_types.h> and use it.
|
||||||
|
*/
|
||||||
|
#include <sys/cdefs.h>
|
||||||
|
#include <sys/_types.h>
|
||||||
|
|
||||||
|
__BEGIN_DECLS
|
||||||
|
void err(int, const char *, ...) __dead2 __printf0like(2, 3);
|
||||||
|
void verr(int, const char *, __va_list) __dead2 __printf0like(2, 0);
|
||||||
|
void errc(int, int, const char *, ...) __dead2 __printf0like(3, 4);
|
||||||
|
void verrc(int, int, const char *, __va_list) __dead2
|
||||||
|
__printf0like(3, 0);
|
||||||
|
void errx(int, const char *, ...) __dead2 __printf0like(2, 3);
|
||||||
|
void verrx(int, const char *, __va_list) __dead2 __printf0like(2, 0);
|
||||||
|
void warn(const char *, ...) __printf0like(1, 2);
|
||||||
|
void vwarn(const char *, __va_list) __printf0like(1, 0);
|
||||||
|
void warnc(int, const char *, ...) __printf0like(2, 3);
|
||||||
|
void vwarnc(int, const char *, __va_list) __printf0like(2, 0);
|
||||||
|
void warnx(const char *, ...) __printflike(1, 2);
|
||||||
|
void vwarnx(const char *, __va_list) __printflike(1, 0);
|
||||||
|
void err_set_file(void *);
|
||||||
|
void err_set_exit(void (*)(int));
|
||||||
|
__END_DECLS
|
||||||
|
|
||||||
|
#endif /* !_ERR_H_ */
|
||||||
2
freebsd-userspace/include/netinet/icmp6.h
Normal file
2
freebsd-userspace/include/netinet/icmp6.h
Normal file
@ -0,0 +1,2 @@
|
|||||||
|
#include <freebsd/bsd.h>
|
||||||
|
#include <freebsd/netinet/icmp6.h>
|
||||||
2
freebsd-userspace/include/netinet/ip6.h
Normal file
2
freebsd-userspace/include/netinet/ip6.h
Normal file
@ -0,0 +1,2 @@
|
|||||||
|
#include <freebsd/bsd.h>
|
||||||
|
#include <freebsd/netinet/ip6.h>
|
||||||
118
freebsd-userspace/include/sysexits.h
Normal file
118
freebsd-userspace/include/sysexits.h
Normal file
@ -0,0 +1,118 @@
|
|||||||
|
/*
|
||||||
|
* Copyright (c) 1987, 1993
|
||||||
|
* The Regents of the University of California. All rights reserved.
|
||||||
|
*
|
||||||
|
* Redistribution and use in source and binary forms, with or without
|
||||||
|
* modification, are permitted provided that the following conditions
|
||||||
|
* are met:
|
||||||
|
* 1. Redistributions of source code must retain the above copyright
|
||||||
|
* notice, this list of conditions and the following disclaimer.
|
||||||
|
* 2. Redistributions in binary form must reproduce the above copyright
|
||||||
|
* notice, this list of conditions and the following disclaimer in the
|
||||||
|
* documentation and/or other materials provided with the distribution.
|
||||||
|
* 3. All advertising materials mentioning features or use of this software
|
||||||
|
* must display the following acknowledgement:
|
||||||
|
* This product includes software developed by the University of
|
||||||
|
* California, Berkeley and its contributors.
|
||||||
|
* 4. Neither the name of the University nor the names of its contributors
|
||||||
|
* may be used to endorse or promote products derived from this software
|
||||||
|
* without specific prior written permission.
|
||||||
|
*
|
||||||
|
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
||||||
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
||||||
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
||||||
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
||||||
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
||||||
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
||||||
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
||||||
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
||||||
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
||||||
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||||
|
* SUCH DAMAGE.
|
||||||
|
*
|
||||||
|
* @(#)sysexits.h 8.1 (Berkeley) 6/2/93
|
||||||
|
*/
|
||||||
|
|
||||||
|
#ifndef _SYSEXITS_H_
|
||||||
|
#define _SYSEXITS_H_
|
||||||
|
|
||||||
|
/*
|
||||||
|
* SYSEXITS.H -- Exit status codes for system programs.
|
||||||
|
*
|
||||||
|
* This include file attempts to categorize possible error
|
||||||
|
* exit statuses for system programs, notably delivermail
|
||||||
|
* and the Berkeley network.
|
||||||
|
*
|
||||||
|
* Error numbers begin at EX__BASE to reduce the possibility of
|
||||||
|
* clashing with other exit statuses that random programs may
|
||||||
|
* already return. The meaning of the codes is approximately
|
||||||
|
* as follows:
|
||||||
|
*
|
||||||
|
* EX_USAGE -- The command was used incorrectly, e.g., with
|
||||||
|
* the wrong number of arguments, a bad flag, a bad
|
||||||
|
* syntax in a parameter, or whatever.
|
||||||
|
* EX_DATAERR -- The input data was incorrect in some way.
|
||||||
|
* This should only be used for user's data & not
|
||||||
|
* system files.
|
||||||
|
* EX_NOINPUT -- An input file (not a system file) did not
|
||||||
|
* exist or was not readable. This could also include
|
||||||
|
* errors like "No message" to a mailer (if it cared
|
||||||
|
* to catch it).
|
||||||
|
* EX_NOUSER -- The user specified did not exist. This might
|
||||||
|
* be used for mail addresses or remote logins.
|
||||||
|
* EX_NOHOST -- The host specified did not exist. This is used
|
||||||
|
* in mail addresses or network requests.
|
||||||
|
* EX_UNAVAILABLE -- A service is unavailable. This can occur
|
||||||
|
* if a support program or file does not exist. This
|
||||||
|
* can also be used as a catchall message when something
|
||||||
|
* you wanted to do doesn't work, but you don't know
|
||||||
|
* why.
|
||||||
|
* EX_SOFTWARE -- An internal software error has been detected.
|
||||||
|
* This should be limited to non-operating system related
|
||||||
|
* errors as possible.
|
||||||
|
* EX_OSERR -- An operating system error has been detected.
|
||||||
|
* This is intended to be used for such things as "cannot
|
||||||
|
* fork", "cannot create pipe", or the like. It includes
|
||||||
|
* things like getuid returning a user that does not
|
||||||
|
* exist in the passwd file.
|
||||||
|
* EX_OSFILE -- Some system file (e.g., /etc/passwd, /etc/utmp,
|
||||||
|
* etc.) does not exist, cannot be opened, or has some
|
||||||
|
* sort of error (e.g., syntax error).
|
||||||
|
* EX_CANTCREAT -- A (user specified) output file cannot be
|
||||||
|
* created.
|
||||||
|
* EX_IOERR -- An error occurred while doing I/O on some file.
|
||||||
|
* EX_TEMPFAIL -- temporary failure, indicating something that
|
||||||
|
* is not really an error. In sendmail, this means
|
||||||
|
* that a mailer (e.g.) could not create a connection,
|
||||||
|
* and the request should be reattempted later.
|
||||||
|
* EX_PROTOCOL -- the remote system returned something that
|
||||||
|
* was "not possible" during a protocol exchange.
|
||||||
|
* EX_NOPERM -- You did not have sufficient permission to
|
||||||
|
* perform the operation. This is not intended for
|
||||||
|
* file system problems, which should use NOINPUT or
|
||||||
|
* CANTCREAT, but rather for higher level permissions.
|
||||||
|
*/
|
||||||
|
|
||||||
|
#define EX_OK 0 /* successful termination */
|
||||||
|
|
||||||
|
#define EX__BASE 64 /* base value for error messages */
|
||||||
|
|
||||||
|
#define EX_USAGE 64 /* command line usage error */
|
||||||
|
#define EX_DATAERR 65 /* data format error */
|
||||||
|
#define EX_NOINPUT 66 /* cannot open input */
|
||||||
|
#define EX_NOUSER 67 /* addressee unknown */
|
||||||
|
#define EX_NOHOST 68 /* host name unknown */
|
||||||
|
#define EX_UNAVAILABLE 69 /* service unavailable */
|
||||||
|
#define EX_SOFTWARE 70 /* internal software error */
|
||||||
|
#define EX_OSERR 71 /* system error (e.g., can't fork) */
|
||||||
|
#define EX_OSFILE 72 /* critical OS file missing */
|
||||||
|
#define EX_CANTCREAT 73 /* can't create (user) output file */
|
||||||
|
#define EX_IOERR 74 /* input/output error */
|
||||||
|
#define EX_TEMPFAIL 75 /* temp failure; user is invited to retry */
|
||||||
|
#define EX_PROTOCOL 76 /* remote error in protocol */
|
||||||
|
#define EX_NOPERM 77 /* permission denied */
|
||||||
|
#define EX_CONFIG 78 /* configuration error */
|
||||||
|
|
||||||
|
#define EX__MAX 78 /* maximum listed value */
|
||||||
|
|
||||||
|
#endif /* !_SYSEXITS_H_ */
|
||||||
Loading…
x
Reference in New Issue
Block a user