Versions Compared

Key

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

 

 

Time & date 

Wednesday Dec 7th  8:00pm Pacific Standard Time, Thursday Dec 7th 9:00am Pakistan time, Thursday Dec 27th  2016 12:00noon Malaysian time, 

...

Attendees

Invitees:

Wajahat Hussain?+, ajmal.farooq@seecs.edu.pk,? Muhammad Anas Abrar? (SEECS); Saqib+, Aqsa? (UAF); Johari?-, Adnan Khan (UNIMAS);  Badrul,  Ridzuan, Ibrahim (UM); (UTM); Adib?-, Fatima (UUM); Fizi Jalil (MYREN);  Les+, Bebo-,

+ Confirmed attendance

- Responded but  Unable to attend: 

? Individual emails sent

Actual attendees:

Wajahat, Les (Saqib stuck in fog/traffic)

Wajahat, Les

Administration

 

PingER for Android (see ePingER on Android two methods).

Amity - Java approach (A. Sai Sabitha and Shivnarayan Rajappa)
  1. They are using the native java tools, they are not running the pinger2.pl <http://pinger2.pl>  script on android since the native java tools have the following advantages
    1. easier for user, 
    2. no need for prior installation of any software, e.g. load perl interpreter which may require missing skills, especially for a non technical user
    3. doesn't need a rooted phone
    4. only the apk needs to be installed to run
  2.  They have fixed the final sequence number change by using regex, and  pushed these changes to github repository.

  3. They have installed apache tomcat in the server and plan to use a java file on the server which would connect to the phones that send the request. This java file will then take the input stream received from the phone and write the output stream to a file that would be stored on the server. We are facing some problems regarding a blocked port that is not allowing the phone to connect to the server we are currently working on resolving the issue.

  4.  SLAC can then regularly pull these files which would be stored based on the month they are received. 

  5. The Android students have started writing a paper on " implementation  of pinger  on android " .

  6. Next steps:

    1. Extend the target list by getting the Beacon list from SLAC. It is at http://www-iepm.slac.stanford.edu/pinger/pinger.xml on a regular basis and updating the <BeaconList> section at their site. This was part of pinger2.pl

    2. Also they will need a utility to clean out old recorded data (say older than 3 months), since it will be gathered from SLAC (via the proxy) and eventually they may run out memory on the Android.
UAF Saqib and Sara Masood
  1. Device ready, will assign live IP to machine next week, then will contact Les to try and gather data.
Discussion

To a large extent it depend on how we plan to use this.

  • If the phones are just MAs in a fixed location then simply porting pinger2.pl is easier and probably sufficient.  
  • If this is intended to grow into a mobile application for general use then it needs to be the Java implementation.

A next step is to get the data from the phone MA to the archive at SLAC. The current method ping_data.pl requires a public IP address for the phone which may not exist if its is mobile. Getting the MA to put the data to the archive may raise some security issue for the archiver.

UUM

From Adib:

Amity 

Tropical cyclone Vardah hit Chennai in India on the Dec 13th. It impacted the Internet, in particular one of Airtel's undersea cables. Les sent email to A. Sai Sabitha to see if  PingER from Amity could see any effect.

Saqib also reported that there was also a cable cut between Singapore and Europe on October 4, 2016 in SEA-ME-WE 4. Thus affecting the internet speed in south Asia and south-east Asia.  Maybe worth looking at the impact (if any).

UUM Social

From Adib:

  • Adib gave a key note presentation at the ICSEC2016 at Changmai in Thailand. As a result:

    • Dr. Wanida Putthividhya <wanidap@cs.tu.ac.th> Dept. of Computer Science, Thammasat University, Thailand. Wanida is looking for more than setup a monitor node, she is interested to use pinger data to propose a forecasting model for internet performance. Les has sent her information on getting updated daily information from the SLAC archive via FTP, see Retrieving Archived PingER hourly data from Anonymous FTP

    • Dr. Charnsak Srisawatsakul <charnsak.s@ubru.ac.th> Faculty of Computer Science, Ubon Ratchathani Rajabhat University, Ubon Ratchathani, Thailand wishes to install a PingER Measurement Agent

    • Hopefully, we can collaborate with them and others in the near future.

    • In addition'Chaisit Choosong' <chaisitc@gmail.com> has installed the PingER traceoute server and the pinger2.pl measurement agent at Rajamangal University of Technology Srivijaya, Thailand. We are working on getting the ping_data.pl gathering agent to work.

  • Adib has submitted the paper on Internet Performance and its Reflection on Socio-economic Development in the ASEAN Countries to Social Sciences Review.

  • We are still  working

  • Adib has written a very nice paper on a case study of ASEAN countries Internet connectivity seen from SLAC and relating that to various socio-economic indices. Is there an update 12/4/2016

  • We are working with SLAC the DoE etc. to get an invite to Adib to visit SLAC..

  • Adib asked a student (Jaafrau)  to explore  “Creative visualization of PingER data, including rich interaction;”.  He has come up with a good design, yet the development part needs a lot of work. Adib will ask him to upload his interface and share the link. No update 8/24/2016 is there an update?Adib has another student starting in September. Adib will look at directing him to PingER.  Any update?

  • Adib had a meeting with Mr. Chaisit Choosong <chaisitc@gmail.com>, from Rajamangala University of Technology Srivijaya last week. Adib  gave him a brief about PingER project, aim, objectives, and its installation requirements.  He is interested to setup a PingER monitoring node at his site. Adib sent another email to introduce Chaisit to Dr. Les and hopefully, Les has followed up with an email on 8/21/2016 with an invitation and information on how to set up the monitor. Adib  will follow  up.  We at SLAC have not heard anything 10/26/2016, Sent an email 12/4/2016.

...

  • However the student chose another topic.

UNIMAS No update from Johari

pinger.unimas.my was not pingable. Fixed.

...

Johari looking at a PingER workshop May 17th 2017 at Unimas.

UAF (Saqib)

...

No update from Saqib  12/14/2016

MA Device The MA at UAF is ready to go, it just needs a port. , will assign live IP to machine next week, then will contact Les to try and gather data.

Saqib has been talking to Muhammad Asif of the Nationall University of Textiles, Discussed last week to put up MA and get a student. Arshad was the Chancellor.

Huawei working with Arshad to sign an MoU to place a researcvh research establishment in Pakistan 

...

HostStatelast seenStatus
brunsvigia.tenet.ac.zaNo data since October 31st, 2016, email 11/21/2016, fixed 24 Nov 2016Oct 31, 2016Does not ping
pinger.ictp.itNo data, email 11/21/2016, 11/27/2016, fixed Dec 2nd,20916Oct 28, 2016Does not ping
pinger.ascr.doe.govNo Data, email 11/21/2016, contact email changed sent again 11/27/2016, fixed Nov 30,2016Oct 30, 2016Does not ping
t2-monitor.ultralight.org Host changed unable to reach, no dns, email 11/21/2016. Problem with certs and DNSAug 12, 2016 
www.hepgrid.uerj.br

Due to a major issue with the cluster's electrical infrastructure we will have to shut down all machines, in order to preserve our hardware. The cause of the outage is still being investigated. 

Sept 31, 2016Does not ping
www.univ-ouaga.bfUnreliable, No data since June 20th. Several emails but most recent have bounced. Probably will have to disableJune 2016Does not ping
pinger.nchc.org.twEmail sent 12/4/2016. Fixed 12/5/2016.Nov 27, 2016Does not ping
perfsonar-unimas.myren.net.myNo data August 2016, pings., Emailed Fitzi 8/20 /2016, 10/16/2016, 11/21/2016, 12/4/2016. Fitzi is out of town.7/31/2016Not pingable

NUST

 

From now onwards, Dr. Wajahat (Faculty member) and Mr. Ajmal Farooq (Network Administrator, SEECS) shall be coordinating with us. 

Dr Wajahat sent email "Myself, Mr. Ajmal and an intern, is the new SEECS team assigned to look after the pingER Pakistan. Here is my brief introduction (https://es.linkedin.com/in/wajahat-hussain-13a2907b). Right now we are in the transition phase. Hopefully by the end of this week we will be in the position to update you".

If possible we'll also want to know the exciting questions on your mind. Master students are eager to work on this project."

reportedthat NUST is now ready to help other sites re-install the PingER software. Some sites have dismantled teh monitors and some of the Points of Contact have left. They are trying to make contacts and provide technical help and hardware. there has been some delys in finding the right person. Once they have the contact etc. then they are in a position to fix in a few hours.

Just before the last meeting (September) Mian Abras Abar said he would make a report and email that to me.  Sent a reminder to Mian 11/21/2016 and again 12/4/2016.

...

comsatsswl.seecs.edu.pk host is pingablewas pingable, FIXED 12/6/2016
maggie1.seecs.edu.pk host is pingable, FIXED 12/6/2016
namal.seecs.edu.pk host is not pingable
pinger.comsats.edu.pk host is not pingablepinger.nchc.org.tw host is not pingable

Next Meeting

Next meeting:  Wednesday Dec, 7th Jan 11th 8pm Pacific time,  Thursday Dec 8thJan 12th, 2016  9:00am Pakistan time, Thursday Dec 8th Jan 12th 2016 12:00noon Malaysian time

...

Old information

Amity - Java approach (A. Sai Sabitha and Shivnarayan Rajappa)
  1. They are using the native java tools, they are not running the pinger2.pl <http://pinger2.pl>  script on android since the native java tools have the following advantages
    1. easier for user, 
    2. no need for prior installation of any software, e.g. load perl interpreter which may require missing skills, especially for a non technical user
    3. doesn't need a rooted phone
    4. only the apk needs to be installed to run
  2.  They have fixed the final sequence number change by using regex, and  pushed these changes to github repository.

  3. They have installed apache tomcat in the server and plan to use a java file on the server which would connect to the phones that send the request. This java file will then take the input stream received from the phone and write the output stream to a file that would be stored on the server. We are facing some problems regarding a blocked port that is not allowing the phone to connect to the server we are currently working on resolving the issue.

  4.  SLAC can then regularly pull these files which would be stored based on the month they are received. 

  5. The Android students have started writing a paper on " implementation  of pinger  on android " .

  6. Next steps:

    1. Extend the target list by getting the Beacon list from SLAC. It is at http://www-iepm.slac.stanford.edu/pinger/pinger.xml on a regular basis and updating the <BeaconList> section at their site. This was part of pinger2.pl

    2. Also they will need a utility to clean out old recorded data (say older than 3 months), since it will be gathered from SLAC (via the proxy) and eventually they may run out memory on the Android.
Discussion

To a large extent it depend on how we plan to use this.

  • If the phones are just MAs in a fixed location then simply porting pinger2.pl is easier and probably sufficient.  
  • If this is intended to grow into a mobile application for general use then it needs to be the Java implementation.

A next step is to get the data from the phone MA to the archive at SLAC. The current method ping_data.pl requires a public IP address for the phone which may not exist if its is mobile. Getting the MA to put the data to the archive may raise some security issue for the archiver.

...