in reply to Re: 209.197.123.153 Down
in thread 209.197.123.153 Down

I ran a ping on that and arbitrarily killed it (Ctrl-C) midway through the 10th packet (causing received packet loss).

Most (all?) variants of ping take the -c flag which lets you specify in advance how many packets to send. Adjust the value to suit your own patience level. eg:

$ ping -n -c 5 66.39.54.27 PING 66.39.54.27 (66.39.54.27) 56(84) bytes of data. 64 bytes from 66.39.54.27: icmp_seq=1 ttl=57 time=92.0 ms 64 bytes from 66.39.54.27: icmp_seq=2 ttl=57 time=92.5 ms 64 bytes from 66.39.54.27: icmp_seq=3 ttl=57 time=92.8 ms 64 bytes from 66.39.54.27: icmp_seq=4 ttl=57 time=91.5 ms 64 bytes from 66.39.54.27: icmp_seq=5 ttl=57 time=91.8 ms --- 66.39.54.27 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 91.522/92.123/92.783/0.465 ms $

🦛

Replies are listed 'Best First'.
Re^3: 209.197.123.153 Down
by kcott (Archbishop) on Jan 24, 2024 at 15:18 UTC

    ++ Thanks.

    I was aware that such a flag existed but couldn't remember what it was. At 2am I was too lazy to type man ping for what was intended as a quick check.

    As is often the case, this short-cut became a long-cut: typing an explanation for Ctrl-C turned out to be more work. 😳

    — Ken