A better way to test network elements

[tradez]

Fellow Monks,
  &nsbp I am sure that there is a better way to do what I am trying to do. I am writing a script that allows people to input an IP from our call center and do simple tests. Forward and Reverse NS Lookup, Ping, and the killer, Traceroute. Pretty simple stuff, but the traceroute is killing me. I am on sunOS 5.7, and the traceroute binary I have running does not seem to have a way to die. Basically, if someone puts in a bad a ip, ie 1.2.3.4 it will get to the gateway and just hang. Currently I work around this by

$fork = fork();

      if(fork){

        sleep 20;
        open (MYFILE, "traceroute$time.txt");
        @data = <MYFILE>;
 
        if (!@data){
 
        $error = 'Ip could not be Tracerouted';
        push (@lines, $error);
 
        }else{
 
          foreach $line (@data) {
 
            $line =~ s/\n/<br>/g;
 
            push (@lines, $line);
 
          }
        }
 

      }else{

        $tracert = `traceroute "$ip" > traceroute$time.txt`;

      }

A simple, yet archaic answer to an issue that I know can be solved more easily. I was thinking about just using a system() call, sleeping, then checking it to see if I got results, but that would really not speed things up much. Please help me to find a better way!

Tradez
"Never underestimate the predicability of stupidity"
- Bullet Tooth Tony, Snatch (2001)

[Moonie]

Why not use Net::Traceroute6? - It has a timeout option that you could take advantage of.

- Moon

[ajwans]

Forking does not seem to be the optimal solution to this. I would prefer to set a handler for SIGALRM and set an alarm, something like.



$SIG{ALRM} = sub { die ("Couldn't traceroute"); };
alarm (20);
if ($tracert = `traceroute "$ip"`)
{
    alarm (0);
}
# handle data from traceroute here



This is documented in the perlipc perldoc.

1. dude, what does mine say?
2. "sweet", what about mine?
3. "dude", what does mine say?
4. GOTO 2