Import translated manuals from JM CVS Repository.

[linuxjm/jm.git] / manual / netkit / draft / man8 / ping.8

.\" Copyright (c) 1985, 1991 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.
.\"
.\"     from: @(#)ping.8        6.7 (Berkeley) 3/16/91
.\"     $Id: ping.8,v 1.1.1.1 2000/10/19 08:22:16 ysato Exp $
.\"
.\" Japanese version copyright (c) 1999 Tatsuo SEKINE <tsekine@isoternet.org>
.\"     all rights reserved
.\"
.\" Translated on Tue Dec 07 16:28:28 JST 1999
.\"     by Tatsuo SEKINE <tsekine@isoternet.org>
.\" Updated Sun Jan 14 20:51:42 JST 2001
.\"     by Yuichi SATO <sato@complex.eng.hokudai.ac.jp>
.\"
.\"WORD: Time To Live   ¼÷Ì¿»þ´Ö
.\"WORD: round-trip     ±ýÉü
.\"WORD: path   ·ÐÏ©
.\"WORD: Berkeley Unix System   BSD Unix ¥·¥¹¥Æ¥à
.\"
.Dd August 30, 1996
.Dt PING 8
.Os "Linux NetKit (0.17)"
.\"O .Sh NAME
.Sh ̾Á°
.Nm ping
.\"O .Nd send
.\"O .Tn ICMP ECHO_REQUEST
.\"O packets to network hosts
.Nd
.Tn ICMP ECHO_REQUEST
¥Ñ¥±¥Ã¥È¤ò¥Í¥Ã¥È¥ï¡¼¥¯¾å¤Î¥Û¥¹¥È¤ËÁ÷¤ë
.\"O .Sh SYNOPSIS
.Sh ½ñ¼°
.\"O .Nm ping
.\"O .Op Fl dfnqrvR
.\"O .Op Fl c Ar count
.\"O .Op Fl i Ar wait
.\"O .Op Fl l Ar preload
.\"O .Op Fl p Ar pattern
.\"O .Op Fl s Ar packetsize
.\"O .Op Fl w Ar waittime
.Nm ping
.Op Fl LRdfnqrv
.Op Fl c Ar count
.Op Fl i Ar wait
.Op Fl l Ar preload
.Op Fl p Ar pattern
.Op Fl s Ar packetsize
.Op Fl t Ar ttl
.Op Fl w Ar waittime
.Op Fl I Ar interface address
.\"O .Sh DESCRIPTION
.Sh ÀâÌÀ
.\"O .Nm Ping
.\"O uses the
.\"O .Tn ICMP
.\"O protocol's mandatory
.\"O .Tn ECHO_REQUEST
.\"O datagram to elicit an
.\"O .Tn ICMP ECHO_RESPONSE
.\"O from a host or gateway.
.Nm ping
¤Ï
.Tn ICMP
¤Î
.Tn ECHO_REQUEST
¥Ç¡¼¥¿¥°¥é¥à¤òÍѤ¤¤Æ¡¢»ØÄꤷ¤¿¥Û¥¹¥È¤ä¥²¡¼¥È¥¦¥§¥¤¤«¤é¤Î
.Tn ICMP ECHO_RESPONSE
¤ò°ú¤­½Ð¤¹¡£
.\"O .Tn ECHO_REQUEST
.\"O datagrams (``pings'') have an IP and
.\"O .Tn ICMP
.\"O header,
.\"O followed by a
.\"O .Dq struct timeval
.\"O and then an arbitrary number of ``pad'' bytes used to fill out the
.\"O packet.
.Tn ECHO_REQUEST
¥Ç¡¼¥¿¥°¥é¥à (``pings'') ¤Ï IP ¤È
.Tn ICMP
¥Ø¥Ã¥À¤ò»ý¤Á¡¢¤½¤ì¤Ë
.Dq struct timeval
¤¬Â³¤­¡¢¤½¤·¤Æ¡¢¥Ñ¥±¥Ã¥È¤Î»Ä¤ê¤òËä¤á¤ë¤¿¤á¤ËǤ°Õ¸Ä¤Î ``pad'' ¥Ð¥¤¥È¤¬¤¢¤ë¡£
.\"O The options are as follows:
.\"O Other options are:
¥ª¥×¥·¥ç¥ó¤Ï°Ê²¼¤ÎÄ̤ê:
¤½¤Î¾¤Î¥ª¥×¥·¥ç¥ó¤Ï:
.Bl -tag -width Ds
.It Fl c Ar count
.\"O Stop after sending (and receiving)
.\"O .Ar count
.\"O packets. After the packets are sent,
.\"O .Nm ping
.\"O will wait up to ten seconds for replies to arrive, then exit.
.Ar count
¸Ä¤Î¥Ñ¥±¥Ã¥È¤òÁ÷¤Ã¤¿ (¤½¤·¤Æ¤½¤Î±þÅú¤ò¼õ¤±¼è¤Ã¤¿) ¸å¡¢Ää»ß¤¹¤ë¡£
¥Ñ¥±¥Ã¥È¤¬Á÷¤é¤ì¤¿¸å¡¢
.Nm ping
¤Ï±þÅú¤ò¼õ¤±¼è¤ë¤Þ¤Ç 10 ÉôÖÂÔ¤Á¡¢½ªÎ»¤¹¤ë¡£
.It Fl d
.\"O Set the
.\"O .Dv SO_DEBUG
.\"O option on the socket being used.
»ÈÍѤ¹¤ë¥½¥±¥Ã¥È¤Ë
.Dv SO_DEBUG
¥ª¥×¥·¥ç¥ó¤òÀßÄꤹ¤ë¡£
.It Fl f
.\"O Flood ping.
.\"O Outputs packets as fast as they come back or one hundred times per second,
.\"O whichever is more.
.\"O For every
.\"O .Tn ECHO_REQUEST
.\"O sent a period ``.'' is printed, while for ever
.\"O .Tn ECHO_REPLY
.\"O received a backspace is printed.
.\"O This provides a rapid display of how many packets are being dropped.
.\"O Only the super-user may use this option.
.\"O .Bf -emphasis
.\"O This can be very hard on a network and should be used with caution.
flood ping (ping ¤Î¹¿¿å)¡£¥Ñ¥±¥Ã¥È¤¬Ìá¤Ã¤Æ¤¯¤ë¤È¤¹¤°¡¢
¤â¤·¤¯¤Ï¡¢1 ÉÃ´Ö¤Ë 100 ²ó¤Î¡¢¤¤¤º¤ì¤«Â¿¤¤²ó¿ô¤À¤±¥Ñ¥±¥Ã¥È¤òÁ÷¤ë¡£
.Tn ECHO_REQUEST
¤¬Á÷¤é¤ì¤ë¤¿¤Ó¤Ë¥Ô¥ê¥ª¥É ``.'' ¤¬É½¼¨¤µ¤ì¡¢
.Tn ECHO_REPLY
¤ò¼õ¤±¼è¤ë¤´¤È¤Ë¡¢¥Ð¥Ã¥¯¥¹¥Ú¡¼¥¹¤¬É½¼¨¤µ¤ì¤ë
(ÌõÃí: ¤¹¤Ê¤ï¤Á ``.'' ¤¬¾Ãµî¤µ¤ì¤ë)¡£
¤³¤ì¤Ë¤è¤ê¡¢¤É¤Î¤¯¤é¤¤¤Î¥Ñ¥±¥Ã¥È¤¬¼è¤ê¤³¤Ü¤µ¤ì¤ë¤«¤ò¡¢
¤¹¤Ð¤ä¤¯É½¼¨¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¡£¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¡¼¤À¤±¤¬¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¨¤ë¡£
.Bf -emphasis
¤³¤ì¤Ï¡¢¥Í¥Ã¥È¥ï¡¼¥¯¤ËÈó¾ï¤ËÉé²Ù¤ò¤«¤±¤ë¤Î¤Ç¡¢Ãí°Õ¤·¤Æ»È¤¦¤Ù¤­¤Ç¤¢¤ë¡£
.Ef
.It Fl i Ar wait
.\"O Wait
.\"O .Ar wait
.\"O seconds
.\"O .Em between sending each packet .
.\"O The default is to wait for one second between each packet.
.\"O This option is incompatible with the
.\"O .Fl f
.\"O option.
¸Ä¡¹¤Î¥Ñ¥±¥Ã¥È¤Î´Ö¤Ë
.Ar wait
ÉÃÂԤġ£
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¸Ä¡¹¤Î¥Ñ¥±¥Ã¥È¤Î´Ö¤Ë 1 ÉÃÂԤġ£¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï
.Fl f
¥ª¥×¥·¥ç¥ó¤È¤ÏƱ»þ¤Ë»ØÄê¤Ç¤­¤Ê¤¤¡£
.It Fl l Ar preload
.\"O If
.\"O .Ar preload
.\"O is specified,
.\"O .Nm ping
.\"O sends that many packets as fast as possible before falling into its normal
.\"O mode of behavior.
.\"O Only the super-user may use this option.
»ØÄꤷ¤¿
.Ar preload
¤ÎÃͤÀ¤±
.Tn ECHO_REQUEST
¥Ñ¥±¥Ã¥È¤ò½ÐÍè¤ë¤À¤±Â®¤¯Á÷¿®¤·¡¢Ä̾ï¤ÎÆ°ºî¤ËÌá¤ë¡£
¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¡¼¤À¤±¤¬¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ÈÍѤǤ­¤ë¡£
.It Fl n
.\"O Numeric output only.
.\"O No attempt will be made to lookup symbolic names for host addresses.
¿ôÃͽÐÎϤΤߡ£
¥Û¥¹¥È¤Î¥¢¥É¥ì¥¹¤«¤é¡¢¥Û¥¹¥È̾¤Î¸¡º÷¤ò»î¤ß¤Ê¤¤¡£
.It Fl p Ar pattern
.\"O You may specify up to 16 ``pad'' bytes to fill out the packet you send.
.\"O This is useful for diagnosing data-dependent problems in a network.
.\"O For example,
.\"O .Dq Li \-p ff
.\"O will cause the sent packet to be filled with all
.\"O ones.
Á÷½Ð¤¹¤ë¥Ñ¥±¥Ã¥È¤òËä¤á¤ë¤¿¤á¤Î 16 ¸Ä¤Þ¤Ç¤Î ``pad'' ¥Ð¥¤¥È¤ò»ØÄê¤Ç¤­¤ë¡£
¤³¤ì¤Ï¥Í¥Ã¥È¥ï¡¼¥¯¤Ç¤Î¡¢¥Ç¡¼¥¿¤Ë°Í¸¤·¤¿ÌäÂê¤Î¿ÇÃǤËÍ­ÍѤǤ¢¤ë¡£
¤¿¤È¤¨¤Ð
.Dq Li \-p ff
¤ÏÁ´¤Æ 1 ¤ÇËä¤á¤é¤ì¤¿¥Ñ¥±¥Ã¥È¤òÁ÷¤ë¡£
.It Fl q
.\"O Quiet output.
.\"O Nothing is displayed except the summary lines at startup time and
.\"O when finished.
ÀŤ«¤Ê½ÐÎÏ¡£
³«»Ï¤È½ªÎ»»þ¤ÎÍ×Ìó°Ê³°¤Ï¡¢²¿¤âɽ¼¨¤·¤Ê¤¤¡£
.It Fl R
.\"O Record route.
.\"O Includes the
.\"O .Tn RECORD_ROUTE
.\"O option in the
.\"O .Tn ECHO_REQUEST
.\"O packet and displays
.\"O the route buffer on returned packets.
.\"O Note that the IP header is only large enough for nine such routes.
.\"O Many hosts ignore or discard this option.
·ÐÏ©¤òµ­Ï¿¡£
.Tn ECHO_REQUEST
¥Ñ¥±¥Ã¥È¤Ë
.Tn RECORD_ROUTE
¥ª¥×¥·¥ç¥ó¤òÀßÄꤷ¡¢Ê֤äƤ­¤¿¥Ñ¥±¥Ã¥È¤Î·ÐÏ©¥Ð¥Ã¥Õ¥¡
(route buffer) ¤òɽ¼¨¤¹¤ë¡£
IP ¥Ø¥Ã¥À¤Ï 9 ¤Ä¤Î·Ðϩʬ¤ÎÂ礭¤µ¤·¤«¤Ê¤¤¤³¤È¤ËÃí°Õ¤»¤è¡£
¤Þ¤¿¡¢Â¿¤¯¤Î¥Û¥¹¥È¤Ï¤³¤Î¥ª¥×¥·¥ç¥ó¤ò̵»ë¤¹¤ë¤«¡¢ÇË´þ¤·¤Æ¤·¤Þ¤¦¡£
.It Fl r
.\"O Bypass the normal routing tables and send directly to a host on an attached
.\"O network.
.\"O If the host is not on a directly-attached network, an error is returned.
.\"O This option can be used to ping a local host through an interface
.\"O that has no route through it (e.g., after the interface was dropped by
.\"O .Xr routed 8 ) .
Ä̾ï¤Î¥ë¡¼¥Æ¥£¥ó¥°¤ò̵»ë¤·¡¢Àܳ¤µ¤ì¤¿¥Í¥Ã¥È¥ï¡¼¥¯¤Î¥Û¥¹¥È¤ËľÀÜÁ÷¤ë¡£
¤â¤·¡¢¥Û¥¹¥È¤¬Ä¾¤ËÀܳ¤µ¤ì¤¿¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¤Ê¤±¤ì¤Ð¡¢¥¨¥é¡¼¤¬Ê֤롣
·ÐÏ©¾ðÊó¤ò»ý¤¿¤Ê¤¤¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤òÄ̤·¤Æ¡¢
¥í¡¼¥«¥ë¤Ê¥Û¥¹¥È¤Ø¤È ping ¤¹¤ë¤Î¤Ë»È¤ï¤ì¤ë¡£(Î㤨¤Ð¡¢¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤¬
.Xr routed 8
¤ËÍ¤ì¤¿¾ì¹ç)¡£
.It Fl s Ar packetsize
.\"O Specifies the number of data bytes to be sent.  
.\"O The default is 56, which translates into 64
.\"O .Tn ICMP
.\"O data bytes when combined
.\"O with the 8 bytes of
.\"O .Tn ICMP
.\"O header data.
.\"O Only the super-user may use this option.
²¿¥Ð¥¤¥È¤Î¥Ç¡¼¥¿¤¬Á÷¤é¤ì¤ë¤«¤ò»ØÄꤹ¤ë¡£¥Ç¥Õ¥©¥ë¥È¤Ï 56 ¤Ç¡¢
.Tn ICMP
¥Ø¥Ã¥À¤Î 8 ¥Ð¥¤¥È¤ò²Ã¤¨¤Æ¡¢
64 ¥Ð¥¤¥È¤Î
.Tn ICMP
¥Ç¡¼¥¿¤Ë¤Ê¤ë¡£
¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¡¼¤À¤±¤¬¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ÈÍѤǤ­¤ë¡£
.It Fl v
.\"O Verbose output.
.\"O .Tn ICMP
.\"O packets other than
.\"O .Tn ECHO_RESPONSE
.\"O that are received are listed.
¾ÜºÙ¤Ê½ÐÎÏ¡£
¼õ¤±¼è¤Ã¤¿
.Tn ECHO_RESPONSE
°Ê³°¤Î
.Tn ICMP
¥Ñ¥±¥Ã¥È¤òɽ¼¨¤¹¤ë¡£
.It Fl w Ar waittime
.\"O Cause
.\"O .Nm ping
.\"O to exit after
.\"O .Ar waittime
.\"O seconds, independently of other considerations.
¤É¤Î¤è¤¦¤Ê¾ì¹ç¤Ç¤â´Ø·¸¤Ê¤¯¡¢
.Nm ping
¤ò
.Ar waittime
Éøå¤Ë½ªÎ»¤µ¤»¤ë¡£
.El
.Pp
°Ê²¼¤Î¥ª¥×¥·¥ç¥ó¤Ë´Ø¤¹¤ëµ­½Ò¤Ï¡¢
.Nm
¤Î¥½¡¼¥¹¡¢¤Ê¤é¤Ó¤Ë FreeBSD ¤Î man ¥Ú¡¼¥¸¤ò»²¹Í¤Ë
ÆüËܸìÌõ¤ËºÝ¤·¤ÆÄɲ䵤줿¡£
.Bl -tag -width indent
.It Fl I Ar interface
Í¿¤¨¤é¤ì¤¿¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤«¤é¡¢¥Þ¥ë¥Á¥­¥ã¥¹¥È¥Ñ¥±¥Ã¥È¤òÁ÷¤ë¡£
.It Fl L
¥Þ¥ë¥Á¥­¥ã¥¹¥È¥Ñ¥±¥Ã¥È¤Î¥ë¡¼¥×¥Ð¥Ã¥¯¤òÍÞÀ©¤¹¤ë¡£
.It Fl t Ar ttl
¥Þ¥ë¥Á¥­¥ã¥¹¥È¥Ñ¥±¥Ã¥È¤Î IP ¼÷Ì¿»þ´Ö (Time To Live) ¤òÀßÄꤹ¤ë¡£
.El
.Pp
.\"O When using
.\"O .Nm ping
.\"O for fault isolation, it should first be run on the local host, to verify
.\"O that the local network interface is up and running.
.\"O Then, hosts and gateways further and further away should be ``pinged''.
ÌäÂê¤ÎÀÚ¤êʬ¤±¤Î¤¿¤á¤Ë
.Nm ping
¤òÍѤ¤¤ë¾ì¹ç¡¢¤½¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤¬ up ¤«¤Ä running ¤Ç¤¢¤ë
¤³¤È¤ò³Îǧ¤¹¤ë¤¿¤á¤Ë¡¢¤Þ¤º¥í¡¼¥«¥ë¥Û¥¹¥È¾å¤Ç¼Â¹Ô¤¹¤ë¤Ù¤­¤Ç¤¢¤ë¡£
¤½¤Î¸å¤Ë¤è¤ê±ó¤¯¤Î¥Û¥¹¥È¤ä¥²¡¼¥È¥¦¥§¥¤¤Ë
.Dq ping
¤¹¤ë¡£
.\"O Round-trip times and packet loss statistics are computed.
.\"O If duplicate packets are received, they are not included in the packet
.\"O loss calculation, although the round trip time of these packets is used
.\"O in calculating the minimum/average/maximum round-trip time numbers.
±ýÉü»þ´Ö (round-trip time) ¤È¾Ã¼º¥Ñ¥±¥Ã¥È¤ÎÅý·×¤¬·×»»¤µ¤ì¤ë¡£
½ÅÊ£¤·¤¿±þÅú¥á¥Ã¥»¡¼¥¸¤ò¼õ¤±¼è¤Ã¤¿¾ì¹ç¡¢
¤½¤ì¤é¤Ï¥Ñ¥±¥Ã¥È¤Î»¼º¤Î·×»»¤Ë¤Ï»È¤ï¤ì¤Ê¤¤¤¬¡¢
¤½¤ì¤Ë¤â¤«¤«¤ï¤é¤º¤½¤¦¤·¤¿¥Ñ¥±¥Ã¥È¤Î±ýÉü»þ´Ö¤Ï¡¢
¤½¤ÎºÇ¾®ÃÍ¡¦Ê¿¶ÑÃÍ¡¦ºÇÂçÃͤη׻»¤ËÍѤ¤¤é¤ì¤ë¡£
.\"O When the specified number of packets have been sent (and received) or
.\"O if the program is terminated with a
.\"O .Dv SIGINT ,
.\"O a brief summary is displayed.
»ØÄꤷ¤¿¿ô¤Î¥Ñ¥±¥Ã¥È¤¬Á÷¤é¤ì¤¿ (¤½¤·¤Æ¤½¤Î±þÅú¤ò¼õ¤±¼è¤Ã¤¿) ¤«¡¢¥×¥í¥°¥é¥à¤¬
.Dv SIGINT
¤Ç½ªÎ»¤µ¤»¤é¤ì¤¿¾ì¹ç¤Ï¡¢´Êñ¤ÊÍ×Ìó¤¬É½¼¨¤µ¤ì¤ë¡£
.Pp
.\"O If 
.\"O .Nm ping
.\"O does not receive any reply packets at all it will exit with code 1.
.\"O On error it exits with code 2. Otherwise it exits with code 0. This
.\"O makes it possible to use the exit code to see if a host is alive or
.\"O not.
¤â¤·
.Nm ping
¤¬Á´¤¯±þÅú¥Ñ¥±¥Ã¥È¤ò¼õ¤±¼è¤é¤Ê¤«¤Ã¤¿¾ì¹ç¤Ë¤Ï¡¢½ªÎ»¥³¡¼¥É 1 ¤Ç½ªÎ»¤¹¤ë¡£
¥¨¥é¡¼¤¬¤¢¤ì¤Ð¥³¡¼¥É 2 ¤Ç½ªÎ»¤¹¤ë¡£¤½¤ì°Ê³°¤Î¾ì¹ç¤Ï¥³¡¼¥É 0 ¤Ç½ªÎ»¤¹¤ë¡£
¤³¤ì¤Ë¤è¤ê¡¢½ªÎ»¥³¡¼¥É¤Ç¡¢¤¢¤ë¥Û¥¹¥È¤¬Æ°¤¤¤Æ¤¤¤ë¤«¤É¤¦¤«¤òȽÃǤ¹¤ë¤³¤È
¤¬¤Ç¤­¤ë¡£
.Pp
.\"O This program is intended for use in network testing, measurement and
.\"O management.
.\"O Because of the load it can impose on the network, it is unwise to use
.\"O .Nm ping
.\"O during normal operations or from automated scripts.
¤³¤Î¥×¥í¥°¥é¥à¤Ï¥Í¥Ã¥È¥ï¡¼¥¯¤Î¥Æ¥¹¥È¡¦·×¬¡¦´ÉÍý¤Ë¤Ä¤¤¤Æ¤Î»ÈÍѤò°Õ¿Þ¤·¤Æ¤¤¤ë¡£
¤³¤Î¥×¥í¥°¥é¥à¤¬¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¶¯¤¤¤ëÉé²Ù¤ò¹Í¤¨¤ì¤Ð¡¢
.Nm ping
¤ò¥È¥é¥Ö¥ë¤Î¤Ê¤¤¤È¤­¤ä¼«Æ°¥¹¥¯¥ê¥×¥È¤«¤é¼Â¹Ô¤¹¤ë¤³¤È¤Ï¾©¤á¤é¤ì¤Ê¤¤¡£
.\"O .Sh ICMP PACKET DETAILS
.Sh ICMP ¥Ñ¥±¥Ã¥È¤Î¾ÜºÙ
.\"O An IP header without options is 20 bytes.
.\"O An
.\"O .Tn ICMP
.\"O .Tn ECHO_REQUEST
.\"O packet contains an additional 8 bytes worth
.\"O of
.\"O .Tn ICMP
.\"O header followed by an arbitrary amount of data.
¥ª¥×¥·¥ç¥ó¤Ê¤·¤Î IP ¥Ø¥Ã¥À¤Ï 20 ¥Ð¥¤¥È¤Ç¤¢¤ë¡£
.Tn ICMP
.Tn ECHO_REQUEST
¥Ñ¥±¥Ã¥È¤Ï¡¢¤µ¤é¤Ê¤ë 8 ¥Ð¥¤¥È¤Î
.Tn ICMP
¥Ø¥Ã¥À¤È¤½¤ì¤Ë³¤¯Ç¤°Õ¤ÎÎ̤Υǡ¼¥¿¤«¤é¤Ê¤ë¡£
.\"O When a
.\"O .Ar packetsize
.\"O is given, this indicated the size of this extra piece of data (the
.\"O default is 56).
.\"O Thus the amount of data received inside of an IP packet of type
.\"O .Tn ICMP
.\"O .Tn ECHO_REPLY
.\"O will always be 8 bytes more than the requested data space
.\"O (the
.\"O .Tn ICMP
.\"O header).
.Ar packetsize
¤¬Í¿¤¨¤é¤ì¤¿»þ¤Ë¤Ï¡¢¤½¤ì¤ÏÉÕ²ÃŪ¤Ê¥Ç¡¼¥¿Éôʬ¤Î¥µ¥¤¥º (¥Ç¥Õ¥©¥ë¥È¤Ï 56) ¤ò¼¨¤¹¡£
¤è¤Ã¤Æ
.Tn ICMP
.Tn ECHO_REPLY
¥Ñ¥±¥Ã¥È¤Î IP ¥Ñ¥±¥Ã¥ÈÆâ¤Ç¼õ¤±¼è¤ë¥Ç¡¼¥¿¤ÎÎ̤ϡ¢
Í׵ᤵ¤ì¤¿¥Ç¡¼¥¿Îΰè¤è¤ê 8 ¥Ð¥¤¥È
.Ns ( Tn ICMP
¥Ø¥Ã¥À¤Îʬ) ¿¤¤¡£
.Pp
.\"O If the data space is at least eight bytes large,
.\"O .Nm ping
.\"O uses the first eight bytes of this space to include a timestamp which
.\"O it uses in the computation of round trip times.
.\"O If less than eight bytes of pad are specified, no round trip times are
.\"O given.
¤â¤·¥Ç¡¼¥¿Îΰ褬 8 ¥Ð¥¤¥È¤è¤ê¤âÂ礭¤±¤ì¤Ð¡¢
.Nm ping
¤Ï¤½¤ÎÎΰè¤ÎÀèƬ 8 ¥Ð¥¤¥È¤ò¡¢±ýÉü»þ´Ö¤ò·×»»¤¹¤ë¤Î¤Ë»È¤¦¥¿¥¤¥à¥¹¥¿¥ó¥×¤ò
´Þ¤á¤ë¤¿¤á¤Ë»ÈÍѤ¹¤ë¡£
¤â¤· 8 ¥Ð¥¤¥È¤è¤ê¤â¾¯¤Ê¤±¤ì¤Ð¡¢±ýÉü»þ´Ö¤ÏÆÀ¤é¤ì¤Ê¤¤¡£
.\"O .Sh DUPLICATE AND DAMAGED PACKETS
.Sh ½ÅÊ£¥Ñ¥±¥Ã¥È¤È¾ã³²¥Ñ¥±¥Ã¥È
.\"O .Nm Ping
.\"O will report duplicate and damaged packets.
.\"O Duplicate packets should never occur, and seem to be caused by
.\"O inappropriate link-level retransmissions.
.\"O Duplicates may occur in many situations and are rarely (if ever) a
.\"O good sign, although the presence of low levels of duplicates may not
.\"O always be cause for alarm.
.Nm ping
¤Ï¡¢½ÅÊ£¥Ñ¥±¥Ã¥È¤È¾ã³²¥Ñ¥±¥Ã¥È¤Ë¤Ä¤¤¤ÆÊó¹ð¤¹¤ë¡£
½ÅÊ£¥Ñ¥±¥Ã¥È¤Ï (¥æ¥Ë¥­¥ã¥¹¥È¥¢¥É¥ì¥¹¤ËÂФ·¤Æ¤Ï) µ¯¤­¤ë¤Ï¤º¤Ï¤Ê¤¤¤¬¡¢
ÉÔŬÀڤʥê¥ó¥¯ÁؤǤκÆÁ÷¤Ë¤è¤Ã¤Æ°ú¤­µ¯¤³¤µ¤ì¤ë¤è¤¦¤Ë»×¤ï¤ì¤ë¡£
½ÅÊ£¤ÏÍÍ¡¹¤Ê¾õ¶·¤Çµ¯¤³¤ë²ÄǽÀ­¤¬¤¢¤ë¡£Ä㤤¥ì¥Ù¥ë¤Î½ÅÊ£¤Î¸ºß¤Ï
ɬ¤º¤·¤â·Ù¹ð¤Ë¤Ï¤Ê¤é¤Ê¤¤¤«¤â¤·¤ì¤Ê¤¤¤¬¡¢¤è¤¤Ãû¸õ¤Ç¤Ï¤Ê¤¤¡£
.Pp
.\"O Damaged packets are obviously serious cause for alarm and often
.\"O indicate broken hardware somewhere in the
.\"O .Nm ping
.\"O packet's path (in the network or in the hosts).
¾ã³²¤ò¼õ¤±¤¿¥Ñ¥±¥Ã¥È¤Ï¡¢ÌÀ¤é¤«¤Ë¿¼¹ï¤Ê·Ù¹ð¤Ç¤¢¤ê¡¢Â¿¤¯¤Î¾ì¹ç
.Nm ping
¥Ñ¥±¥Ã¥È¤Î·ÐÏ©¾å (¥Í¥Ã¥È¥ï¡¼¥¯Æâ¡¢¤â¤·¤¯¤Ï¤½¤Î¥Û¥¹¥ÈÆâ) ¤Î¤É¤³¤«¤Ë
²õ¤ì¤¿¥Ï¡¼¥É¥¦¥§¥¢¤¬¤¢¤ë¤³¤È¤ò¼¨¤¹¡£
.\"O .Sh TRYING DIFFERENT DATA PATTERNS
.Sh °Û¤Ê¤ë¥Ç¡¼¥¿¥Ñ¥¿¡¼¥ó¤Î»î¹Ô
.\"O The (inter)network layer should never treat packets differently depending
.\"O on the data contained in the data portion.
(¥¤¥ó¥¿¡¼) ¥Í¥Ã¥È¥ï¡¼¥¯Áؤϡ¢·è¤·¤Æ¥Ç¡¼¥¿Éôʬ¤Ë´Þ¤Þ¤ì¤ë¥Ç¡¼¥¿¤Ë¤è¤Ã¤Æ
¥Ñ¥±¥Ã¥È¤Î°·¤¤¤òÊѤ¨¤¿¤ê¤·¤Ê¤¤¡£
.\"O Unfortunately, data-dependent problems have been known to sneak into
.\"O networks and remain undetected for long periods of time.
ÉÔ¹¬¤Ë¤â¡¢¥Ç¡¼¥¿¤Ë°Í¸¤·¤¿ÌäÂ꤬¥Í¥Ã¥È¥ï¡¼¥¯¤Ø¤È¿¯Æþ¤·¡¢
Ť¤»þ´Öȯ¸«¤µ¤ì¤Ê¤¤¤Þ¤Þ¤È¤Ê¤Ã¤Æ¤·¤Þ¤¦²ÄǽÀ­¤¬ÃΤé¤ì¤Æ¤¤¤ë¡£
.\"O In many cases the particular pattern that will have problems is something
.\"O that doesn't have sufficient ``transitions'', such as all ones or all
.\"O zeros, or a pattern right at the edge, such as almost all zeros.
ÌäÂê¤Î¤¢¤ë¥Ñ¥±¥Ã¥È¤ÎÆÃÄê¤Î¥Ñ¥¿¡¼¥ó¤Ï¿¤¯¤Î¾ì¹ç¡¢
Á´¤Æ¤¬ 0 ¤Þ¤¿¤ÏÁ´¤Æ¤¬ 1 ¤Î¤è¤¦¤Ê¤â¤Î¡¢
¤¢¤ë¤¤¤Ï±¦Ã¼°Ê³°¤¬Ëؤó¤É 0 ¤Î¤è¤¦¤Ê¡¢
½½Ê¬¤Ê ``Á«°Ü (transitions)'' ¤ò»ý¤¿¤Ê¤¤¤â¤Î¤Ç¤¢¤ë¡£
.\"O It isn't necessarily enough to specify a data pattern of all zeros (for
.\"O example) on the command line because the pattern that is of interest is
.\"O at the data link level, and the relationship between what you type and
.\"O what the controllers transmit can be complicated.
¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ç (Î㤨¤Ð) Á´¤Æ 0 ¤È¤¤¤¦¥Ç¡¼¥¿¥Ñ¥¿¡¼¥ó¤ò»ØÄꤹ¤ë¤³¤È¤Ï¡¢
ɬ¤º¤·¤â½½Ê¬¤Ç¤Ï¤Ê¤¤¡£
¤Ê¤¼¤Ê¤é¤Ð¡¢¤½¤Î´Ø¿´¤Î¤¢¤ë¤Î¤Ï¥Ç¡¼¥¿¥ê¥ó¥¯Áؤˤª¤±¤ë¥Ñ¥¿¡¼¥ó¤Ç¤¢¤ê¡¢
¤¢¤Ê¤¿¤¬ÆþÎϤ·¤¿¤â¤Î¤È¡¢¥³¥ó¥È¥í¡¼¥é¡¼¤¬Á÷¿®¤¹¤ë¤â¤Î¤È¤Î´Ø·¸¤Ï
Ê£»¨¤À¤«¤é¤Ç¤¢¤ë¡£
.Pp
.\"O This means that if you have a data-dependent problem you will probably
.\"O have to do a lot of testing to find it.
¤³¤ì¤Ï¡¢¤â¤·¤¢¤Ê¤¿¤¬¥Ç¡¼¥¿°Í¸À­¤ÎÌäÂê¤òÊú¤¨¤Æ¤¤¤ë¤Ê¤é¡¢
¤½¤ì¤òȯ¸«¤¹¤ë¤¿¤á¤Ë¤Ï
²¿²ó¤â¤Î¥Æ¥¹¥È¤ò¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤â¤·¤ì¤Ê¤¤¤³¤È¤ò°ÕÌ£¤¹¤ë¡£
.\"O If you are lucky, you may manage to find a file that either can't be sent
.\"O across your network or that takes much longer to transfer than other
.\"O similar length files.
¤â¤·±¿¤¬Îɤ±¤ì¤Ð¡¢¥Í¥Ã¥È¥ï¡¼¥¯¤òÄ̤·¤ÆÁ÷¤ë¤³¤È¤Î¤Ç¤­¤Ê¤¤¥Õ¥¡¥¤¥ë¤«¡¢
Ʊ¤¸¤è¤¦¤ÊŤµ¤Î¥Õ¥¡¥¤¥ë¤è¤ê¡¢Å¾Á÷¤Ë¤º¤Ã¤È»þ´Ö¤Î¤«¤«¤ë¥Õ¥¡¥¤¥ë¤ò
ȯ¸«¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤«¤â¤·¤ì¤Ê¤¤¡£
.\"O You can then examine this file for repeated patterns that you can test
.\"O using the
.\"O .Fl p
.\"O option of
.\"O .Nm ping .
¤½¤¦¤·¤¿¤é¡¢¤½¤Î¥Õ¥¡¥¤¥ë¤òÄ´¤Ù·«¤êÊÖ¤·¸½¤ï¤ì¤ë¥Ñ¥¿¡¼¥ó¤ò
.Nm ping
¤Î
.Fl p
¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¥Æ¥¹¥È¤Ç¤­¤ë¡£
.\"O .Sh TTL DETAILS
.Sh TTL ¤Î¾ÜºÙ
.\"O The
.\"O .Tn TTL
.\"O value of an IP packet represents the maximum number of IP routers
.\"O that the packet can go through before being thrown away.
.\"O In current practice you can expect each router in the Internet to decrement
.\"O the
.\"O .Tn TTL
.\"O field by exactly one.
IP ¥Ñ¥±¥Ã¥È¤Î
.Tn TTL
¤È¤¤¤¦Ãͤϡ¢¥Ñ¥±¥Ã¥È¤¬ÇË´þ¤µ¤ì¤ëÁ°¤ËÄ̲᤹¤ë¤³¤È¤¬¤Ç¤­¤ë
IP ¥ë¡¼¥¿¤ÎºÇÂçÃͤò¼¨¤¹¡£
¸½ºß¤Î´·Î㤫¤é¡¢¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤Î³Æ¥ë¡¼¥¿¤Ï
.Tn TTL
¥Õ¥£¡¼¥ë¥É¤òÀµ³Î¤Ë 1 ¸º¤é¤¹¤³¤È¤ò´üÂԤǤ­¤ë¡£
.Pp
.\"O The
.\"O .Tn TCP/IP
.\"O specification states that the
.\"O .Tn TTL
.\"O field for
.\"O .Tn TCP
.\"O packets should
.\"O be set to 60, but many systems use smaller values (4.3
.\"O .Tn BSD
.\"O uses 30, 4.2 used
.\"O 15).
.Tn TCP/IP
µ¬³Ê¤Ï¡¢
.Tn TCP
¥Ñ¥±¥Ã¥È¤Î
.Tn TTL
¥Õ¥£¡¼¥ë¥É¤Ï 60 ¤ËÀßÄꤵ¤ì¤ë¤Ù¤­¤Ç¤¢¤ë¤È¤·¤Æ¤¤¤ë¤¬¡¢Â¿¤¯¤Î¥·¥¹¥Æ¥à¤Ï
¤â¤Ã¤È¾®¤µ¤ÊÃͤò»ÈÍѤ·¤Æ¤¤¤ë (4.3
.Tn BSD
¤Ï 30¡¢4.2 ¤Ï 15)¡£
.Pp
.\"O The maximum possible value of this field is 255, and most Unix systems set
.\"O the
.\"O .Tn TTL
.\"O field of
.\"O .Tn ICMP ECHO_REQUEST
.\"O packets to 255.
¤³¤Î¥Õ¥£¡¼¥ë¥É¤ÎÀßÄê²Äǽ¤ÊºÇÂçÃÍ¤Ï 255 ¤Ç¡¢Ëؤó¤É¤Î Unix ¥·¥¹¥Æ¥à¤Ï
.Tn ICMP ECHO_REQUEST
¤Î
.Tn TTL
¥Õ¥£¡¼¥ë¥É¤ò 255 ¤ËÀßÄꤷ¤Æ¤¤¤ë¡£
.\"O This is why you will find you can ``ping'' some hosts, but not reach them
.\"O with
.\"O .Xr telnet 1
.\"O or
.\"O .Xr ftp 1 .
¤³¤ì¤Ï¡¢¤¢¤ë¥Û¥¹¥È¤Ç¤Ï ``ping'' ¤¬Ä̤ë¤Î¤Ë¡¢
.Xr telnet 1
¤ä
.Xr ftp 1
¤Ç¤Ï¤½¤Î¥Û¥¹¥È¤ËÆϤ«¤Ê¤¤Íýͳ (¤Î°ì¤Ä) ¤Ç¤¢¤ë¡£
.Pp
.\"O In normal operation ping prints the ttl value from the packet it receives.
.\"O When a remote system receives a ping packet, it can do one of three things
.\"O with the
.\"O .Tn TTL
.\"O field in its response:
ping ¤ÎÄ̾ï¤ÎÁàºî¤Ç¤Ï¡¢¼õ¤±¼è¤Ã¤¿¥Ñ¥±¥Ã¥È¤Î ttl ¤ÎÃͤ¬É½¼¨¤µ¤ì¤ë¡£
¥ê¥â¡¼¥È¤Î¥·¥¹¥Æ¥à¤¬ ping ¥Ñ¥±¥Ã¥È¤ò¼õ¤±¼è¤Ã¤¿»þ¡¢¤½¤Î±þÅú¤Ë¤ª¤±¤ë
.Tn TTL
¥Õ¥£¡¼¥ë¥É¤Ë¤Ï°Ê²¼¤Î 3 ¤Ä¤Î¤¦¤Á¤Î 1 ¤Ä¤ò¼è¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
.Bl -bullet
.It
.\"O Not change it; this is what Berkeley Unix systems did before the
.\"O .Bx 4.3 tahoe
.\"O release.
Êѹ¹¤·¤Ê¤¤; ¤³¤ì¤Ï
.Bx 4.3 tahoe
¥ê¥ê¡¼¥¹°ÊÁ°¤Î BSD Unix ¥·¥¹¥Æ¥à¤¬¹Ô¤Ã¤Æ¤¤¤¿¤â¤Î¤Ç¤¢¤ë¡£
.\"O In this case the
.\"O .Tn TTL
.\"O value in the received packet will be 255 minus the
.\"O number of routers in the round-trip path.
¤³¤Î¾ì¹ç¡¢¼õ¤±¼è¤Ã¤¿¥Ñ¥±¥Ã¥È¤Î
.Tn TTL
¤ÎÃͤϡ¢255 ¤«¤é±ýÉü·ÐÏ©¾å¤Î¥ë¡¼¥¿¤Î¿ô¤ò°ú¤¤¤¿¤â¤Î¤Ë¤Ê¤ë¡£
.It
.\"O Set it to 255; this is what current Berkeley Unix systems do.
.\"O In this case the
.\"O .Tn TTL
.\"O value in the received packet will be 255 minus the
.\"O number of routers in the path
.\"O .Xr from
.\"O the remote system
.\"O .Em to
.\"O the
.\"O .Nm ping Ns Em ing
.\"O host.
255 ¤Ë¥»¥Ã¥È¤¹¤ë; ¤³¤ì¤Ï¸½ºß¤Î BSD Unix ¤¬¹Ô¤Ã¤Æ¤¤¤ë¤â¤Î¤Ç¤¢¤ë¡£
(ÌõÃí: Linux ¤â¤³¤ì¤Ë¤¢¤¿¤ë)¡£
¤³¤Î¾ì¹ç¡¢¼õ¤±¼è¤ë¥Ñ¥±¥Ã¥È¤Î
.Tn TTL
¤ÎÃͤϡ¢¥ê¥â¡¼¥È¥·¥¹¥Æ¥à
.Xr ¤«¤é
.Nm ping
¤ò¹Ô¤Ã¤¿¥Û¥¹¥È¤Ø¤Î·ÐÏ©¾å¤Î¥ë¡¼¥¿¤Î¿ô¤ò¡¢255 ¤«¤é°ú¤¤¤¿¤â¤Î¤Ç¤¢¤ë¡£
.It
.\"O Set it to some other value.
.\"O Some machines use the same value for
.\"O .Tn ICMP
.\"O packets that they use for
.\"O .Tn TCP
.\"O packets, for example either 30 or 60.
.\"O Others may use completely wild values.
¤½¤Î¾¤ÎÃͤ˥»¥Ã¥È¤¹¤ë¡£¤¤¤¯¤Ä¤«¤Î¥Þ¥·¥ó¤Ï¡¢Î㤨¤Ð 30 ¤Þ¤¿¤Ï 60 ¤Î¤è¤¦¤Ê
.Tn TCP
¥Ñ¥±¥Ã¥È¤ÎÃͤÈƱ¤¸¤â¤Î¤ò
.Tn ICMP
¥Ñ¥±¥Ã¥È¤ËÍѤ¤¤ë¡£¤Þ¤¿Á´¤¯°Û¤Ê¤ëÃͤòÍѤ¤¤ë¥Þ¥·¥ó¤â¤¢¤ë¤«¤âÃΤì¤Ê¤¤¡£
.El
.\"O .Sh BUGS
.Sh ¥Ð¥°
.\"O Many Hosts and Gateways ignore the
.\"O .Tn RECORD_ROUTE
.\"O option.
¿¤¯¤Î¥Û¥¹¥È¤È¥²¡¼¥È¥¦¥§¥¤¤Ï
.Tn RECORD_ROUTE
¥ª¥×¥·¥ç¥ó¤ò̵»ë¤¹¤ë¡£
.Pp
.\"O The maximum IP header length is too small for options like
.\"O .Tn RECORD_ROUTE
.\"O to
.\"O be completely useful.
.\"O There's not much that that can be done about this, however.
.Tn RECORD_ROUTE
¤ò´°Á´¤ËÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢IP ¥Ø¥Ã¥À¤ÎºÇÂçŤÏû²á¤®¤ë¡£
¤·¤«¤·¡¢¤³¤ì¤Ë¤Ä¤¤¤Æ¤Ç¤­¤ë¤³¤È¤Ï¿¤¯¤Ê¤¤¡£
.Pp
.\"O Flood pinging is not recommended in general, and flood pinging the
.\"O broadcast address should only be done under very controlled conditions.
flood ping ¤Ï°ìÈÌŪ¤Ë¤Ï¿ä¾©¤µ¤ì¤Ê¤¤¤·¡¢¥Ö¥í¡¼¥É¥­¥ã¥¹¥È¥¢¥É¥ì¥¹¤Ø¤Î
flood ping ¤Ï¡¢¤­¤Á¤ó¤È¾ò·ï¤òÀ°¤¨¤¿¾ì¹ç¤Ë¤ª¤¤¤Æ¤Î¤ß»ÈÍѤµ¤ì¤ë¤Ù¤­¤Ç¤¢¤ë¡£
.Pp
ÆüËܸìÌõ¤ËºÝ¤·¡¢¤¤¤¯¤Ä¤«¤Î¥ª¥×¥·¥ç¥ó¤Ë´Ø¤¹¤ëµ­½Ò¤ò²Ã¤¨¤¿¤¬¡¢Àµ¤·¤¤¤«¤É
¤¦¤«Ê¬¤«¤é¤Ê¤¤¡£
.\"O .Sh SEE ALSO
.Sh ´ØÏ¢¹àÌÜ
.Xr netstat 1 ,
.Xr ifconfig 8
.\"O .Sh HISTORY
.Sh ÍúÎò
.\"O The
.\"O .Nm
.\"O command appeared in
.\"O .Bx 4.3 .
.Nm
¥³¥Þ¥ó¥É¤Ï
.Bx 4.3
¤«¤éÅо줷¤¿¡£