Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 309
  • Last Modified:

Ping: reply from an intermediate system.

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

ping Output:

64 bytes from p15.www.scd.yahoo.com (66.94.230.46): icmp_seq=2038 ttl=49 time=253 ms
64 bytes from p15.www.scd.yahoo.com (66.94.230.46): icmp_seq=2039 ttl=50 time=257 ms
64 bytes from p15.www.scd.yahoo.com (66.94.230.46): icmp_seq=2040 ttl=50 time=264 ms
From if-6-0.core2.PDI-PaloAlto.teleglobe.net (63.243.156.1) icmp_seq=2049 Time to live exceeded
From if-6-0.core2.PDI-PaloAlto.teleglobe.net (63.243.156.1) icmp_seq=2050 Time to live exceeded
From if-6-0.core2.PDI-PaloAlto.teleglobe.net (63.243.156.1) icmp_seq=2051 Time to live exceeded
From Vlan2.msfc1.AEQ-Ashburn.Teleglobe.net (64.86.81.195) icmp_seq=2052 Time to live exceeded
From 59.145.11.70 icmp_seq=2076 Time to live exceeded
64 bytes from p15.www.scd.yahoo.com (66.94.230.46): icmp_seq=2092 ttl=50 time=257 ms
64 bytes from p15.www.scd.yahoo.com (66.94.230.46): icmp_seq=2093 ttl=50 time=256 ms
64 bytes from p15.www.scd.yahoo.com (66.94.230.46): icmp_seq=2110 ttl=49 time=250 ms
64 bytes from p15.www.scd.yahoo.com (66.94.230.46): icmp_seq=2111 ttl=48 time=250 ms


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

Could anyone explain me what exactly happened in the middle?

Thanks,
expertblr
0
expertblr
Asked:
expertblr
  • 2
  • 2
1 Solution
 
ravenplCommented:
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.
0
 
expertblrAuthor Commented:
But, I want to know why the TTL was dropped? Any specific reason?
0
 
ravenplCommented:
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.
0
 
expertblrAuthor Commented:
Thank you!!
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now