I am stuck at a very strange result after running the command ping -R in a unix environment. To be more specific, I am trying to follow the path to a server and back but there is quite a mismach between the results from running this command and the traceroute to the same server. Why is that? I am already familiar with the concept of ping -R command and have actually read the manual page very thoroughly, however, I had no luck in expldaining to myself why that could happen. Any suggestions would be much appreciated as I am really confused. Thanks
Tell me more
×
Server Fault is a question and answer site for
professional system and network administrators. It's 100% free, no registration required.
|
|
|||||||||||
|
|
Ping -r displays outgoing IP addresses, i.e. addresses when leaving the routers, while traceroute displays addresses when entering the routers. If the 9-address limit of ping -r is sufficient to display all the addresses encountered in a round trip, you can see first the addresses opposite to you, then the addresses towards you. With traceroute you only see the addresses towards you. |
|||
|
|
|
Ping uses ICMP, traceroute uses UDP? Not sure why that would make a difference though, it all rides on IP. Does your traceroute have an option to use ICMP ECHO instead of UDP datagrams? If so, try that and see if it gives you the same answer. Maybe per-flow route caching? |
||||
|