Large RTT or Why doesn't my ping traffic get discarded?
jhellenthal at dataix.net
Wed Dec 21 21:21:03 UTC 2022
As well if this persists you may consider disabling hardware rx/tx checksumming to see if it clears up your results. Some net cards can get glitchy causing this exact behavior.
The fact that there's a highway to Hell but only a stairway to Heaven says a lot about anticipated traffic volume.
> On Dec 21, 2022, at 13:58, William Herrin <bill at herrin.us> wrote:
> On Wed, Dec 21, 2022 at 9:10 AM Jason Iannone <jason.iannone at gmail.com> wrote:
>> Here's a question I haven't bothered to ask until now. Can someone please help me understand why I receive a ping reply after almost 5 seconds?
>> 64 bytes from 18.104.22.168: icmp_seq=398 ttl=54 time=4915.096 ms
>> 64 bytes from 22.214.171.124: icmp_seq=399 ttl=54 time=4310.575 ms
>> 64 bytes from 126.96.36.199: icmp_seq=400 ttl=54 time=4196.075 ms
>> 64 bytes from 188.8.131.52: icmp_seq=401 ttl=54 time=4287.048 ms
>> 64 bytes from 184.108.40.206: icmp_seq=403 ttl=54 time=2280.466 ms
>> 64 bytes from 220.127.116.11: icmp_seq=404 ttl=54 time=1279.348 ms
>> 64 bytes from 18.104.22.168: icmp_seq=405 ttl=54 time=276.669 ms
> Hi Jason,
> This usually means a problem on the Linux machine originating the
> packet. It has lost the ARP for the next hop or something similar so
> the outbound ICMP packet is queued. The glitch repairs itself,
> briefly, releasing the queued packets. Then it comes right back.
> Bill Herrin
> For hire. https://bill.herrin.us/resume/
More information about the NANOG