You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

They followed the instructions at Installation Overview.They were able to download and install the files.

The cgi-bin directory appears as:

It would be good to get an ls -l to ensure teh files are executable.

and /usr/local/share/pinger appears as:

They then remotely logged in to test traceroute.pl file using http://202.12.103.71/cgi-bin/traceroute.pl which gives a webpage.  This page looks correct, just tap yes to get it to make the traceroute. It also works if I VPN into SLAC from my home in the Bay Area. After pressing Yes I get:

It appears that though the request is being made to 202.12.103.71 when traceroute.pl at Amity tries to get the IP address of the traceroute server at Amity it gets 127.0.1.1. I suggest adding some debugging statements to traceroute.pl around line 84 (or you can use the perl -dT option (see the lines following line 2 in traceroute.pl)) which reads:

use Net::Domain qw(hostname hostfqdn hostdomain);
my $hostname = hostfqdn();
my $ipv="4";#set default used by gethostbyname6 to decide if to force IPv6
my $ipaddr=gethostbyname6($hostname);

to trace what is happening and see if it is fixable (possibly hardcode the $ipaddr).

I would sort this out before going onto ping_data.pl. Once ping_data.pl works (puts up its form) then debugging will be simpler.

 

 

  • No labels