Ping: Unterschied zwischen den Versionen
| Zeile 98: | Zeile 98: | ||
3 packets transmitted, 3 received, 0% packet loss, time 2001ms | 3 packets transmitted, 3 received, 0% packet loss, time 2001ms | ||
rtt min/avg/max/mdev = 22.685/24.664/28.471/2.692 ms | rtt min/avg/max/mdev = 22.685/24.664/28.471/2.692 ms | ||
== Anwendung == | == Anwendung == | ||
Version vom 27. Februar 2024, 19:56 Uhr
ping - Prüft die Erreichbarkeit eines Netzwerkknotens durch Senden eines ICMP ECHO_REQUEST
Beschreibung
- packed internet grouper
- Prüft die Erreichbarkeit eines Netzwerkknotens durch Senden eines ICMP ECHO_REQUEST
Installation
ping ist Teil des Pakets iputils-ping, das in jeder Installation enthalten sein sollte.
# apt install iputils-ping Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig iputils-ping ist schon die neueste Version (3:20211215-1). 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Syntax
Optionen
| Option | Beschreibung |
|---|---|
| -4 | Use IPv4 only. |
| -6 | Use IPv6 only. |
| -a | Audible ping. |
| -A | Adaptive ping. Interpacket interval adapts to round-trip time, so that effectively not more than one (or more, if preload is set) unanswered
probe is present in the network. Minimal interval is 200msec unless super-user. On networks with low RTT this mode is essentially equivalent to flood mode. |
| -b | Allow pinging a broadcast address. |
| -B | Do not allow ping to change source address of probes. The address is bound to one selected when ping starts. |
| -c count | Stop after sending count ECHO_REQUEST packets. With deadline option, ping waits for count ECHO_REPLY packets, until the timeout expires. |
| -d | Set the SO_DEBUG option on the socket being used. Essentially, this socket option is not used by Linux kernel. |
| -D | Print timestamp (unix time + microseconds as in gettimeofday) before each line. |
| -f | Flood ping. For every ECHO_REQUEST sent a period “.” is printed, while for every ECHO_REPLY received a backspace is printed. This provides a
rapid display of how many packets are being dropped. If interval is not given, it sets interval to zero and outputs packets as fast as they come back or one hundred times per second, whichever is more. Only the super-user may use this option with zero interval. |
| -F flow label | IPv6 only. Allocate and set 20 bit flow label (in hex) on echo request packets. If value is zero, kernel allocates random flow label. |
| -h | Show help. |
| -i interval | Wait interval seconds between sending each packet. Real number allowed with dot as a decimal separator (regardless locale setup). The default
is to wait for one second between each packet normally, or not to wait in flood mode. Only super-user may set interval to values less than 0.2 seconds. |
| -I interface | interface is either an address, an interface name or a VRF name. If interface is an address, it sets source address to specified interface
address. If interface is an interface name, it sets source interface to specified interface. If interface is a VRF name, each packet is routed using the corresponding routing table; in this case, the -I option can be repeated to specify a source address. NOTE: For IPv6, when doing ping to a link-local scope address, link specification (by the '%'-notation in destination, or by this option) can be used but it is no longer required. |
| -l preload | If preload is specified, ping sends that many packets not waiting for reply. Only the super-user may select preload more than 3. |
| -L | Suppress loopback of multicast packets. This flag only applies if the ping destination is a multicast address. |
| -m mark | use mark to tag the packets going out. This is useful for variety of reasons within the kernel such as using policy routing to select
specific outbound processing. |
| -M pmtudisc_opt | Select Path MTU Discovery strategy. pmtudisc_option 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). |
| -N nodeinfo_option | IPv6 only. Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request. CAP_NET_RAW capability is required. |
Parameter
Umgebungsvariablen
Exit-Status
Syntax
ping [-aAbBdDfhLnOqrRUvV46] [-c count] [-F flowlabel] [-i interval] [-I interface] [-l preload]
[-m mark] [-M pmtudisc_option] [-N nodeinfo_option] [-w deadline] [-W timeout] [-p pattern]
[-Q tos] [-s packetsize] [-S sndbuf] [-t ttl] [-T timestamp option] [hop...] {destination}
Anstelle der IP-Adresse kann auch ein Host-Name angegeben werden. Es wird dann versucht, diesen in eine DNS-Adresse aufzulösen.
$ ping OPTIONEN 10.10.0.1
Man muss ping entweder händisch stoppen (mit Strg + C ) oder mit der entsprechenden Option die Anzahl der gesendeten Pakete begrenzen.
Es gibt zwei Varianten des ping-Befehl
- ping - für IPv4-Adressen
- ping6 - für IPv6-Adressen
$ ping foxtom.de PING foxtom.de (116.202.118.50) 56(84) bytes of data. 64 bytes from mx10.foxtom.de (116.202.118.50): icmp_seq=1 ttl=54 time=28.5 ms 64 bytes from mx10.foxtom.de (116.202.118.50): icmp_seq=2 ttl=54 time=22.7 ms 64 bytes from mx10.foxtom.de (116.202.118.50): icmp_seq=3 ttl=54 time=22.8 ms ^C --- foxtom.de ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 22.685/24.664/28.471/2.692 ms
Anwendung
Fehlerbehebung
Konfiguration
Dateien
Anhang
Siehe auch
Sicherheit
Dokumentation
RFC
| RFC | Titel |
|---|---|
| 0000 |
Man-Pages
Info-Pages
Links
Projekt
Weblinks
TMP
Konfiguration
Dateien
Anwendung
-c ANZAHL
$ ping -c 10 foxtom.de
-w ENDE
$ ping -w 15 foxtom.de
-W AUSZEIT
$ ping -W 015 foxtom.de
-i INTERVALL
$ ping -i 15 foxtom.de
-I SCHNITTSTELLE
$ ping -I enp2s0 ($ ip a)foxtom.de
Ping und MTU
- Die im Befehl ping angegebene Größe entspricht der Anzahl der zu sendenden Datenbytes.
- Diese muss also 28 Byte kleiner sein als die tatsächliche Paketgröße, um die Größe des Paket-Headers zu berücksichtigen.
- Dieser lässt sich recht einfach über Bordmittel des Betriebssystems bestimmen.
siehe MTU
Beispiel
$ ping -s 1500 -c 10 -M do <Hostname>
Fehlerbehung
Ping 127.
- https://rixx.de/blog/fun-legacy-ip-addresses/
- https://bugzilla.mozilla.org/show_bug.cgi?id=160819
- https://www.reddit.com/r/sysadmin/comments/11weum/can_someone_explain_how_this_works_ping_1271/?rdt=50191
- https://www.quora.com/Is-127-1-a-valid-IP-address
Dokumentation
Man-Pages
Info-Pages
Links
Intern
Weblinks
TMP
ping
ping prüft die Verbindung zu einem Zielsystem, indem es einen Echo Request sendet und einen Echo Reply erwartet
$ ping google.de PING google.de(ham02s17-in-x03.1e100.net (2a00:1450:4005:80b::2003)) 56 data bytes 64 bytes from ham02s17-in-x03.1e100.net (2a00:1450:4005:80b::2003): icmp_seq=1 ttl=119 time=25.7 ms 64 bytes from ham02s17-in-x03.1e100.net (2a00:1450:4005:80b::2003): icmp_seq=2 ttl=119 time=22.9 ms 64 bytes from ham02s17-in-x03.1e100.net (2a00:1450:4005:80b::2003): icmp_seq=3 ttl=119 time=22.6 ms 64 bytes from ham02s17-in-x03.1e100.net (2a00:1450:4005:80b::2003): icmp_seq=4 ttl=119 time=22.9 ms 64 bytes from ham02s17-in-x03.1e100.net (2a00:1450:4005:80b::2003): icmp_seq=5 ttl=119 time=23.1 ms ^C --- google.de ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 22.572/23.416/25.650/1.130 ms
