Versions Compared

Old Version 9

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:  Week of April 15-18  July  11th 10 pm Pacific time (Nb now on summer time); a day later 10:00 am Pakistan time; 10:30 am India time; 1:00 pm Malaysian & Guangzhou time;  12:00 pm Thailand time; 7:00 am Jordan and 6:00am Turkey.  

Doodle poll invites sent 5/27/2019.

Format

New items and updates are in boldface. Action/discussion items are in red

Coordinates of team members:

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

  • Saif A. Kazakzeh (xsaifahmadx@gmail.com) of Jordan added.

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+

  •  + Responded via Doodle will can 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 umar.kalim@gmail.com; xsaifahmadx@gmail.com
Actual Attendees

BeboSaqib, SaqibWajahat, Les

Others

Administration

Use of Zoom

  • Dr. Umar Kalim has left SLAC to join Amazon. He will continue to be in the Bay Area. He will continue to be involved in the PingER project. 
  • Bebo's SLAC account expires March 2020. He will not be able to renew it, since he will no longer be a SLAC employee. As a result Bebo will likely let his participation in PingER lapse.
  • This meeting was scheduled with the aid of a Doodle poll.

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

) 

What: PingER Standing Meeting
When: June 11, 2019 10:00 PM Pacific Time (US and Canada)

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

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

Jordan  (Updated 3/6/2019)

Turkey

Email from Eyad Ayoubi 3/16/2019.
"I'm almost settled, and waiting for my residency ID. ...
For installing Pinger MA in Turkey, I will do it soon, but first I need a PC for this purpose and I, unfortunately, don't have an extra one, however, I do my best to find a cheap PC to use, and then I might need some help during installation and I will contact you and Baraa".  A possibility might be to send him the Raspberry Pi that we used to run a PingER MA on at SLAC for a couple of years.  Email sent 4/3/2019. Response 4/4/2019: "I am asking about the process of having public IP address because I understood that we need public IP for the agent"

Amity (Updated 3/3/2019).

Amity team photo:

Image Removed

The following are the data analysis projects:

  • Title (tentative): Correlation Analysis between network performance and GDP of a country using PingER data. Abstract (tentative):
    This paper aims towards finding the correlation between Gross domestic product (GDP) of a country and it’s network performance (ping analysis) 
    using PingER data. Email ID: Naman Madan, naman.madan25@gmail.com 
  • Title (tentative): Comparison of network performance of India and Pakistan using PingER data. Abstract (tentative):
    This paper aims at comparing the network performance of India and Pakistan using the PingER network performance data of 2-3 years of both the countries and applying clustering to the year-wise data. Comparing the number of components in each cluster will help in concluding the quality of the network performance. More the number of the components, with the least average RTT, better the performance. Email ID: Vishwani Sati, vishwani.sati@gmail.com 
  • Title (tentative): Data packets loss prediction due to environmental factors.
    Abstract (tentative): Pinger data losses during certain environmental factors like – Earthquakes, heavy rainfalls, Tsunamis etc, are a major concern for the big companies, delay of few seconds will lead to huge customer breakdown. To deal with this situation, we will analyze the data losses trend with respect to the external environmental factors and will predict the data losses beforehand so that company will have upper hand if some crises stricks in future. We will analyze the Pinger data and environmental conditions attributes and will make an algorithm that will predict the losses in pinger data. Email: Gurpreet Singh, gurpreetn92@gmail.com.

Android progress:

  • 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 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.
  • 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.
  • We have requested (emails 3/6/2019, 3/15/2019) to know 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 gathering/storage/analysis to be backward compatible. Thus 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.

Work Flow for the PingER App

1. The user opens the application. The layout consists of a ListView displaying the hardcoded IP addresses from the SLAC website along with two buttons- one to ping the beacons and the other to get the location of the user. 

2. On Clicking the “Ping” Button each of the hardcoded IP addresses is pinged and the output is displayed on the screen.

Image Removed

3. On Clicking the “Get Location” button the current location of the user is displayed. Google Geolocation API is used to implement this feature.

Image Removed

 

Flowchart of the Application

Image Removed

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, reminder sent 4/4/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 difference would probably require a change in meeting time (e.g. 10:00 pm SLAC = 6:00 am Turkey)

...

He will discuss with the department head about installing a PingER MA there.

Exit plan for PingER - Discussion Topic

Time to start thinking about this. Do we need one?

  • Les retired, still active.
  • Bebo's SLAC account expires early 2020, he will bow out then.
  • Topher busy getting funding etc.
  • Umar has left SLAC, but still involved.
  • In the over two decades since PingER started, the Internet and wide area networking have changed dramatically
    • Speeds, deployment,  reliabililty, number of users and applications have improved exponentially
    • There are lots of other monitoring tools nowadays: perfSONAR, ISP monitoring, Akamai

What does it affect?

  • Pakistan monitoring - Wajahat
    • What is the commitment from Pakistan?
  • China - monitoring; big data, blockchain - Saqib
    • Is the current historical data sufficient?
  • ePingER on Android - Amity, Bebo, Topher
    • This is new, Amity would need to take leadership
    • Topher is very busy with getting funding and other projects
    • Bebo less interested partially due to loss of SLAC account early next year
  • Three PingER analysis projects - Amity
    • Title (tentative): Correlation Analysis between network performance and GDP of a country using PingER data. Abstract (tentative):
    • Title (tentative): Comparison of network performance of India and Pakistan using PingER data. Abstract (tentative): 
    • Title (tentative): Data packets loss prediction due to environmental factors. 
    • Is the current historical data sufficient?
  • Compare IPv4 with IPv6 and ICMP versus UDP versus TCP pings - Umar
    • Umar in new job may not have resources/time
    • Measurements probably do not rely on PingER project, rather they can be made ad hoc.
  • Monthly meetings - Les, Umar
    • Scheduling with doodle - Les
    • Making up agenda and current status - Les
    • Invitation via Zoom - Umar
    • Attending - all

Possible scenarios

  • Hard stop
  • Soft stop:
    • Continue running monitors, gathering data, archiving and presenting  as long as SLAC provides storage (1TB) and pinger.slac.stanford.edu VM
      • Give up on monitors after email prompt and no resolution
      • Do not add any extra functions
    • Keep historical data publicly available as long as SLAC provides storage (1TB) and pinger.slac.stanford.edu VM
  • In either case explore what role the Internet Archive might play in maintaining/storing PingER data.
  • Meet with Amity, Topher, Bebo, Les to get their input to
    • Access to PingER historical data
    • their taking leading role
    • ePinger Android futures

Jordan  (Updated 4/25/2019)

Turkey (Updated 4/25/2019)

Eyad emailed: "I have gathered some information about how to have a public IP address and it seems it is not complicated, just a subscription with the ISP, I will discuss in the next meeting". Sent email requesting update 5/26/2019. Eyad responded no progress yet.

We also received an unsolicited email:
" We are employing PingER in Hasan Kalyoncu University, in Turkey, for the purpose of conducting researches on the Internet performance in Turkey. 
Actually, we have collected data in our node, so we would like our collected data to be retrieved by the archival site at SLAC. Below are the details information on our monitoring node.
 
  • DNS: pinger.hku
  • Public IP:  10.15.2.146
  • Node Coordinates
  • Latitude: 37.014764 Longitude: 37.205743
  • Node Location: Şahinbey Mahallesi, Havalimanı Yolu 8.Km, 27000            Şahinbey/Gaziantep
  • Contact Person: 
  • Name: Mohammed Madi
  • Designation: Assistant Professor in Computer Engineering Department
  • Contact Number: 00905537717593
  • Email address: mohammed.madi@hku.edu.tr
Thank you in advance, looking forward to hearing from you"
Unfortunately, this appears to be a private IP address so is not accessible.  Les sent an email 4/19/2019 to Mohammed. Mohammed provided a public IP address ( 95.0.84.5), however, it is not pingable and the URL does not respond. Sent another email 4/24/2019, 4/28/2019, 5/7/2019, 5/26/2019.
Also sent email to Adib (who is in Turkey) and Eyad in case they know the person or site. Adib responded 4/20/2019: "Yes, I know Mohammed, he graduated from UUM (Malaysia), and we worked together at the same department. He is a good researcher. I think, he can contribute to PingER project."

Amity (Updated 4/25/2019).

Amity team photo:

Image Added

Android progress:

  • Instructions from Aayush to load the application are at ePingER Functional prototype (for Androids only)
    • They sent a new copy of the app 4/6/2019, see ePingER Functional prototype
      • The information has been passed to Topher, who plans to install on an Android. The ball is now in our court
      • There is a discussion between Les and Aayush on how to format the raw data records, in particular with respect to the lat/long. Sent a reminder 4/18/2019.
      • We (SLAC) an email to Aayush asking how we gather the raw data from the cloud. Sent reminder 4/18/2019.
        • Aayish responded 4/18/2019: 
          Yes, we have modified the app to write the semi-colon to the file as a separator.
          However, at this point we suggest you to not make any changes to the pinger project yet. 

          Let us see and run in this parallel to what is already setup at Amity MA. This will allow us to compare the quality of results by both the systems – one at present which does not utilize the app, and the new one which requires an app for data collection.
          We send the data from the app to the firebase cloud service as JSON objects via a REST API. 
          On the cloud-server side, we intend to build a compute-service that automatically converts the json data to a txt format, for consumption by data researcher team at amity (because they are already used to running analysis on the txt files; but seem to be open to working with JSON data as well). [For the SLAC gatherer we would at least initially prefer the data to be retrieved/available in txt form. This way the changes to the gatherer are minimized and more consistent with current practice.]

          So once the team finds that the results are significant enough, then we can formally propose to include lat/long data in the Pinger gathering, archiving and analysis.
          For now, it would be best that we do not disturb the current Amity MA, and that the android project runs parallel to this."
  • Topher is back, Bebo is contacting him. Bebo's thoughts were that:
    •  If the Amity app is robust  (i.e. it does not noticeably impact the other services, power, networking, security etc) make it part of the standard Rainforest installation;
    • Topher's package knows the GPS location, so it should be available to PingER for recording.
  • PingER will need a fixed name for each Android MA.  Since the Android may be mobile the IP address may be dynamic. There is a DNS name to dynamic IP address service that may be useful. Maybe there is another unique fixed identifier in an Android that could be used such as a serial number or SIM ID.

Adib (Updated 3/3/2019)

...

Title: Socio-economic Development Indices and Their Reflection on Internet Performance in ASEAN Countries

Corresponding Author: Adib Habbal

Co-Authors: Les Cottrell, Emmanuel Mkpojiogu, Bebo White, Suhaidi Hassan, Faisal Zulhumadi

Unfortunately, it was rejected.
Adib, Bebo and Les are looking for another journal, some possibilities include: https://webscience-journal.net/webscience, 

...

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

 

NUST: (Updated 3/3/2019)

  • 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? Email sent 3/15/2019):

    • 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?
  • Wajahat also suggested a letter to the higher-ups at NUST about PingER would assist.  Les worked with Wajahat to craft such a letter.

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/GHZU (Updated 3/3/2019)

  • Saqib 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, 3/15/2019.

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.

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

 

PingER at SLAC  

 

better choice. Adib  submitted it to the 2nd journal. He sent email 4/20/2019: "we received an unfavorable response from the information society. So sad that this paper does not get enough attention from journal editors. But I will keep trying, let's pray for the best." 

It has been submitted with the title: Submission title: Socio-economic Development Indices and Their Reflection on Internet Performance in ASEAN Countries to Engineering Science and Technology, an International Journal. They have requested a re-submission "Please apply "author template" which can be found in "guide for authors" page. We declare in our Guide for Authors page that: All authors are requested to use the Author Template and prepare their articles as the editorial board of the journal has decided to limit all published pages within 10 pages. Therefore, we do not proceed with the peer-review process if authors do not submit their articles using the Author Template and limit the manuscript to 10 pages including all content."  

 

Kind regards,

 

JESTECH Editor

 

 

 

Engineering Science and Technology, an International Journal

 

Corresponding author: Dr Adib Habbal
Listed co-author(s): Mr Faisal Zulhumadi, Mr Emmanuel Mkpojiogu, Professor Suhaidi Hassan, Professor Bebo White, Dr Les Cottrell

 


 

 

 

NUST (Updated 4/25/2019) 

Wajahat suggested a letter to the higher-ups at NUST about PingER would assist.  Les worked with Wajahat to craft such a letter. It was sent to Wajahat by email 4/3/2019.  It was sent by paper mail 4/4/2019 to Principal SEECS.

  • Wajahat said the letter has been received and a written response is being drafted.
  • They (NUST) would also be interested in other collaborations with SLAC
    • Since Les is no longer an employee of SLAC but rather an emeritus this may complicate things.
    • A possibility might be in high-speed data transfer. It would need a champion from NUST, and a plan and funding to provide access to 100Gbps

 

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.

Wajahat has 2 students, he will propose some PingER related projects to them.

Wajahat said that contacts at some sites are not very interested in PingER and wonder why there are so many pings. Thus he believes we need new sites representing the regions of Pakistan that have willing collaborators. Thus we should give up on sites such as CAE and ISRA that have not had any data to gather for a year or so.  Les has since disabled these sites.

We have not been able to gather data from maggie1.seecs.edu.pk since March 2019. Sent email to Wajahat, he responded that it may be an IPv6 host.  Tried accessing using IPv6 but no success.

 UAF (University of Agriculture, Faisalabad)/GHZU (Updated 3/3/2019)

Saqib joined the University of Agriculture in Faisalabad. He plans to pursue the blockchain paper.

Thailand, Charnsak

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. 4/9/2019 Charnsak said we need to drop this.

UNIMAS

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.

Email from Johari 4/21/2019:  I am still very much interested in the project but I have to manage my time better. Will try to join the next meeting and probably get someone from my side to monitor the equipment and make use of the data collected

SLAC (Updated 4/25/2019) 

Umar fixed up the PingER deployment map at http://wanmon.slac.stanford.edu/wan-mon/viper/pinger-coverage-gmap.html by updating the Google map key. Also they shut down (since it did not support SSL) a web server (www-wanmon.slac.stanford.edu) I was using which is causing some PingER web cronjobs to fail. Nothing too serious at the moment, I am working to see if the problem can be fixed.  Also tighter security was imposed on https which broke some links to get the pinger.xml configuration file.

State of MAs.

Fixed 4/5/2019 March 19, 2019. The host is pingable and web is responding. Email sent 4/3/2019. Recommend update ping_table.pl
Host
State
last seen
Status
pinger2.if.ufrj.brUnable to gather data since 1st July, 2019. Senet email 6/2/2019 to Vinícius Ferrão <ferrao@if.ufrj.br>, he responded that there had been a power outage and he has re-established it.6/1/2019Fixed 6/3/2019
pinger.uum.edu.myUnable to gather data since 2nd May 2019. Host is pingable. Sent email 5/5/2019 to Adib, he will contact Dr. Suhaidi. Sent reminder 5/14/2019, Adib has contacted Dr Suhaidi who will get someone to help. Still down 6/2/2019, sent another reminder to Adib.5/2/2019 
pinger.es.netUnable to gather data as of May 24th, 2019. Host is pingable. May have run out of disk space. Sent email 6/2/2019 to Chin Guok suggesting update ping_data.pl and install the data trimmer. Chin responded 6/3/2019, looking at updating ping_data.pl first to diagnose the problem. Installed new pinger2.pl, ping_data.pl and updated pinger.xml to add <BeaconList>.5/24/2019Fixed 6/5/2019
pinger6.cs.ubru.ac.thUnable to gather data, pings. Email sent 5/24/20195/20/2019Fixed 5/29/2019
pinger.unimas.myUnable to gather data, does not ping. Email sent 5/24/2019. Johari responded that he will look at it. Sent reminder 6/2/2019.5/20/2019 
HostStatelast seenStatus
pingeramity.inUnable to gather data since March 29, 2019, unable to ping it, sent email 4/3/2019, got response (4/3/2019) they will look into it.March 29, 2019
rainbow.inp.nsk.suUnable to gather data starting March 19, 2019Fixed 4/3/2019
pinger6.cs.ubru.ac.th

Stopped 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, 3/15/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

maggie1.seecs.edu.pkUnable to gather data since March 26, 2019March 26, 2019 
cae.seecs.edu.pkAt the request of Wajahat re-enabled but unable to gather data  

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.

Questions:

...

...

  • Averages and computed. Min RTT is available. Scripts need to be updated to use minRTT.

...

...

4/19/2019, also cannot ping the host. Sent email 4/25/2019. Sergy responded 4/30/2019 he has moved on unclear there is a follow on contact. Probably will disableApril 17, 2019Disabled 5/8/2019.
brunsvigia.tenet.ac.zaLen Lotz the contact is working on getting his people to move MA to a VMApril 17, 2019Moved to VM 5/1/2019
netmon.physics.carleton.caUnable to gather data, host is pingable and http://netmon.physics.carleton.ca/cgi-bin/ping_data.pl? responds. It appears the pinger.xml file is corrupted. Email sent 4/28/2019April 23, 2019Fixed June 30, 2019
pingeramity.inUnable to gather data since March 29, 2019, unable to ping it, sent email 4/3/2019, got response (4/3/2019) they will look into it.March 29, 2019Fixed 4/5/2019
rainbow.inp.nsk.su

Unable to gather data starting March 19, 2019. The host is pingable and web is responding. Email sent 4/3/2019. Recommend update ping_table.pl

March 19, 2019Fixed 4/3/2019
pinger6.cs.ubru.ac.th

Stopped 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, 3/15/2019. Down again 4/23/2019, restored 4/27/2019.

2/25/2019Fixed 3/16/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

Disabled 4/28/2019

maggie1.seecs.edu.pkUnable to gather data since March 26, 2019. Sent email to Wajahar 5/25/2019. Should we Disable it or is someone working on it? Wajahat said it might be an IPv6 node, however, ping6 from pinger.slac.stanford.edu to maggie1 does not work.March 26, 2019 
cae.seecs.edu.pkAt the request of Wajahat re-enabled but unable to gather dataOver a year agoDisabled 4/17/2019

Umar compare ICMP and TCP Ping

Umar is looking at the scamper project from CAIDA, see https://www.caida.org/tools/measurement/scamper/. Les will put Umar in contact with the scamper folks (email sent 4/28/2019)

Unfortunately, for the IPv4 vs IPv6 comparison, there is insufficient data (i.e. only about targets)

...

Next Meeting

Next meeting:  There will be a Doodle poll, April week 15th-18th for August 8-11 8-11pm or August 15-18 at 10 pm Pacific time; a day later 10:00 am Pakistan time; 10:30 am India time; 1:00 pm Malaysian & Guangzhou time;  2:00 pm Thailand time; 7:00 am Jordan time. 6:00am Turkey time.  Any thoughts on time of day. 

...

Old information