extended ping - source:?

Unanswered Question
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Collin Clark Fri, 01/05/2007 - 14:31
User Badges:
  • Purple, 4500 points or more

How could you ever get a reply if you used a source other than the router? You use other source interfaces for testing NAT, ACLs etc. If it replies on the source interface theres a good chance it will respond from a client beyond it, validating your config.

sundar.palaniappan Fri, 01/05/2007 - 14:37
User Badges:
  • Green, 3000 points or more

By default, ping(s) originated from the router would source the egress (outbound) interface IP. Instead, you can choose a difference interface/IP to be the source to test network connectivity between that subnet and the destination.

Sourcing the IP of another device on the network would be using a duplicate address and the IOS wouldn't facilitate that function. What if an alternate route (eg, host route) exists to the actual source itself then the echo-replies wouldn't make it back to the router and would make you believe there's a network connectivity problem when, actually, there is no problem.



Richard Burts Tue, 01/30/2007 - 19:31
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN


Thank you for clarifying the context of your question. And score another one (-1 actually) for those people who write the certification questions based on a half understanding of what the material is talking about.

I would agree that some of the official documentation is slightly vague about what the source address of extended ping really is. And someone expanded on what they thought that meant. And the reality is that extended ping will only accept source addresses that are interface addresses on that router (and the justification for the restriction is well explained by several of the previous posts).




This Discussion