display the missing icmp_seq count | ping command
Clash Royale CLAN TAG#URR8PPP
I am looking for something which shows me the missing ICMP
package when running ping command or which can display failed in the output. Example below
Current output where we are missing the icmp_seq count.
64 bytes from 192.168.56.11: icmp_seq=38 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=54 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=55 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=56 ttl=64 time=0.679 ms
Desired Output which will count the icmp_seq if missing then show error
64 bytes from 192.168.56.11: icmp_seq=51 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
Failed
Failed
Failed
Failed
64 bytes from 192.168.56.11: icmp_seq=58 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=59 ttl=64 time=0.679 ms
Failed
Failed
Failed
linux awk grep ping gawk
add a comment |
I am looking for something which shows me the missing ICMP
package when running ping command or which can display failed in the output. Example below
Current output where we are missing the icmp_seq count.
64 bytes from 192.168.56.11: icmp_seq=38 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=54 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=55 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=56 ttl=64 time=0.679 ms
Desired Output which will count the icmp_seq if missing then show error
64 bytes from 192.168.56.11: icmp_seq=51 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
Failed
Failed
Failed
Failed
64 bytes from 192.168.56.11: icmp_seq=58 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=59 ttl=64 time=0.679 ms
Failed
Failed
Failed
linux awk grep ping gawk
add a comment |
I am looking for something which shows me the missing ICMP
package when running ping command or which can display failed in the output. Example below
Current output where we are missing the icmp_seq count.
64 bytes from 192.168.56.11: icmp_seq=38 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=54 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=55 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=56 ttl=64 time=0.679 ms
Desired Output which will count the icmp_seq if missing then show error
64 bytes from 192.168.56.11: icmp_seq=51 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
Failed
Failed
Failed
Failed
64 bytes from 192.168.56.11: icmp_seq=58 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=59 ttl=64 time=0.679 ms
Failed
Failed
Failed
linux awk grep ping gawk
I am looking for something which shows me the missing ICMP
package when running ping command or which can display failed in the output. Example below
Current output where we are missing the icmp_seq count.
64 bytes from 192.168.56.11: icmp_seq=38 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=54 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=55 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=56 ttl=64 time=0.679 ms
Desired Output which will count the icmp_seq if missing then show error
64 bytes from 192.168.56.11: icmp_seq=51 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
Failed
Failed
Failed
Failed
64 bytes from 192.168.56.11: icmp_seq=58 ttl=64 time=0.679 ms
64 bytes from 192.168.56.11: icmp_seq=59 ttl=64 time=0.679 ms
Failed
Failed
Failed
linux awk grep ping gawk
linux awk grep ping gawk
edited Dec 9 '16 at 14:37
asked Dec 9 '16 at 5:11
Mongrel
2,06331445
2,06331445
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
The trick you could use is to create a loop to run the ping
command with the option -c
to send only 1 packet:
while : ; do
ping -c1 -w1 192.168.56.11 | sed -n '/^64 bytes/p;/0 received/s/.*/Failed/p'
done
The -w
is specifying the timeout in second that will be triggered in case of host unreachable.
The sed
command prints the ping output in case of success, and replace the ping output by Failed
in case of failure.
add a comment |
check this code
this just parse the ping output
bash-4.1$ cat ping.awk
#!/usr/bin/awk -f
#
# analyzes ping output on Linux and looks for missed returns
# based on icmp_seq
#
# ping output is expected on stdin
#
BEGIN num = 0
$5 ~ /icmp_seq=/
split($5, res, /=/);
if (res[2] != num + 1)
print "missed between", num, "and", res[2]
num = res[2];
bash-4.1$ cat ping_result.txt
64 bytes from 192.168.56.11: icmp_seq=38 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
bash-4.1$ awk -f ping.awk ping_result.txt
missed between 0 and 38
missed between 38 and 52
Can you provide more information on how to use this script .
– Mongrel
Dec 9 '16 at 9:24
check the modified answer
– Kamaraj
Dec 9 '16 at 9:28
Seems that I need to run theping 192.168.56.11
and capture the log then I need to run the above script which will calculate the output am I right.
– Mongrel
Dec 9 '16 at 9:38
yes.. you are correct
– Kamaraj
Dec 9 '16 at 9:41
I will be having atleast 14 screen which will be monitored & We need real time ping failed
– Mongrel
Dec 9 '16 at 9:49
|
show 4 more comments
So far I have managed to write the below command. I can run it in background & tailf
the file which is getting created.
[root@connect ~]# touch result.txt; while true; do ping -c 1 -w 2 192.168.56.11 || echo “`date` ping faild” >> result.txt; sleep 1; done
add a comment |
On Linux, could use:
fping -l google.com
The above command will show statistics:
- Average elapsed time for each request.
- Percentage of package lost overall.
Sample output
google.com : [160], 84 bytes, 32.0 ms (39.1 avg, 0% loss)
google.com : [161], 84 bytes, 32.3 ms (39.1 avg, 0% loss)
google.com : [162], 84 bytes, 33.8 ms (39.1 avg, 0% loss)
google.com : [163], 84 bytes, 31.3 ms (39.0 avg, 0% loss)
google.com : [164], 84 bytes, 32.8 ms (39.0 avg, 0% loss)
google.com : [165], 84 bytes, 37.3 ms (39.0 avg, 0% loss)
google.com : [166], 84 bytes, 32.4 ms (38.9 avg, 0% loss)
google.com : [167], 84 bytes, 36.1 ms (38.9 avg, 0% loss)
google.com : [168], 84 bytes, 32.8 ms (38.9 avg, 0% loss)
google.com : [169], 84 bytes, 33.8 ms (38.8 avg, 0% loss)
google.com : [170], 84 bytes, 32.6 ms (38.8 avg, 0% loss)
google.com : [171], 84 bytes, 33.0 ms (38.8 avg, 0% loss)
google.com : [172], 84 bytes, 33.2 ms (38.7 avg, 0% loss)
^C
google.com : xmt/rcv/%loss = 173/173/0%, min/avg/max = 31.3/38.7/261
Tips:
ctrl + c
to stop it, and it will show an additional line of statistics, include:
package sent / package received / lost percentage, min/avg/max of elapse time.
Install
It's not installed by default, could install it via:
- Ubuntu / Mint
sudo apt install fping
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f329110%2fdisplay-the-missing-icmp-seq-count-ping-command%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
The trick you could use is to create a loop to run the ping
command with the option -c
to send only 1 packet:
while : ; do
ping -c1 -w1 192.168.56.11 | sed -n '/^64 bytes/p;/0 received/s/.*/Failed/p'
done
The -w
is specifying the timeout in second that will be triggered in case of host unreachable.
The sed
command prints the ping output in case of success, and replace the ping output by Failed
in case of failure.
add a comment |
The trick you could use is to create a loop to run the ping
command with the option -c
to send only 1 packet:
while : ; do
ping -c1 -w1 192.168.56.11 | sed -n '/^64 bytes/p;/0 received/s/.*/Failed/p'
done
The -w
is specifying the timeout in second that will be triggered in case of host unreachable.
The sed
command prints the ping output in case of success, and replace the ping output by Failed
in case of failure.
add a comment |
The trick you could use is to create a loop to run the ping
command with the option -c
to send only 1 packet:
while : ; do
ping -c1 -w1 192.168.56.11 | sed -n '/^64 bytes/p;/0 received/s/.*/Failed/p'
done
The -w
is specifying the timeout in second that will be triggered in case of host unreachable.
The sed
command prints the ping output in case of success, and replace the ping output by Failed
in case of failure.
The trick you could use is to create a loop to run the ping
command with the option -c
to send only 1 packet:
while : ; do
ping -c1 -w1 192.168.56.11 | sed -n '/^64 bytes/p;/0 received/s/.*/Failed/p'
done
The -w
is specifying the timeout in second that will be triggered in case of host unreachable.
The sed
command prints the ping output in case of success, and replace the ping output by Failed
in case of failure.
answered Dec 9 '16 at 7:59
oliv
1,651311
1,651311
add a comment |
add a comment |
check this code
this just parse the ping output
bash-4.1$ cat ping.awk
#!/usr/bin/awk -f
#
# analyzes ping output on Linux and looks for missed returns
# based on icmp_seq
#
# ping output is expected on stdin
#
BEGIN num = 0
$5 ~ /icmp_seq=/
split($5, res, /=/);
if (res[2] != num + 1)
print "missed between", num, "and", res[2]
num = res[2];
bash-4.1$ cat ping_result.txt
64 bytes from 192.168.56.11: icmp_seq=38 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
bash-4.1$ awk -f ping.awk ping_result.txt
missed between 0 and 38
missed between 38 and 52
Can you provide more information on how to use this script .
– Mongrel
Dec 9 '16 at 9:24
check the modified answer
– Kamaraj
Dec 9 '16 at 9:28
Seems that I need to run theping 192.168.56.11
and capture the log then I need to run the above script which will calculate the output am I right.
– Mongrel
Dec 9 '16 at 9:38
yes.. you are correct
– Kamaraj
Dec 9 '16 at 9:41
I will be having atleast 14 screen which will be monitored & We need real time ping failed
– Mongrel
Dec 9 '16 at 9:49
|
show 4 more comments
check this code
this just parse the ping output
bash-4.1$ cat ping.awk
#!/usr/bin/awk -f
#
# analyzes ping output on Linux and looks for missed returns
# based on icmp_seq
#
# ping output is expected on stdin
#
BEGIN num = 0
$5 ~ /icmp_seq=/
split($5, res, /=/);
if (res[2] != num + 1)
print "missed between", num, "and", res[2]
num = res[2];
bash-4.1$ cat ping_result.txt
64 bytes from 192.168.56.11: icmp_seq=38 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
bash-4.1$ awk -f ping.awk ping_result.txt
missed between 0 and 38
missed between 38 and 52
Can you provide more information on how to use this script .
– Mongrel
Dec 9 '16 at 9:24
check the modified answer
– Kamaraj
Dec 9 '16 at 9:28
Seems that I need to run theping 192.168.56.11
and capture the log then I need to run the above script which will calculate the output am I right.
– Mongrel
Dec 9 '16 at 9:38
yes.. you are correct
– Kamaraj
Dec 9 '16 at 9:41
I will be having atleast 14 screen which will be monitored & We need real time ping failed
– Mongrel
Dec 9 '16 at 9:49
|
show 4 more comments
check this code
this just parse the ping output
bash-4.1$ cat ping.awk
#!/usr/bin/awk -f
#
# analyzes ping output on Linux and looks for missed returns
# based on icmp_seq
#
# ping output is expected on stdin
#
BEGIN num = 0
$5 ~ /icmp_seq=/
split($5, res, /=/);
if (res[2] != num + 1)
print "missed between", num, "and", res[2]
num = res[2];
bash-4.1$ cat ping_result.txt
64 bytes from 192.168.56.11: icmp_seq=38 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
bash-4.1$ awk -f ping.awk ping_result.txt
missed between 0 and 38
missed between 38 and 52
check this code
this just parse the ping output
bash-4.1$ cat ping.awk
#!/usr/bin/awk -f
#
# analyzes ping output on Linux and looks for missed returns
# based on icmp_seq
#
# ping output is expected on stdin
#
BEGIN num = 0
$5 ~ /icmp_seq=/
split($5, res, /=/);
if (res[2] != num + 1)
print "missed between", num, "and", res[2]
num = res[2];
bash-4.1$ cat ping_result.txt
64 bytes from 192.168.56.11: icmp_seq=38 ttl=64 time=1.23 ms
64 bytes from 192.168.56.11: icmp_seq=52 ttl=64 time=0.831 ms
64 bytes from 192.168.56.11: icmp_seq=53 ttl=64 time=0.679 ms
bash-4.1$ awk -f ping.awk ping_result.txt
missed between 0 and 38
missed between 38 and 52
edited Dec 9 '16 at 9:27
answered Dec 9 '16 at 6:39
Kamaraj
2,9461513
2,9461513
Can you provide more information on how to use this script .
– Mongrel
Dec 9 '16 at 9:24
check the modified answer
– Kamaraj
Dec 9 '16 at 9:28
Seems that I need to run theping 192.168.56.11
and capture the log then I need to run the above script which will calculate the output am I right.
– Mongrel
Dec 9 '16 at 9:38
yes.. you are correct
– Kamaraj
Dec 9 '16 at 9:41
I will be having atleast 14 screen which will be monitored & We need real time ping failed
– Mongrel
Dec 9 '16 at 9:49
|
show 4 more comments
Can you provide more information on how to use this script .
– Mongrel
Dec 9 '16 at 9:24
check the modified answer
– Kamaraj
Dec 9 '16 at 9:28
Seems that I need to run theping 192.168.56.11
and capture the log then I need to run the above script which will calculate the output am I right.
– Mongrel
Dec 9 '16 at 9:38
yes.. you are correct
– Kamaraj
Dec 9 '16 at 9:41
I will be having atleast 14 screen which will be monitored & We need real time ping failed
– Mongrel
Dec 9 '16 at 9:49
Can you provide more information on how to use this script .
– Mongrel
Dec 9 '16 at 9:24
Can you provide more information on how to use this script .
– Mongrel
Dec 9 '16 at 9:24
check the modified answer
– Kamaraj
Dec 9 '16 at 9:28
check the modified answer
– Kamaraj
Dec 9 '16 at 9:28
Seems that I need to run the
ping 192.168.56.11
and capture the log then I need to run the above script which will calculate the output am I right.– Mongrel
Dec 9 '16 at 9:38
Seems that I need to run the
ping 192.168.56.11
and capture the log then I need to run the above script which will calculate the output am I right.– Mongrel
Dec 9 '16 at 9:38
yes.. you are correct
– Kamaraj
Dec 9 '16 at 9:41
yes.. you are correct
– Kamaraj
Dec 9 '16 at 9:41
I will be having atleast 14 screen which will be monitored & We need real time ping failed
– Mongrel
Dec 9 '16 at 9:49
I will be having atleast 14 screen which will be monitored & We need real time ping failed
– Mongrel
Dec 9 '16 at 9:49
|
show 4 more comments
So far I have managed to write the below command. I can run it in background & tailf
the file which is getting created.
[root@connect ~]# touch result.txt; while true; do ping -c 1 -w 2 192.168.56.11 || echo “`date` ping faild” >> result.txt; sleep 1; done
add a comment |
So far I have managed to write the below command. I can run it in background & tailf
the file which is getting created.
[root@connect ~]# touch result.txt; while true; do ping -c 1 -w 2 192.168.56.11 || echo “`date` ping faild” >> result.txt; sleep 1; done
add a comment |
So far I have managed to write the below command. I can run it in background & tailf
the file which is getting created.
[root@connect ~]# touch result.txt; while true; do ping -c 1 -w 2 192.168.56.11 || echo “`date` ping faild” >> result.txt; sleep 1; done
So far I have managed to write the below command. I can run it in background & tailf
the file which is getting created.
[root@connect ~]# touch result.txt; while true; do ping -c 1 -w 2 192.168.56.11 || echo “`date` ping faild” >> result.txt; sleep 1; done
answered Dec 15 '16 at 3:13
Mongrel
2,06331445
2,06331445
add a comment |
add a comment |
On Linux, could use:
fping -l google.com
The above command will show statistics:
- Average elapsed time for each request.
- Percentage of package lost overall.
Sample output
google.com : [160], 84 bytes, 32.0 ms (39.1 avg, 0% loss)
google.com : [161], 84 bytes, 32.3 ms (39.1 avg, 0% loss)
google.com : [162], 84 bytes, 33.8 ms (39.1 avg, 0% loss)
google.com : [163], 84 bytes, 31.3 ms (39.0 avg, 0% loss)
google.com : [164], 84 bytes, 32.8 ms (39.0 avg, 0% loss)
google.com : [165], 84 bytes, 37.3 ms (39.0 avg, 0% loss)
google.com : [166], 84 bytes, 32.4 ms (38.9 avg, 0% loss)
google.com : [167], 84 bytes, 36.1 ms (38.9 avg, 0% loss)
google.com : [168], 84 bytes, 32.8 ms (38.9 avg, 0% loss)
google.com : [169], 84 bytes, 33.8 ms (38.8 avg, 0% loss)
google.com : [170], 84 bytes, 32.6 ms (38.8 avg, 0% loss)
google.com : [171], 84 bytes, 33.0 ms (38.8 avg, 0% loss)
google.com : [172], 84 bytes, 33.2 ms (38.7 avg, 0% loss)
^C
google.com : xmt/rcv/%loss = 173/173/0%, min/avg/max = 31.3/38.7/261
Tips:
ctrl + c
to stop it, and it will show an additional line of statistics, include:
package sent / package received / lost percentage, min/avg/max of elapse time.
Install
It's not installed by default, could install it via:
- Ubuntu / Mint
sudo apt install fping
add a comment |
On Linux, could use:
fping -l google.com
The above command will show statistics:
- Average elapsed time for each request.
- Percentage of package lost overall.
Sample output
google.com : [160], 84 bytes, 32.0 ms (39.1 avg, 0% loss)
google.com : [161], 84 bytes, 32.3 ms (39.1 avg, 0% loss)
google.com : [162], 84 bytes, 33.8 ms (39.1 avg, 0% loss)
google.com : [163], 84 bytes, 31.3 ms (39.0 avg, 0% loss)
google.com : [164], 84 bytes, 32.8 ms (39.0 avg, 0% loss)
google.com : [165], 84 bytes, 37.3 ms (39.0 avg, 0% loss)
google.com : [166], 84 bytes, 32.4 ms (38.9 avg, 0% loss)
google.com : [167], 84 bytes, 36.1 ms (38.9 avg, 0% loss)
google.com : [168], 84 bytes, 32.8 ms (38.9 avg, 0% loss)
google.com : [169], 84 bytes, 33.8 ms (38.8 avg, 0% loss)
google.com : [170], 84 bytes, 32.6 ms (38.8 avg, 0% loss)
google.com : [171], 84 bytes, 33.0 ms (38.8 avg, 0% loss)
google.com : [172], 84 bytes, 33.2 ms (38.7 avg, 0% loss)
^C
google.com : xmt/rcv/%loss = 173/173/0%, min/avg/max = 31.3/38.7/261
Tips:
ctrl + c
to stop it, and it will show an additional line of statistics, include:
package sent / package received / lost percentage, min/avg/max of elapse time.
Install
It's not installed by default, could install it via:
- Ubuntu / Mint
sudo apt install fping
add a comment |
On Linux, could use:
fping -l google.com
The above command will show statistics:
- Average elapsed time for each request.
- Percentage of package lost overall.
Sample output
google.com : [160], 84 bytes, 32.0 ms (39.1 avg, 0% loss)
google.com : [161], 84 bytes, 32.3 ms (39.1 avg, 0% loss)
google.com : [162], 84 bytes, 33.8 ms (39.1 avg, 0% loss)
google.com : [163], 84 bytes, 31.3 ms (39.0 avg, 0% loss)
google.com : [164], 84 bytes, 32.8 ms (39.0 avg, 0% loss)
google.com : [165], 84 bytes, 37.3 ms (39.0 avg, 0% loss)
google.com : [166], 84 bytes, 32.4 ms (38.9 avg, 0% loss)
google.com : [167], 84 bytes, 36.1 ms (38.9 avg, 0% loss)
google.com : [168], 84 bytes, 32.8 ms (38.9 avg, 0% loss)
google.com : [169], 84 bytes, 33.8 ms (38.8 avg, 0% loss)
google.com : [170], 84 bytes, 32.6 ms (38.8 avg, 0% loss)
google.com : [171], 84 bytes, 33.0 ms (38.8 avg, 0% loss)
google.com : [172], 84 bytes, 33.2 ms (38.7 avg, 0% loss)
^C
google.com : xmt/rcv/%loss = 173/173/0%, min/avg/max = 31.3/38.7/261
Tips:
ctrl + c
to stop it, and it will show an additional line of statistics, include:
package sent / package received / lost percentage, min/avg/max of elapse time.
Install
It's not installed by default, could install it via:
- Ubuntu / Mint
sudo apt install fping
On Linux, could use:
fping -l google.com
The above command will show statistics:
- Average elapsed time for each request.
- Percentage of package lost overall.
Sample output
google.com : [160], 84 bytes, 32.0 ms (39.1 avg, 0% loss)
google.com : [161], 84 bytes, 32.3 ms (39.1 avg, 0% loss)
google.com : [162], 84 bytes, 33.8 ms (39.1 avg, 0% loss)
google.com : [163], 84 bytes, 31.3 ms (39.0 avg, 0% loss)
google.com : [164], 84 bytes, 32.8 ms (39.0 avg, 0% loss)
google.com : [165], 84 bytes, 37.3 ms (39.0 avg, 0% loss)
google.com : [166], 84 bytes, 32.4 ms (38.9 avg, 0% loss)
google.com : [167], 84 bytes, 36.1 ms (38.9 avg, 0% loss)
google.com : [168], 84 bytes, 32.8 ms (38.9 avg, 0% loss)
google.com : [169], 84 bytes, 33.8 ms (38.8 avg, 0% loss)
google.com : [170], 84 bytes, 32.6 ms (38.8 avg, 0% loss)
google.com : [171], 84 bytes, 33.0 ms (38.8 avg, 0% loss)
google.com : [172], 84 bytes, 33.2 ms (38.7 avg, 0% loss)
^C
google.com : xmt/rcv/%loss = 173/173/0%, min/avg/max = 31.3/38.7/261
Tips:
ctrl + c
to stop it, and it will show an additional line of statistics, include:
package sent / package received / lost percentage, min/avg/max of elapse time.
Install
It's not installed by default, could install it via:
- Ubuntu / Mint
sudo apt install fping
answered Dec 22 '18 at 8:53
Eric Wang
18418
18418
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f329110%2fdisplay-the-missing-icmp-seq-count-ping-command%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown