I'm having trouble with the record route (-R) option of the ping command in Linux. It appears that when I run the command without this option, I am able to receive a response from a range of servers (commercial websites like Google, Yahoo etc. as well as internal servers within my campus network). However when I use the -R option, it gives me 100% packet loss for ALL of these. For example, when I run ping www.google.com.au it behaves as expected, giving responses until I terminate it. But when I run ping -R www.google.com.au, it just waits forever, sending packets but not printing anything on the screen. Then when I terminate it forcefully, it shows something like this: 130 packets transmitted, 0 received, 100% packet loss, time 128999ms
The same thing happens for all hosts that I try to ping. Also I've tried from a range of machines in different places so it can't be a firewall issue. Can someone tell me why the record route option messes up the ping?
Cheers.
Best Answer
Try traceroute or mtr.
They should both give you what you are after. The -R option is ping is not widely known/supported. 3