Versions Compared

Key

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

...

  • Instructions from Aayush to load the application are at ePingER Functional prototype (for Androids only)
    • Topher was able to make the prototype work on an android phone prior to our last call. They might have an updated app, in which case he can further test it, but he’d need to know where to get it. He offered to put it in an android phone and drop it off for you at SLAC where we can also test it, in early February. 
    • Email sent to Amity 1/27/2019 asking if there is a newer version of the App.
  • We will use the amity anonymous FTP server to gather the data.
  • They will add the GPS coordinates (lat/long) to the MA data. This will enable looking at mobile PingER measurements.
  • We have requested (emails 3/6/2019, 3/15/2019) to know how the extra information on lat/long will be added to the records (I.e. the format of the android records) since accommodating that will require changes in the gathering/storage/analysis to be backwardsbackward compatible. Thus it needs to be algorithmically simple to identify and extract the extra information. For example providing a simple separator between the old data format and the new extra lat/long data, such as a semi-colon.

...

 

HostStatelast seenStatus
pinger.cs.ubru.ac.thStopped being pingable 2/25/2019. Thus by default the gathering failed. However, by ignoring the ping result gathering works to http://pinger.cs.ubru.ac.th/cgi-bin/ping_data.pl. Fixed gatherer script and gathered missing data. 3/2/2019 sent email to Charnsak asking if the pinging can be fixed. It appears appeared to be fixed 4/3/2019.  2/25/2019.Ping fails but gathering works.
pinger6.cs.ubru.ac.thStopped being pingable 2/25/2019. Thus by default the gathering failed. Gathering also fails to http://202.29.20.125/cgi-bin/ping_data.pl . Emailed Charnsak 3/4/2019, 3/15/2019.2/25/2019 
pinger.cs.ubru.ac.thUnable to gather data. Not pingable by name or address. Emailed Charnsack 3/15/2019.3/513/2019 
pinger.isra.edu.pk

Down, it came up Sep 2-4, 2018. It is pinging, however, all the targets are not responding after 31 tries, email sent to Wajahat 9/18/2018. As of 10/14/2018 it is not pingable. Working again as of 1/5/2019.

It started again1/26/2019. It does not respond to pings from SLAC but does respond to http://pinger.isra.edu.pk/cgi-bin/ping_data.pl? which is used to get the data.  However, the data indicate that none of the pings respond, e.g.

pinger.isra.edu.pk 121.52.154.228 pinger.fsktm.um.edu.my 103.18.2.152 100 1548633600 31 0

i.e. all 31 pings fail and  0 give any response.

When one tries to ping from pinger.isra.edu.pk using http://pinger.isra.edu.pk/cgi-bin/traceroute.pl?function=ping&target=www-wanmon.slac.stanford.edu&options=-i%200.2 the web page responds but all pings from isra fail. Email sent to Wajahat 1/28/2019. Started working again 1/30/2019. Stopped being pingable and unable to gather data 2/11/2019. 3/2/2019 can gather data but all the pings are failing. This is not a normal failure mode. Emailed Wajahat 3/3/2019, 3/15/2019.

March 6, 2018

Fixed 1/5/2019

Failed again starting 1/26/2019.

Working again 1/30/2019

monitor.seecs.edu.pk

results{monitor.seecs.edu.pk}[0] not defined, unable to gather data for 11 consecutive days this month

Skipping monitor.seecs.edu.pk(5) does not ping by name or address 111.68.101.10, email sent to Wajahat 1/26/2019, 2/3/2019, 3/3/2019.

It started working again 3/5/2019.

1/14/2019Working again 3/5/2019.

...