Page History

Unable to gather data from maggie1.seecs.edu.pk and monitor.seecs.edu.pk. Email sent 1/26/2019

• 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. Wajahat will look at it.
• Wajahat fixed maggie.seecs.edu.pk 2/29/2019, Les sent email 2/3/2019 to Wajahat asking about monitor1.seecs.edu.pk.
• pinger.isra.edu.pk is not pingable and unable to gather data starting 2/11/2019. We will wait a few days and see if it recovers.
  

Wajahat provided the following update 12/8/2018

• "We have been aggressively pursuing the three nodes(121.52.146.180 (kohat.edu.pk) down since Nov 22/2017; cae.seecs.edu.pk last time we were able to gather any data was September 2nd 2018; and pinger.isra.edu.pk no data since 5th Sept 2018, so it is a candidate to Disable). It appears to me that the participating institutes have started to lose interest in the project. Anyhow, we will keep pushing. Maybe a letter of appreciation from SLAC might rejuvenate their energies. What is your opinion?

• Wajahat raised the topic: We also need to formulate some research problems that have the potential of appearing in some well-known places. This might help in attracting NUST students which is getting harder these days. I need your help in this regard.

  Discussion:

  • There is a web page at Future PingER Projects which was last updated July 2018. Topics that currently stand out include:
    • Applying Blockchain to PingER data, see the paper by Saqib, here.
    • Graphical traceroute maps.  Note currently when one looks up the location of a router, it usually gives the location of the home site that is managing the routers, e.g. ESnet routers in the US and Europe are all identified as being at LBL. Using ping minimum RTTs to a router from multiple sites (e.g. the perfSONAR traceroute servers in the US, Canada, and Europe, see http://www.slac.stanford.edu/comp/net/wan-mon/viper/tulipmap.html) one can use trilateration to identify the location of the router. Earlier work on this can be found at http://www.slac.stanford.edu/comp/net/tulip/
    • Deploying Android/Pinger devices, understand how their low cost (cheap enough to be disposable), low power (e.g. use of solar power) and potential mobility may be used, i.e. the risks, mitigations, and benefits.
    • Linked Open  Data applied to PingER data.
    • Using PingER data as a source of big data to search anomalies, trends etc.
    • Case studies, e.g. can one identify the impact on networking of social unrest such as the current Venezuala difficulties, or of other events such as earthquakes or Tsunamis.
      • I have increased the number of working  Venezuelan target hosts monitored from SLAC from 3 to 8, to possibly assist in this.
      • Another interesting case study would be to look at the impact of hurricanes on Internet connectivity in say the Caribbean, see for example Hurricanes Irma and Maria 2017. 
    • Compare and contrast IPv6 with IPv4 behavior, identify outliers and understand - Umar, Les, and Saqib are looking at this.
  • Also, see PingER Papers and Presentations for some topics that have recently resulted in papers.