[src/trunk]: src/sbin ping for IPv6. try

[itojun <itojun%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/8e006ba8b242
branches:  trunk
changeset: 474218:8e006ba8b242
user:      itojun <itojun%NetBSD.org@localhost>
date:      Thu Jul 01 19:59:59 1999 +0000

description:
ping for IPv6.  try
        ping6 ::1
on you node.

diffstat:

 sbin/Makefile       |     5 +-
 sbin/ping6/Makefile |    18 +
 sbin/ping6/ping6.8  |   314 ++++++++++
 sbin/ping6/ping6.c  |  1507 +++++++++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 1843 insertions(+), 1 deletions(-)

diffs (truncated from 1868 to 300 lines):

diff -r 5aeb804ef771 -r 8e006ba8b242 sbin/Makefile
--- a/sbin/Makefile     Thu Jul 01 19:42:12 1999 +0000
+++ b/sbin/Makefile     Thu Jul 01 19:59:59 1999 +0000
@@ -1,4 +1,4 @@
-#      $NetBSD: Makefile,v 1.57 1999/05/06 16:05:26 christos Exp $
+#      $NetBSD: Makefile,v 1.58 1999/07/01 19:59:59 itojun Exp $
 #      @(#)Makefile    8.5 (Berkeley) 3/31/94
 
 # Not ported: XNSrouted enpload scsiformat startslip
@@ -28,4 +28,7 @@
 SUBDIR+= mount_umap
 SUBDIR+= mount_union
 
+# IPv6
+SUBDIR+= ping6
+
 .include <bsd.subdir.mk>
diff -r 5aeb804ef771 -r 8e006ba8b242 sbin/ping6/Makefile
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/sbin/ping6/Makefile       Thu Jul 01 19:59:59 1999 +0000
@@ -0,0 +1,18 @@
+# $NetBSD: Makefile,v 1.1 1999/07/01 19:59:59 itojun Exp $
+
+PROG=  ping6
+MAN=   ping6.8
+
+BINOWN  = root
+BINGRP  = bin
+BINMODE = 4555
+
+CFLAGS+= -DINET6
+#CFLAGS+= -DIPSEC
+#LDADD+=       -L${.OBJDIR}/../libipsec -L${.OBJDIR}/../libipsec/obj \
+#      -L/usr/local/v6/lib -lipsec
+#DPADD+= ${.OBJDIR}/../libipsec/libipsec.a \
+#      ${.OBJDIR}/../libipsec/obj/libipsec.a \
+#      /usr/local/v6/lib/libipsec.a
+
+.include <bsd.prog.mk>
diff -r 5aeb804ef771 -r 8e006ba8b242 sbin/ping6/ping6.8
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/sbin/ping6/ping6.8        Thu Jul 01 19:59:59 1999 +0000
@@ -0,0 +1,314 @@
+.\" 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.
+.\"
+.\"     $Id: ping6.8,v 1.1 1999/07/01 20:00:00 itojun Exp $
+.\"
+.Dd May 17, 1998
+.Dt PING6 8
+.Os
+.Sh NAME
+.Nm ping6
+.Nd send
+.Tn ICMPv6 ECHO_REQUEST
+packets to network hosts
+.Sh SYNOPSIS
+.Nm
+.Op Fl AdEfnqRrvw
+.Op Fl a Ar addrtype
+.Op Fl b Ar bufsiz
+.Op Fl c Ar count
+.Op Fl h Ar hoplimit
+.Op Fl I Ar interface
+.Op Fl i Ar wait
+.Op Fl l Ar preload
+.Op Fl p Ar pattern
+.Op Fl s Ar packetsize
+.Ar host
+.Sh DESCRIPTION
+.Bl -tag -width Ds
+.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 charaters.
+.Bl -tag -width Ds -compact
+.It Ic a
+requires all the responder's unicast addresses. If the charater is ommited,
+only those addresses which belong to the interface which has the
+responder's address are required.
+.It Ic g
+requires responder's global-scope addresses.
+.It Ic s
+requires responder's site-local addresses.
+.It Ic l
+requires responder's link-local addresses.
+.El
+.It Fl b Ar bufsiz
+Set socket buffer size.
+.It Fl c Ar count
+Stop after sending
+.Pq and receiving
+.Ar count
+.Tn ECHO_RESPONSE
+packets.
+.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 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 ping
+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 n
+Numeric output only.
+No attempt will be made to lookup symbolic names for host addresses.
+.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.
+.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.
+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 
+.Po
+e.g., after the interface was dropped by
+.Xr routed 8
+.Pc .
+.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.
+.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 FQDN query, rather than echo-request.
+.It Fl W
+Same as
+.Fl w.
+This option was remained for backward compatibility.
+.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
+.Pq 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, maximum, mean, and standard deviation of
+the round-trip times.
+.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
+.\" .Pq 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
+.\" .Pq 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
+.Nm Ping6
+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
+.Pq 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 ping
+packet's path