Name
Allow pinging a broadcast address.
Do not allow ping to change source address of probes. The address is bound to one selected when ping starts.
Set the SO_DEBUG option on the socket being used. Essentially, this socket option is not used by Linux kernel.
-F flow label
-I interface address
Set source address to specified interface address. Argument may be numeric IP address or name of device. When pinging IPv6 link-local address this option
is required.
Suppress loopback of multicast packets. This flag only applies if the ping destination is a multicast address.
Numeric output only. No attempt will be made to lookup symbolic names for host addresses.
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.
Bypass the normal routing tables and send directly to a host on an attached interface. 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 provided the option -I is also used.
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.
Set socket sndbuf. If not specified, it is selected to buffer not more than one packet.
Set the IP Time to Live.
-T timestamp option
Select Path MTU Discovery strategy. hint may be either do (prohibit fragmentation, even local one), want (do PMTU discovery, fragment
locally when packet size is large), or dont (do not set DF flag).
Show version and exit.
Specify a timeout, in seconds, before ping exits regardless of how many packets have been sent or received. In this case ping does not stop
after count packet are sent, it waits either for deadline expire or until count probes are answered or for some error notification from
network.
Time to wait for a response, in seconds. The option affects only timeout in absense of any responses, otherwise ping waits for two RTTs.
When using ping 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 minimum/average/maximum
round-trip time numbers. 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. Shorter current statistics can be obtained without termination of process with signal SIGQUIT.
If ping does not receive any reply packets at all it will exit with code 1. If a packet count and deadline are both specified, and
fewer than count packets are received by the time the deadline has arrived, it will also exit with code 1. On other error it exits with code 2.
Otherwise it exits with code 0. This makes it possible to use the exit code to see if a host is alive or not.
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
ping during normal operations or from automated scripts.
Icmp Packet Details
If the data space is at least of size of struct timeval ping uses the beginning bytes of this space to include a timestamp which it uses in the
computation of round trip times. If the data space is shorter, no round trip times are given.
Duplicate and Damaged Packets
ping will report duplicate and damaged packets. Duplicate packets should never occur, 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.
Damaged packets are obviously serious cause for alarm and often indicate broken hardware somewhere in the ping packet’s path (in the network or in
the hosts).
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 doesn’t have sufficient ”transitions”, such as all ones or all zeros, or a pattern right at the edge, such as almost all zeros. It isn’t
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.
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 can’t 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 -p option of ping.
Ttl Details
The 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 TTL field by exactly one.
The TCP/IP specification states that the TTL field for TCP packets should be set to 60, but many systems use smaller values (4.3 BSD uses 30, 4.2 used 15).
In normal operation ping 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 TTL field in its response:
- Not change it; this is what Berkeley Unix systems did before the 4.3BSD Tahoe release. In this case the TTL value in the received packet will be 255 minus
the number of routers in the round-trip path. - Set it to 255; this is what current Berkeley Unix systems do. In this case the TTL value in the received packet will be 255 minus the number of routers in
the path from the remote system to the pinging host. - Set it to some other value. Some machines use the same value for ICMP packets that they use for TCP packets, for example either 30 or 60. Others may use
completely wild values.
Bugs
- Many Hosts and Gateways ignore the RECORD_ROUTE option.
- Flood pinging is not recommended in general, and flood pinging the broadcast address should only be done under very controlled conditions.
See Also
The ping command appeared in 4.3BSD.
The version described here is its descendant specific to Linux.
Security
ping requires CAP_NET_RAWIO capability to be executed. It may be used as set-uid root.
Availability
ping is part of iputils package and the latest versions are available in source form at
http://www.skbuff.net/iputils/iputils-current.tar.bz2.
Referenced By
The ping command is a Command Prompt command used to test the ability of the source computer to reach a specified destination computer. It’s a simple way to verify that a computer can communicate with another computer or network device.
For example, you might find no responses when pinging a network printer, only to find out that the printer is offline and its cable needs replaced. Or maybe you need to ping a router to verify that your computer can connect to it to eliminate it as a possible cause for a networking issue.
The word “ping” is also used online to refer to a brief message, usually over text or email. For example, you can “ping your boss” or send them a message about a project, but the ping command has nothing to do with it.
Ping Command Availability
The ping command is available from the Command Prompt in Windows 11, Windows 10, Windows 8, Windows 7, Windows Vista, and Windows XP operating systems. It’s also available in older versions of Windows like Windows 98 and 95.
This command can also be found in Command Prompt in the Advanced Startup Options and System Recovery Options repair/recovery menus.
Ping Command Syntax
The availability of certain ping command switches and other ping command syntax might differ from operating system to operating system.
How to Read Command Syntax
The -f, -v, -r, -s, -j, and -k options work when pinging IPv4 addresses only. The -R and -S options only work with IPv6.
21 Best Command Prompt Tricks
Ping Command Examples
Below are several examples of commands that use ping.
The result displayed in the Command Prompt window will look something like this:
In the above example, we’re pinging 127.0.0.1, also called the IPv4 localhost IP address or IPv4 loopback IP address, without options.
Using the ping command with this address is an excellent way to test that Windows’ network features are working properly but it says nothing about your own network hardware or your connection to any other computer or device. The IPv6 version of this test would be ping ::1.
Find Hostname With Ping
In this example, we’re asking the ping command to find the hostname assigned to the 192.168.1.22 IP address, but to otherwise ping it as normal.
The command might resolve the IP address, 192.168.1.22, as the hostname J3RTY22, for example, and then execute the remainder of the ping with default settings.
Ping Router Command
Similar to the ping command examples above, this one is used to see if your computer can reach your router. The only difference here is that instead of using a ping command switch or pinging the localhost, we’re checking the connection between the computer and the router (192.168.2.1 in this case).
If you’re having trouble logging in to your router or accessing the internet at all, see if your router is accessible with this ping command, of course, replacing 192.168.2.1 with your router’s IP address.
Ping With IPv6
In this example, we force the ping command to use IPv6 with the -6 option and continue to ping SERVER indefinitely with the -t option. You can interrupt the ping manually with Ctrl+C.
The number after the % in the replies generated in this ping command example is the IPv6 Zone ID, which most often indicates the network interface used. You can generate a table of Zone IDs matched with your network interface names by executing netsh interface ipv6 show interface. The IPv6 Zone ID is the number in the Idx column.
Ping Related Commands
The ping command is often used with other networking related Command Prompt commands like tracert, ipconfig, netstat, and nslookup.
Other Ping Uses
You can also use ping on a Linux computer, and third-party ping tools exist as well which offer more features than the basic ping command.
Thanks for letting us know!
Get the Latest Tech News Delivered Every Day
Примеры команд Ping, опции, переключатели и многое другое
Команда ping – это команда командной строки, используемая для проверки способности исходного компьютера достигать указанного конечного компьютера. Команда ping обычно используется как простой способ проверить, может ли компьютер обмениваться данными по сети с другим компьютером или сетевым устройством.
Команда ping работает, отправляя сообщения эхо-запроса протокола управляющих сообщений Интернета (ICMP) на конечный компьютер и ожидая ответа. Сколько из этих ответов возвращено и сколько времени требуется для их возврата – это две основные части информации, которые предоставляет команда ping.
Например, вы можете обнаружить, что при пинге сетевого принтера нет никаких ответов, только чтобы узнать, что принтер отключен и его кабель необходимо заменить. Или, может быть, вам нужно пропинговать маршрутизатор, чтобы убедиться, что ваш компьютер может подключиться к нему, чтобы устранить его как возможную причину проблемы с сетью.
Слово «пинг» также используется в Интернете для обозначения краткого сообщения, обычно через текстовое сообщение или электронную почту. Например, вы можете «пинговать своего босса» или отправить ей сообщение, когда закончите с конкретным проектом, но это не имеет никакого отношения к команде ping.
Доступность команды пинга
Команда ping доступна из командной строки в операционных системах Windows 10, Windows 8, Windows 7, Windows Vista и Windows XP. Команда ping также доступна в более старых версиях Windows, таких как Windows 98 и 95.
Команду ping также можно найти в командной строке в меню «Дополнительные параметры запуска» и «Параметры восстановления системы».
Доступность некоторых переключателей команды ping и другого синтаксиса команды ping может отличаться в зависимости от операционной системы.
Синтаксис команды Ping
См. Как читать синтаксис команды, если вы не уверены, как интерпретировать синтаксис команды ping, как описано выше или в таблице ниже.
Параметры команды Ping
-f , -v , -r , -s , -j и параметры -k работают только при проверке адресов IPv4. Параметры -R и -S работают только с IPv6.
Вы можете сохранить вывод команды ping в файл, используя оператор перенаправления. См. Как перенаправить вывод команды в файл для получения инструкций или посмотрите наш список хитростей командной строки для получения дополнительных советов.
ping -n 5 -l 1500 www.google.com
В этом примере команда ping используется для проверки связи с именем хоста www.google.com . Параметр -n указывает команде ping отправлять 5 ICMP-эхо-запросов вместо значения по умолчанию 4, а параметр -l устанавливает пакет размер каждого запроса 1500 байт вместо 32 байт по умолчанию.
Результат, отображаемый в окне командной строки, будет выглядеть примерно так:
Ответ от 172.217.1.142: байты = 1500 время = 30 мс TTL = 54 Ответ от 172.217.1.142: байты = 1500 время = 30 мс TTL = 54 Ответ от 172.217.1.142: байты = 1500 время = 29 мс TTL = 54 Ответ от 172.217.1.142: байты = 1500 время = 30 мс TTL = 54 Ответ от 172.217.1.142: байт = 1500 раз = 31 мс TTL = 54 Статистика пинга для 172.217.1.142: пакетов: отправлено = 5, получено = 5, Потеря = 0 (потеря 0%), Приблизительное время прохождения сигнала в миллисекундах: Минимум = 29мс, Максимум = 31мс, Среднее = 30мс
Использование команды ping для отправки ping 127.0.0.1 – отличный способ проверить правильность работы сетевых функций Windows, но ничего не говорит о вашем сетевом оборудовании или вашем подключении к любому другому компьютеру или устройству. Версия этого теста для IPv6 будет ping :: 1 .
ping -a 192.168.1.22
Как и в приведенных выше примерах команды ping, этот используется для проверки того, может ли ваш компьютер подключиться к маршрутизатору. Единственное отличие состоит в том, что вместо использования переключателя команды ping или ping на локальном узле мы проверяем соединение между компьютером и маршрутизатором (в данном случае 192.168.2.1 ).
ping -t -6 SERVER
В этом примере мы заставляем команду ping использовать IPv6 с параметром -6 и продолжаем бесконечно пингуем SERVER с параметром -t . Вы можете прервать пинг вручную с помощью Ctrl + C .
Число после % в ответах, сгенерированных в этом примере команды ping, представляет собой идентификатор зоны IPv6, который чаще всего указывает используемый сетевой интерфейс. Вы можете создать таблицу идентификаторов зон, соответствующих именам вашего сетевого интерфейса, выполнив netsh interface ipv6 show interface . Идентификатор зоны IPv6 – это номер в столбце Idx .
Команды, связанные с Ping
Команда ping часто используется с другими командами командной строки, такими как tracert, ipconfig, netstat и nslookup.
Provided by: iputils-ping_20190709-3_amd64
ping will report duplicate and damaged packets. Duplicate packets should never occur, 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.
Damaged packets are obviously serious cause for alarm and often indicate broken hardware
somewhere in the ping packet’s path (in the network or in the hosts).
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 doesn’t have sufficient
“transitions”, such as all ones or all zeros, or a pattern right at the edge, such as
almost all zeros. It isn’t 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.
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 can’t 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 -p
option of ping.
• Many Hosts and Gateways ignore the RECORD_ROUTE option.
• The maximum IP header length is too small for options like RECORD_ROUTE to be
completely useful. There’s not much that can be done about this, however.
• Flood pinging is not recommended in general, and flood pinging the broadcast address
should only be done under very controlled conditions.
The ping command appeared in 4.3BSD.
The version described here is its descendant specific to Linux.
As of version s20150815, the ping6 binary doesn’t exist anymore. It has been merged into
ping. Creating a symlink named ping6 pointing to ping will result in the same funcionality
as before.
ping is part of iputils package.
