Time & date 

This meeting:  Tuesday, February 12th,  10 pm Pacific time (Nb now on winter time); a day later 11:00 am Pakistan time; 11:30 am India time; 2:00 pm Malaysian & Guangzhou time;  1:00 pm Thailand time; 8:00 am Jordan time.  We moved the time forward by 2 hours to accommodate the time in Jordan.

Doodle poll invites sent 1/26/2019.

Format

New items and updates are in boldface.

Coordinates of team members:

See: http://pinger.unimas.my/pinger/contact.php

  • Need to add Umar and Dr. Taha - Johari

Attendees

Invitees:

Wajahat Hussain+ (SEECS), Saqib+ (GZHU); Johari+ (UNIMAS);  Adib (Turkey); Dr. Charnsak Srisawatsakul (Ubru), Eyad Ayoubi+ (Jordan), Baraa Muslmani+( Jordan), Dr. Shadi Jawarneh (Jordan), Bebo White+, Umar Kalim-, Les Cottrell+

  •  Email addresses (all the following are in pinger-my).: 
    • 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 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; cottrell@slac.stanford.edu
  • + Responded via Doodle will attend; - Responded via Doodle but unable to attend on this date; ? extra email sent asking if attending
Actual Attendees

Wajahat, Saqib, Eyad, Barra, Bebo, Les

Others

Administration

Use of Zoom

IMPORTANT NOTE: The meeting is setup to record automatically. By joining the meeting you are agreeing to being recorded. (see details.)
What: PingER Standing Meeting
When: Feb 12, 2019 10:00 PM Pacific Time (US and Canada)
Where: Join from PC, Mac, Linux, iOS or Android:https://stanford.zoom.us/j/811437823
Or iPhone one-tap (US Toll): +18333021536,,811437823# or +16507249799,,811437823#
Or Telephone:
    Dial: +1 650 724 9799 (US, Canada, Caribbean Toll) or +1 833 302 1536 (US, Canada, Caribbean Toll Free)
          
    Meeting ID: 811 437 823
    International numbers available: https://zoom.us/u/acKQGp4oHV
    Meeting ID: 811 437 823
How to setup and use Zoom:

Recording

Jordan  (Updated 2/14/2019)

We had a Zoom meeting with Eyad and Baraa of the Jordan team.

Amity (Updated 2/14/2018).

Amity team photo:


Email list (pinger-am in https://groups.google.com) set up for the Amity PingER team including Aayush Jain, James David, Naman Madan, Dr Sai Sabitha. Invites sent 1/26/2019

Dr. Sai Sabitha Topher sent the final copy of paper Id 255: "Network Performance of PingER data with respect to growth of the Telecom Industry in India" that was presented at Amity Confluence conference 1/10/2019.

Requested final copy of the paper ID 256: "Extension of the PingER project onto Mobile Devices using Android Applications" for the SLAC archives, by email 1/26/2019.

From the meeting with Amity last month:

We (Topher and the PingER team) agreed to request Amity to share the App and instructions with us; we will look at installing on a jailbroken Android phone at the San Francisco end and try it out.

  • 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.

Email sent to Amity 1/26/2019: "We also need to finish up the proxy acquisition of data from the Android MAs. According to the notes from the recent meeting

  • 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.
  • Is this correct? What will be the address to fetch the data from by anonymous FTP? If so there any progress? Do you need anything from our end?"

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.

Adib (Updated 2/14/2018)

 

NUST: (Updated 2/14/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:

    • 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.

UAF/GHZU (Updated 2/14/2019)

  • Saqib's current contract expires February 2019. Saqib reports that things are still unsure, his current contract cannot be renewed. He will return to Pakistan February 15th 2019. He has applied to multiple places in China, Pakistan, etc. He will probably join the University of Agriculture in Faisalabad. He plans to pursue the blockchain paper.

Thailand (No update 8/9/2018, No update 9/6/2018, No update 11/19/2018, 1/15/2019, 2/12/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)

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.

Sent reminder emails 8/6/2018. 9/3/2018.

 

PingER at SLAC  

PingER IPV6 support

 

HostStatelast seenStatus

pingersonar-um.myren.net.my, perfsonar-usm.myren.net.my, pingersonar-utm.myrec.net.my

Unable to gather data since mid-November, unable to ping, unable to contact Fizi Jalil, so they have been Disabled.Mid-November 2018Disabled
pinger.nwfpuet.edu.pk/cgi-binThe hostname did not resolve from SLAC, DESY andCERN, however it does resolve from some other places. Email sent to Wajahat and to SLAC net-admin 1/12/2019. No responses, on 1/13/2019 it was fixed, no idea how. It appears that the DNS resolution is intermittently failing. Therefore Les modified getdata.pl to first try DNS and if it fails try getting the data from the IP address in the configuration file. As of 1/18/2019 it appears to be working reliably.Started 1/7/2019Working again. Recovered missing data.
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/2018it 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.

March 6, 2018

Fixed 1/5/2019

Failed again starting 1/26/2019.

Working again 1/30/2019

maggie1.seecs.edu.pk,

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

Skipping maggie1.seecs.edu.pk(3) does not ping by name or address 111.68.101.45

Wajahat fixed 1/14/2019. Went back and gathered missing data.

1/14/2019Wajahat fixed 1/29/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.

1/14/2019 
pinger.fsktm.um.edu.mySent email to Nor Badrual Anuar 1/5/2018. Recommend replacing the pinger.xml file from the master at http://www-iepm.slac.stanford.edu/pinger/pinger.xml and editing it. Nor Badrul Anuar replied saying he will look at it. The file pinger.xml does not close the HostList with a </HostList>. Nor Badrual Anuar edited the pinger.xml file, but the problem was that the hard disk space was full. There are data files going back to 2012. Recommended he deletes all data files up through October 2018. He did this. Then the version of pinger2.pl he was using (ca. 2012) needed SrcIP to be in the pinger.xml file. He added SrcIP to pinger.xml and also updated pinger2.pl. This fixed it. Also recommended he install the data trimmer (see http://www-iepm.slac.stanford.edu/pinger/tools/install2.html) and enter it in the cronjob.12/28/2018Badrul fixed 1/30/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.

Questions:

  • Why should we focus on minimum RTT instead of average RTT
  • Are the R plots generated using minRTT?
    • Averages and computed. Min RTT is available. Scripts need to be updated to use minRTT.
  • What is the breakdown of latency between endpoints? If there is a difference, is it because of the type or location of the source? What if the source of traffic was not SLAC? Is there a correlation with the distance between the endpoints?
  • Are the differences limited to a particular region? How do we determine/understand if traffic prioritization is implemented?Test in a controlled environment to avoid variables such as traffic prioritization, queuing delay due to cross traffic. Review the time series of latencies for both ICMP and TCP ping, instead of averages?Is there a difference between IPv4 measurements vs. IPv6.
    • It may be that end hosts which are farther away have larger variances and thus the pronounced differences.

Next Meeting

Next meeting:  There will be a Doodle poll, March week 11-14th 10 pm Pacific time ; a day later 11:00 am Pakistan time; 11:30 am India time; 2:00 pm Malaysian & Guangzhou time;  1:00 pm Thailand time; 8:00 am Jordan time.  We moved the time forward by 2 hours to accommodate the time in Jordan.

Old information

  • No labels