Versions Compared

Old Version 1

changes.mady.by.user Les Cottrell

Saved on

compared with

New Version 2

changes.mady.by.user Les Cottrell

Saved on

Key

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

...

Attendees

Invitees:

Wajahat Hussain+, Taha (SEECS), Saqib + (GZHU); Johari (UNIMAS);  Adib (Turkey); Dr. Charnsak Srisawatsakul? (Ubru), Eyad Ayoubi - (Jordan), Baraa Muslmani-( Jordan), Dr. Shadi Jawarneh ? (Jordan)

 Les+, Bebo+, Umar+

  • + Responded via Doodle will attend; - Responded via Doodle but unable to attend on this date; ?email sent asking if attending

...

Use of Zoom

Currently, there will be a different URL for each meeting of the form https://stanford.zoom.us/j/198241953 where the 195360538 will vary from meeting to meeting. 

Time: Jan 15, 2019 10:00 PM Pacific Time (US and Canada)
Join from PC, Mac, Linux, iOS or Android: https://stanford.zoom.us/j/198241953
Or iPhone one-tap (US Toll): +18333021536,,198241953# or +16507249799,,198241953#
Or Telephone:
    Dial: +1 650 724 9799 (US, Canada, Caribbean Toll) or +1 833 302 1536 (US, Canada, Caribbean Toll Free)          
    Meeting ID: 198 241 953
    International numbers available: https://zoom.us/u/abS5kMW4Kx
    Meeting ID: 198 241 953
How to setup and use Zoom:

Recording

Action Items from previous meetings

  • Amity to set up a pinger-am email list. Sent email reminder 1/26/2019.

Jordan  

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

...

Amity (Updated 1/3/2019).

Topher (Rain Forest Connection), Bebo, Umar, and Les met via Zoom with Amity team 1/2/2019. See meeting notes.

  • The unreliability There was caused by a dynamic address which has now been changed to a static address, also they will get a new UPS to fix power problems. a long discussion on Android/ePingER
      • It has been reliable since 7:46am 12/21/2018 GMT.
      There was a long discussion on Android/ePingER
      • We will use anonymous FTP to gather the data.
      • They will add the GPS coordinates (lat/long) to the MA data. This will enable looking at mobile PingER measurements.
      • The paper on Android/PingER will be presented and published here on Jan 10th 2019.
    • Email sent to Sabitha and Naman 1/18/2019.
      • How did the presentation of the paper Id 255: "Network Performance of PingER data with respect to growth of the TElecom Industry in India". Were there any interesting comments etc? Has the paper been published. If so please send a final copy to post to the local DoE/SLAC archives.  
      • Same questions for ID 256: "Extension of the PingER project onto Mobile Devices using Android Applications"
      • Requested them to set up a pinger-am email list of people at Amity working on PingER related issues (1/18/2019).

    Adib (Updated 12/15/2018)

    ...

     

    NUST: (No update 1/15/2019)

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

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

    Wajahat was unable to attend but 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?
    • 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.

    UAF/GHZU (Updated 1/18/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.
    • Gathering data is no longer working. Saqib tried to make the Beijing MA live again. However, he has little control over it as it is in the CERNET cloud. The traceroute server still works. We have given up on the MA. It has been Disabled.

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

    ...

     

    gzhucn  
    HostStatelast seenStatus
    pinger.nwfpuet.edu.Is not working- Disabled10/20/2018 
    pingersonar-myren.net.myNo response. Sent email to hafizi@myren.net requesting help 12/24/2018. It was returned with address unknown. Sent email to Johari and postmaster requesting a forwarding address. Postmaster email bounced. Disabled6/26/2018

    Host pingable but web server does not respond.

    Disabled 1/3/2019

    pk/cgi-binThe hostname did not resolve from SLAC,DESY and pinger.nwfpuet.edu.pk/cgi-binThe hostname did not resolve from SLAC,DESY and CERN, 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.pkDown, 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.March 6, 2018Fixed 1/5/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.12/28/2018Corrupted pinger.xml filepingeramity.inIt has been working since 28th July. It is unclear how stable it is. It is down again 9/5/2018. Worked again from 9/24/2018 to 9/28/2018. Emailed Amity requesting clarification 10/3/2018. They are looking at it. No response 12/24/2018. It is still unreliable, details of unreliability, e.g. not pingable at times and no data some days, sent email 12/23/2018. Changed from Dynamic to Static IP address, and will replace UPS. It has been reliable since 7:46AM Dec 21, 2018 GMT.April 27, 2018 The file pinger.xml does not close the HostList with a </HostList>. Sent reminder email 1/26/2019.12/28/2018Corrupted pinger.xml file

    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.

    ...