Traceroute.pl problems

Tests

• Does the form come up?
• Can one execute traceroute from the command line?
• Can one execute traceroute -I from the command line , it needs sudo?
• Can one execute traceroiute -m 30 -q 3 from the command line (see below)?. The option m gives the maximum number of hops, the option q gives the number of probes/hop.
• Is the server for traceroute.pl on a local address, for example does traceroute.pl?target=www.cern.ch gives:

  10.60.112.55 is a private address
  See The Naming System for information on host.domain and Addresses for information on Internet addresses.
  

• Does the pingserver work (see below)?
• Is there anything interesting in the web server log?
• The best thing to try next is to test traceroute.pl from the command line 
  • If it terminates with Alarm clock (see example below), then  try increasing the alarm(nn) statement in traceroute.pl (nn is the number of seconds)
    
• In traceroute.pl try replacing exec($Tr, @Tropts, $addr) with system($Tr, @Tropts, $addr) == 0 or die "system($Tr, @Tr, $addr) failed: $?\n"; and test traceroute.pl from the command line as above.
• Remove  the -wT from #!/usr/bin/perl -wT in traceroute.pl and test traceroute.pl from the command line as above.
• Create a simple perl script and execute from the command line and execute:

  #!/usr/bin/perl
  system('/bin/traceroute, -m 30 -q 1 -w 3, 134.79.197.200, 140') == 0 or die "system('traceroute, -m 30 -q 1 -w 3, 134.79.197.200, 140') failed: $?\n"; exit;
  

Traceroute.pl  stops after 4 hops

Below is an example:

After a lot of testing changing the number of queries per hop (-q), the timeout on queries (-w), the first hop to start at (-f), the maximum number of hops (-m) and turning off name resolution, this was found to be due to name resolution, i.e. using the -n option to turn off name resolution it went much faster and completed 30 hops. The name resolution was slow since one of the name servers was down causing timeouts. After disabling the use of the non working name server the execution was about 60 times faster. Results from the testing are shown in the spreadsheet here .