Ping -r results are confusing

ping

As you know, "ping -r" displays hops (maximum 9 hops) between your computer and destination (as tracert does).

Using this command, in many cases, I get "request timeOut" (first pic) while by using simple ping command, I get all the replies (second pic).

Note, based on my captures, there is no difference between packets generated by "ping -r" and simple ping commands.

Now, why??!!!!

enter image description here

enter image description here

Best Answer

ping -r adds RECORD_ROUTE flags in packet which many hosts ignoring this flag. Is not recommended tool to check path route. I would use instead traceroute or mtr. And is only supporting up to 9 hops. If destination is farther than 9 hops this will fail. As manual says:

>      -R     Record route. (IPv4 only) Includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on  returned 
> packets.   Note
>               that the IP header is only large enough for nine such routes.  Many hosts ignore or discard this option.
Related Topic