...
- 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
Amity (Updated 4/25/2019).
Amity team photo:
Android progress:
...
...
...
I am working on it. but currently I am busy with final examinations and project presentations, submitting the results.
I will be free next week and will fully concentrate on that issue and settle it.
thank you so much for your concern and I am sorry for being late in response. "
Amity (Updated 4/25/2019).
Amity team photo:
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."
- Aayish responded 4/18/2019:
- They sent a new copy of the app 4/6/2019, see ePingER Functional prototype
- 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)
- Adib is wondering about
- Journal of Computer Information Systemshttps://www.tandfonline.com/action/journalInformation?show=aimsScope&journalCode=ucis20
- The Information Societyhttps://www.tandfonline.com/action/journalInformation?show=aimsScope&journalCode=utis20
Bebo reviewed and responded to Adib suggesting the second one is a 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."
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. It has been disabled.
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
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)
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. Les believes most of the problems have been discovered and fixed. www-wanmon has been shut-down.
Les has been working with FNAL to migrate the MA to a new FNAL host, hopefully pretty seamlessly.
Les has read the documents on PingER Metrics Motion Chart and updated the PingER measurement data, the country populations, the Human Development Index and ICT Development Index for the Pinger Motion Charts (see https://www-iepm.slac.stanford.edu/pinger/pinger-metrics-motion-chart.html using Firefox and enabling Flash.
State of MAs.
Host | State | last seen | Status |
---|---|---|---|
pinger.uum.edu.my | Unable 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.unimas.my | Unable 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 | |
pingeramity.in | Unable 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 | Fixed 4/5/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/2019 | Fixed 3/16/2019. |
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)
- Adib is wondering about
- Journal of Computer Information Systemshttps://www.tandfonline.com/action/journalInformation?show=aimsScope&journalCode=ucis20
- The Information Societyhttps://www.tandfonline.com/action/journalInformation?show=aimsScope&journalCode=utis20
Bebo reviewed and responded to Adib suggesting the second one is a 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."
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.
Host | State | last seen | Status | ||||
---|---|---|---|---|---|---|---|
pinger2.if.ufrj.br | Unable 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/2019 | Fixed 6/3/2019 | ||||
pinger.uum.edu.my | Unable 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.net | Unable 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/2019 | Fixed 6/5/2019 | ||||
pinger6.cs.ubru.ac.th | Unable to gather data, pings. Email sent 5/24/2019 | 5/20/2019 | Fixed 5/29/2019 | ||||
pinger.unimas.my | Unable 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 | |||||
rainbow.inp.nsk.su | Unable to gather data starting 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 disable | April 17, 2019 | Disabled 5/8/2019. | ||||
brunsvigia.tenet.ac.za | Len Lotz the contact is working on getting his people to move MA to a VM | April 17, 2019 | Moved to VM 5/1/2019 | ||||
netmon.physics.carleton.ca | Unable 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/2019 | April 23, 2019 | Fixed June 30, 2019 | ||||
pingeramity.in | Unable 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 | Fixed 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, 2019 | Fixed 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/2019 | Fixed 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 | |||||
maggie1.seecs.edu.pk | Unable 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.pk | At the request of Wajahat re-enabled but unable to gather data | Over a year ago | Disabled 4/17/2019Disabled 7/3/2019. |
Umar compare ICMP and TCP Ping
...