Versions Compared

Old Version 30

changes.mady.by.user Les Cottrell

Saved on

compared with

New Version 31

changes.mady.by.user Les Cottrell

Saved on

Key

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

...

  •  + Responded via Doodle will attend; - Responded, but unable to attend on this date; ? extra email sent asking if attending 
  • Email addresses (all the following are in pinger-my).
    • cottrell@slac.stanford.edu; wajahat.hussain@seecs.edu.pk; saqibutm@outlook.com; johari.abdullah@gmail.com; adibhabbal@karabuk.edu.tr; charnsak.s@ubru.ac.th; eyadayoubi@gmail.com; b.muslmani@yahoo.com; shadi.jawarneh@yahoo.com; bebo@slac.stanford.edu; kalim@slac.stanford.edu
Actual Attendees

 Bebo, Saqib, Les

Others

Administration

Use of Zoom

 

IMPORTANT NOTE: The meeting is set up to record automatically. By joining the meeting you are agreeing to be recorded. (see details. 

Also, note that daylight savings time will kick in on Sunday 3/10. Therefore, please consult the time conversion table here.

What: PingER Standing Meeting

When: Mar 14, 2019, 10:00 PM Pacific Time (US and Canada)

Where: Join from PC, Mac, Linux, iOS or Android: https://stanford.zoom.us/j/201093085

How to set up and use Zoom:

To use the software, you would have to download the Zoom client (and installed if prompted). The instructions to do so are listed here: https://zoom.us/download#client_4meeting

The instructions about setting up the software are listed at the URL below. You may want to create an account if you do not have one already. If you are invited to a meeting (i.e., you are not hosting the meeting), you are not required to create an account; you can simply join the meeting using the meeting ID.

https://support.zoom.us/hc/en-us/articles/201362033-Getting-Started-on-PC-and-Mac

...

Amity (Updated 3/3/2019).

...

Bebo will contact Topher, and look at installing on a spare Android at Bebo's home in San Francisco.  We could also do that at SLAC.

  • Topher will get us some Android phones when he gets back

...

  • . Topher is in Ecuador at the moment, he and Bebo will be meet in April. 
  • At this time Topher will install the latest version of the App in the Androids
  • Les will contact Amity to see if they will have an update to the Android/Pinger by 2nd week in April. Ideally such an update would include the location information for the MA when the measurement is made.  Email sent to Amity 3/15/2019:
    •  
      Topher (the person with the Android phones) is currently in Ecuador and he and Bebo will meet early April. At that time Topher will install the latest version of the Amity Android/PingER MA App in some Android phones for testing and evaluation. Thus it would be helpful if you could aim for say Monday April 8th 2019 for a release of the App.
        
      As I mentioned 3/6/2019, it would be good to make the following addition to the App:
       
      To track measurements made by a mobile device requires one to know its location at the time of the measurement.  This information needs to be recorded together with each measurement. We need to decide 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 existing gathering/storage/analysis to be backwards compatible. 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. This new location data might be appended at the end of each current measurement following the semi-colon.  

 

Adib (Updated 3/3/2019)

  • Adib moved to Karabuk University in Turkey where he is an Associate Professor.  
    • The time

...

Adib (Updated 3/3/2019)

Bebo reviewed and responded to Adib suggesting the second one is a better choice. Adib will submit ity to the 2nd journal.

 

NUST: (Updated 3/3/2019)

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 . (Wajahat was this useful? Is there something else?):

    • 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.
    • Are any of these of interest?

Saqib sent email to Wajahat:

  • As discussed in the last meeting, kindly check if it is possible to get an IPv6 address in NUST for installing an IPv6 MA in PK. I will also contact PERN regarding the possibility of getting an IPv6 address. 
  • Wajahat is moving from one office to another in NUST. There are IPs but he has not been able to get to the right person. He will update if the situation changes. Email sent 3/15/2019 requesting an update.

UAF UAF/GHZU (Updated 3/3/2019)

  • Saqib's current contract expired February 2019. He returned to Pakistan February 15th 2019. He has applied to multiple places in China, Pakistan, etc. He will probably join joined the University of Agriculture in Faisalabad. He plans to pursue the blockchain paper.
  • Bebo sent email:, see below.  Saqib will follow up.
    • Not sure whether this would be relevant for PingER work - maybe Saqib's blockchain paper? I'm not sure that there has been much discussion re: PingER security - thoughts? The submission is due May 24th
      Bebo
      •  From: Security and Communication Networks <scn@journals.hindawi.com>
        Sent: Monday, February 25, 2019 11:58 PM
        To: White, Bebo
        Subject: Special Issue: "Cryptography and Security Tools and Techniques for Networked Embedded Systems"
         
        Dear Dr. White, We are currently accepting submissions for our upcoming Special Issue titled 
        "Cryptography and Security Tools and Techniques for Networked Embedded Systems," which will 
        be published in Security and Communication Networks in October 2019. The Special Issue is open to both 
        original research articles and review articles, and the deadline for submission is May 24, 2019. 
        You can find the Call for Papers at https://www.hindawi.com/journals/scn/si/136986/cfp/. 
        Security and Communication Networks is a peer-reviewed journal published by Hindawi
        as part of a publishing collaboration with John Wiley & Sons (https://www.hindawi.com/wiley.hindawi/). 
        Starting January 2017, the journal has been converted to a fully open access publication, which 
        means that anyone can access it online without a subscription and authors retain the copyright of their work. 
        The most recent Impact Factor for Security and Communication Networks is 0.904 according to Clarivate Analytics' l
        atest Journal Citation Reports. The journal's most recent CiteScore is 1.36 according to the latest 
        CiteScore metrics released by Scopus. Please read over the journal's author guidelines at 
        https://www.hindawi.com/journals/scn/guidelines/ for more information on the journal's policies and 
        the submission process. Manuscripts should be submitted online to the Special Issue at 
        https://mts.hindawi.com/submit/journals/scn/adcsc/. 
        Please do not hesitate to contact me if you have any questions. Best regards, Rana Khaled

Thailand (No update 8/9/2018, No update 9/6/2018, No update 11/19/2018, 1/15/2019, 2/12/2019, no update 3/14/2019)

Charnsak is looking at a host in Champasak University, Chan Parsa province in Laos as a potential site for a PingER MA. Charnsak just got approved to make contact with the Champasak University. He expects to set up the MA in the next 4-5 months (say towards end 2018). It also depends on the partner university, and there may be a lot of paperwork.

Email requesting update sent 12/6/2018.

UNIMAS (No update 8/9/2018, no update 9/6/2018, no update 10/7/2018, no update 11/19/2018, 12/11/2018, 1/15/2019, 2/12/2019, 3/14/2019)

Need to add Umar Kalim to http://pinger.unimas.my/pinger/contact.php. From the 7/5/2018 meeting: Johari can't ssh into the server so he will go to it on Monday.  He will also upload the new UNIMAS PingER website next week.

...

 
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 to be fixed 4/3/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.2/25/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.

No update to the following 3/14/2019.

Context:

  • Is there any statistical difference between ICMP and TCP Ping? The context here is the Internet (not data center). This is important because the network stack is different (e.g., MPI over infiniband) and latencies are significantly less.

...