Ping shows (DUP!) reply

Solution Verified - Updated -

Issue

  • While performing a ping from the source server to the destination server, duplicate ICMP reply packets (DUP!) are observed on the source side.
64 bytes from 198.51.100.55: icmp_seq=43 ttl=61 time=1.64 ms
64 bytes from 198.51.100.55: icmp_seq=43 ttl=61 time=1.66 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=43 ttl=61 time=1.68 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=43 ttl=61 time=1.20 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=43 ttl=61 time=1.80 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=44 ttl=61 time=0.921 ms
64 bytes from 198.51.100.55: icmp_seq=44 ttl=61 time=0.846 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=44 ttl=61 time=0.956 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=44 ttl=61 time=0.916 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=44 ttl=61 time=0.885 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=45 ttl=61 time=0.686 ms
64 bytes from 198.51.100.55: icmp_seq=45 ttl=61 time=0.708 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=45 ttl=61 time=0.728 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=45 ttl=61 time=0.798 ms (DUP!)
64 bytes from 198.51.100.55: icmp_seq=45 ttl=61 time=0.812 ms (DUP!)

Environment

Red Hat Enterprise Linux (All Version)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content