Versions Compared

Old Version 11

changes.mady.by.user Les Cottrell

Saved on

compared with

New Version Current

changes.mady.by.user Les Cottrell

Saved on

Key

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

Time & date 

This meeting:  February 27 2020 9 pm Pacific time; a day later 9:00 am Pakistan time; 9:30 am India time; 12:00 pm Malaysian & Guangzhou time;  11:00 am Thailand time; 6:00 am Jordan and 5:00am Turkey.    

Doodle poll invites sent 02/17/2020

Format

New items and updates are in boldface.

...

Mailing list: pinger-my@googlegroups.com for membership see  https://groups.google.com.

...

Invitees:

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

...

Wajahat is recovering from numerous infections, starting to visit office once again (2/17/2020)

Actual Attendees

Bebo, Saqib, Umar, Les

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) 

Roger Cottrell is inviting you to a scheduled Zoom meeting.

Topic: PingER Collaboration meeting 

Join Zoom Meeting
https://zoom.us/j/???????????9258476228

Meeting ID: ??? ??? ????925 847 6228

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 

Amity team photo:

Email sent 10/1/2020

 

Bebo, at our last meeting (Nov 26th), we discussed Amity and installing, testing the Amity Android PingER. My understanding was that you would need help to ensure it is working and the current level of collaboration does not look very conducive. It would help if Topher could assist and he would be visiting you around the end of the 1st week on December last year
From the minutes of our last meeting:
"SLAC needs to know how to access the Firebase data.
  • Once that is known and the data with lat, long included and we understand the format and how to access it, Les will look at how to incorporate in a backward-compatible fashion into the current PingER.Amity sent some information 10/19/2019. Les sent a long email 11/15/2019, asking how to understand files, how to get the lat/long and engaging Bebo and Saqib etc. 
  • Naman replied 11/18/2019 "The link which I shared is the apk file. You need not to extract it. Just download the apk and install on the mobile platform." Bebo, do you need more information, can you try this or follow up with Naman."
I sent email to Naman on Dec 6th with a copy to you saying:

...

In the page that came up (see 2nd attachment) I saw no place to enter the Google account pingeramity123@gmail.com. The page had a video and a Get Started button. I tried the video but saw nothing about entering a Google account.
Towards the bottom of https://firebase.google.com/
there was a section:
Authenticate a new user. With choices of Language (Swift Objective-C etc.)
The Authenticate a new user was a pull down that included "Subscribe a new user to a notification topic" 
I clicked on this and the 1st attachment popped up
That did not appear to help. 
I am sure this is all very powerful once one understands how to use it, but at the moment I am stalled.  Please help a newbie."
Naman responded 12/22/2019:

...

We will arrange a skype meeting in the first week of January to demonstrate how firebase works."
It appears we have missed the window of Topher's visit and the 1st week of January is over.

...

Two papers presented at Coinfluence 2020 meeting (they have been submitted to IEEE):

  • Implementation of PingER on Android Mobile Devices using Firebase, A Rajapappa, A Upadhyay, A S Sabitha, A Bansal, B White, L. Cottrell, Confluence 2020, 10th International Conference on Cloud Computing, Data Science & Engineering, Amity University, Noida, India, Jan 29-20 2020.
  • Comparison of Network Performance of India and Pakistan using PingER Data, A Sachan, N Madam, A S Sabitha, A Bansal, L Cottrell, B White, Confluence 2020, 10th International Conference on Cloud Computing, Data Science & Engineering, Amity University, Noida, India, Jan 29-30 2020.
  • 2/17/2020 Amity sent a video explaining how to access their data. It is a Windows wmv file so on a Mac you will need to download VLC to play it.  The format of their data appears to be:

    Image Added
    However, the PingER format for the measurements (as given in https://confluence.slac.stanford.edu/display/IEPM/PingER+Monitor+node+format) is

    Src_name                        Src_addr         Dst_name                   Dst_addr       Len  Unix_GMTs  sent      rcv min   avg    max   seqs-----------------    RTTs-----------------------------

    pinger.slac.stanford.edu 134.79.240.30 ping.slac.stanford.edu 134.79.18.21 100 1152489601      10    10 0.255 0.341 0.467 0 1 2 3 4 5 6 7 8 9 0.287 0.380 0.467 0.391 0.327 0.387 0.291 0.332 0.255 0.299

    which is very different. Also we wish to add the lat long of the Measurement agent so we can accommodate the maneuverability of the MAs.  I propose that in order to maintain backward compatibility we add the lat long of the MA at the end of each record following a semi-colon (;). E.g. 
    monitor.niit.edu.pk 203.99.50.204 www.carnet.hr 161.53.160.25 100 1171756802 10 10 223.323 224.978 226.805 1 2 3 4 5 6 7 8 9 10 226 223 226 223 223 226 223 224 226 225; 37.4472 122.1754

    I have emailed Amity with this information 2/27/2020.

Bebo

Bebo's account at SLAC was 'Off-Boarded' since his sponsor (Umar) had left SLAC and there was nobody to 'On-Board' him when his current term expired. Les got the new head of networking at SLAC (Mark) to sponsor Bebo, and Bebo was 'On-Boarded' 3/2/2020.

Bebo brought our attention to a report from KeepitOn on the 213 Internet shutdowns in 2019. An internet shutdown happens when someone — usually a government — intentionally disrupts the internet or mobile apps to control what people say or do.

NUST

 

IPv6 host at NUST:

Wajahat has requested Hasan to install PingER on an IPv6 host at NUST, Saqib has contacted Hasan to tell him where to find and upload the code. There is not a host name for the MA yet. Hopefully, this will be available by next month's meeting.

  •  7/24/2019 Les emailed Wajahat with a request for an update.
  • At the meeting Wajahat had asked the student to contact Saqib and get the information on energizing IPv6. Saqib provided the information, but the student could not access the URL (apparently the URLwas down). Wajahat was on leave and when he returned the internship had expired, so Wajahat is unsure what happened. Wajahat will start a new student next week and will set him on the IPv6 project. Progress? 

Sent email on 2/4/2020 to Kiran at NUST on how to bring the vu host's pinger.xml up to date. As of 2/3/2020 pinger.xml at vu now looks good and we now appear to be able to gather good data.

We are working on maggie2, monitor and nwfpuet:

UAF (University of Agriculture, Faisalabad)/GHZU

Saqib plans to continue work on PingER monitoring for remote areas, in particular in Pakistan. He will use Android PingERs. This may partially tie into the Amity project.

He will also continue his work on Blockchain and plans to attend a Blockchain workshop in Guangzhou.

The 4th  Call for Proposals for The Asi@Connect Project:

  • Saqib submitted a concept note in WP6 with Wajahat and Les as co-applicant.
  • It was accepted and Saqib was given the go-ahead to submit a Full Proposal.
  • With suggestions and an endorsement letter from PERN plus CVs from Wajahat and Les, Saqib put together a full proposal and it was submitted 11/6/2019.
  • However, it was not accepted

Saqib plans to get 2-3 undergraduate students in a month or so and plans to look at Android PingER.

He has been invited to an APAN meeting in Nepal, however, with the Corona Virus it was postponed.

Saqib registered a DNS name for GC Women University Faisalabad. The new URL is http://pinger.gcwuf.edu.pk/cgi-bin/ping_data.pl. Previously there was no DNS name so the name was reported as 121.52.153.227. This required a change in the <SrcName> in pinger.xml and exposed a bug in ping_data.pl which has been fixed in the latest release (4.6).

SLAC

  • Les turned on the debugging to investigate the discovery that several analysis scripts had stopped working in November 2019
    • Each night we run about 100 analysis scripts as batch jobs and after fixing problems with the mon-lib.pl etc. we still found about 10% were randomly failing.
    • After about 4 weeks it eventually transpired that some of the batch machines had not been enabled to access the Oracle database via the firewall. The jobs submitted to those hosts failed.
    • The cause of the problem was eventually identified about January 3rd and fixed about January 6th. No data was lost.
  • The new version of Linux CentOS7, does not appear to support the following modules that are used by the PingER analysis.
    • The Oracle database interface. PingER uses Oracle so there could be a problem. 
    • The perl statistics module
    • I will restrict the PingER analysis jobs to the earlier version of Linux (RHEL6) to avoid these problems. I am working with the systems folks at SLAC and looking into when the current version of Linux at SLAC (RHEL6) will no longer be supported and following SLAC's planning on how or whether to address the issues.
      • Rhel6 has full support until Nov 30, 2020. It then goes on "extended" support until June 2024. I expect SLAC will continue to use it during the extended support phase, at least for a couple of years.
      • Umar did some research and found:

...

Bebo

NUST (Updated 7/24/2019)

 

IPv6 host at NUST:

Wajahat has requested Hasan to install PingER on an IPv6 host at NUST, Saqib has contacted Hasan to tell him where to find and upload the code. There is not a host name for the MA yet. Hopefully, this will be available by next month's meeting.

  •  7/24/2019 Les emailed Wajahat with a request for an update.
  • At the meeting Wajahat had asked the student to contact Saqib and get the information on energizing IPv6. Saqib provided the information, but the student could not access the URL (apparently the URLwas down). Wajahat was on leave and when he returned the internship had expired, so Wajahat is unsure what happened. Wajahat will start a new student next week and will set him on the IPv6 project. Progress? 

Sent email on 2/4/2020 to Kiran at NUST on how to bring the vu host's pinger.xml up to date. As of 2/3/2020 pinger.xml at vu now looks good and we now appear to be able to gather good data.

We are working on maggie2, monitor and nwfpuet:

UAF (University of Agriculture, Faisalabad)/GHZU

Saqib plans to continue work on PingER monitoring for remote areas, in particular in Pakistan. He will use Android PingERs. This may partially tie into the Amity project.

He will also continue his work on Blockchain and plans to attend a Blockchain workshop in Guangzhou.

The 4th  Call for Proposals for The Asi@Connect Project:

  • Saqib submitted a concept note in WP6 with Wajahat and Les as co-applicant.
  • It was accepted and Saqib was given the go-ahead to submit a Full Proposal.
  • With suggestions and an endorsement letter from PERN plus CVs from Wajahat and Les, Saqib put together a full proposal and it was submitted 11/6/2019.

SLAC (Updated 8/26/2019) 

  • Les turned on the debugging to investigate the discovery that several analysis scripts had stopped working in November 2019
    • Each night we run about 100 analysis scripts as batch jobs and after fixing problems with the mon-lib.pl etc. we still found about 10% were randomly failing.
    • After about 4 weeks it eventually transpired that some of the batch machines had not been enabled to access the Oracle database via the firewall. The jobs submitted to those hosts failed.
    • The cause of the problem was eventually identified about January 3rd and fixed about January 6th. No data was lost.
  • The new version of Linux CentOS7, does not appear to support the following modules that are used by the PingER analysis.
    • The Oracle database interface. PingER uses Oracle so there could be a problem. 
    • The perl statistics module
    • I will restrict the PingER analysis jobs to the earlier version of Linux (RHEL6) to avoid these problems. I am working with the systems folks at SLAC and looking into when the current version of Linux at SLAC (RHEL6) will no longer be supported and following SLAC's planning on how or whether to address the issues.
      • Rhel6 has full support until Nov 30, 2020. It then goes on "extended" support until June 2024. I expect SLAC will continue to use it during the extended support phase, at least for a couple of years
        • .

Umar 

State of MAs.

Host
State
last seen
Status
pinger.nchc.org.tw Intermittent problems starting 11/9/2019, it is not pingable starting 11/12/2019.  
pinger.vu.edu.pkUnable to gather data since 29th August, 2019. The host is pingable. Emailed Wajahat 11/3/2019. Wajahat responded 11/11/2019 "Anything improved?". Les responded they are still not working with more details and suggesting we focus on vu. 11/20/2019 Les asks if there is an update? Wajanat responded 11/20/2019 "These guys are not responding. We are trying to contact them. Already tried multiple times." This just applies to vu. Wajahat recommends we keep trying to gather data. I have turned off the warnings. Kieran Kiran fixed it 2/3/2020 by restoring the pinger.xml file following email instructions from Les8/28/2019Fixed 2/3/2020.
monitor.seecs.edu.pkNo data since 10/29/2019, host is pingable email to Wajahat 11/7/2019. Reminder to Kieran Kiran and Wajahat 2/16/2020. Host not pingable sent email to Kiran and Wajahat 3/3/2020.10/27/2019 
maggie2.seecs.edu.pkNo data since 11/4/2019, host is pingable email to Wajahat 11/2/2019, 11/20/2019. Reminder to Kieran Kiran and Wajahat 2/16/2020. Host no longer pingable, sent email to Kiran and Wajahat 3/3/2020.  
pinger.nwfpuet.edu.pkSomething amiss since April 2019 when it dropped from monitoring over 150 targets down to 4. There is nothing in <BeaconsList>, all the hosts it attempts to monitor are in the locally manually maintained <NodeList>. Does not ping by name. Email sent 11/7/2019, and again 11/20/2019. Reminder to Kieran Kiran and Wajahat 2/16/2020.   
pingeramity.inContinues to be unstable. Email 8/29/2019. Turned off email warnings 11/20/2019.  

Next Meeting

Next meeting:  There will be a Doodle poll, for  2020 at 10 9 pm Pacific time; a day later 109:00 am Pakistan time; 109:30 am India time; 112:00 pm Malaysian & Guangzhou time;  21:00 pm Thailand time; 76:00 am Jordan time. 65:00am Turkey time.  

...

Old information

...