Ping: reply from an intermediate system.

   I'm using RH9.0. I'm getting the bwlow output while pinging  to yahoo.

ping Output:

64 bytes from ( icmp_seq=2038 ttl=49 time=253 ms
64 bytes from ( icmp_seq=2039 ttl=50 time=257 ms
64 bytes from ( icmp_seq=2040 ttl=50 time=264 ms
From ( icmp_seq=2049 Time to live exceeded
From ( icmp_seq=2050 Time to live exceeded
From ( icmp_seq=2051 Time to live exceeded
From ( icmp_seq=2052 Time to live exceeded
From icmp_seq=2076 Time to live exceeded
64 bytes from ( icmp_seq=2092 ttl=50 time=257 ms
64 bytes from ( icmp_seq=2093 ttl=50 time=256 ms
64 bytes from ( icmp_seq=2110 ttl=49 time=250 ms
64 bytes from ( icmp_seq=2111 ttl=48 time=250 ms

My doubt is, we see a reply from with icmp_seq 2049-2052 and another reply form  with icmp_seq 2076 both displaying Time to live exceeded.

Could anyone explain me what exactly happened in the middle?

Who is Participating?
the TTL is dropped (decreased by one) on each router. Possibly on bridge/routing switch also.
If TTL reaches zero, 'Time to live exceeded' is sent back to sender and the packet is dropped.
It's very propable, that routing loop was detected and we avoilded keeping this packed live forever.
Routing in WAN is not static as You used to in LAN. Packets can take different ways.
The simplest scenario is load balancing over two lines, where one of those lines have additional router(or other device) which drops the TTL counter.
expertblrAuthor Commented:
But, I want to know why the TTL was dropped? Any specific reason?
expertblrAuthor Commented:
Thank you!!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.