Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Installation Overview.This is proceeding. They have a working pinger2.pl. They have a public DNS pingeramity.it. They have installed ping_data.pl, it is working however: 

They  have changed from

<SrcName>pingeramity.amitynoida.local</SrcName>

...


There is information on progress at Setting up PingER servers at Amity.

There is now something strange They fixed up a  strangeness in the DNS lookup for pingeramity.in as seen from SLAC that is was causing problems with gathering data:

[cottrell@pinger ~]$ nslookup pingeramity.in
Server: 134.79.111.111
Address: 134.79.111.111#53

Non-authoritative answer:
Name: pingeramity.in
Address: 202.12.103.71
Name: pingeramity.in
Address: 173.193.105.245

[cottrell@pinger ~]$ nslookup pingeramity.in

Server:  134.79.111.111

Address: 134.79.111.111#53

Non-authoritative answer:

Name: pingeramity.in

Address: 173.193.105.245

Name: pingeramity.in

Address: 202.12.103.71

[cottrell@pinger ~]$ dig pingeramity.in

 

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.37.rc1.el6_7.7 <<>> pingeramity.in

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33477

;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 0

 

;; QUESTION SECTION:

;pingeramity.in.   IN A

 

;; ANSWER SECTION:

pingeramity.in.  28097 IN A 202.12.103.71

pingeramity.in.  28097 IN A 173.193.105.245

 

;; AUTHORITY SECTION:

pingeramity.in.  36508 IN NS dns3.bigrock.in.

pingeramity.in.  36508 IN NS dns4.bigrock.in.

pingeramity.in.  36508 IN NS dns1.bigrock.in.

pingeramity.in.  36508 IN NS dns2.bigrock.in.

 

;; Query time: 1 msec

;; SERVER: 134.79.111.111#53(134.79.111.111)

;; WHEN: Mon Apr 11 21:34:04 2016

;; MSG SIZE  rcvd: 148

The host has been un-pingable for the last two days.

Traceroute/ping servers - Les

...

I.e. the target address is a private Internet address (RFC 1918).  One gets a similar result for http://202.12.103.71/cgi-bin/traceroute.pl?function=ping

This is at least was at least partially due to the host's environment variable REMOTE_ADDR=10.0.253.1 whereas it should be the public address of the remote host but. 10.0.253.1 is a private address so here is no way to traceroute to it. THis has probably been fixed with the pingeramity.in DNS registration. However the host is unpingable.

Android implementation of Pinger Measurement Agent - Bebo

...