...
Membership of pinger-my in https://groups.google.com.
- Johari, Please add Umar to the membership
- Dr. Umar Kalim now of SLAC has re-joined the team, he is in the email list pinger-my@googlegroups.com and also in the membership list http://pinger.unimas.my/pinger/contact.php
Amity
Manuscript titled - Clustering Analysis of PingER Network Data for Vardha Cyclone has been PEER REVIEWED and ACCEPTED for publication in the Confluence-2018:8th International Conference: on the theme “Cloud Computing, Data Science & Engineering” prevented on 11th - 12th January 2018 at Amity University Uttar Pradesh, Noida, India.
- Their PingER MA system has crashed and they are reinstalling the project.
They are having problems with the traceroute server and ping_data.pl (that gathers the data). Les is working with them. I believe traceroute.pl (they have an unusual linux traceroute command that does not support all the options used by PingER) and ping_data.pl are fixed. It looks like pinger2.pl is not running.
...
Currently, no data is available on PingER on Android due to unavailability of the live IP address. No update 4/19/2017, 7/6/2017. Email sent to Sara Masood. No update 9/24/2017. Any update 10/24/2017. No progress 1/18/2018.
PingER at SLAC
Working with Saqib to test pinger2.pl to make it work with IPv6 servers and targets.
- ipv6 connectivity is now available on pinger.slac.stanford.edu, thus I am able to test and fix pinger2.pl MA code to ensure works for IPv6.
- Ran into a problem that IPv6 pings were being blocked at the SLAC border firewalls. This has been fixed.
- A host to test against is ipv6.google.com (2607:f8b0:4007:800::200e).
- gathering of the data from others sites is also fixed,
- aggregation, analysis, and presentation modified and believed fixed but not tested.
- working on meta database to accept IPv6 addresses, close but not done.
...
- Meta database (NODEDETAILS) is now fully ipv6 compliant, need to enter some ipv6 hosts.
- Currently pinger2.pl works for either an IPv4 MA or an IPv6 MA, but not both at once. Thus Saqib has two MAs one for Ipv4 and one for IPv6. Looking at being able to make pinger2.pl work for both. This will enable migration, but will also require a new analysis and presentation, e.g. the ability to select IPv4
...
- or IPv6 measurements or both. I am ready to start testing to see what is broken
Working on Validating ICMP ping measurements against TCP nping measurements.
- Scripts written to generate configuration files for perfSONAR and PingER targets.
- Also have script to compare ICMP/ping RTTs with TCP (syn/ack) RTTs.
- Staring analysis with Excel.
Les has written scripts identify IPv6 pingable hosts in various lists including PingER hosts, perfSONAR hosts.
...
- The agreement looks good.
- Want MAs at SLAC (Les, Umar), China (Saqib), Malaysia (Johari), Thailand (Charnsak), Pakistan (Wajahat?)
PingER data is currently kept on a Sun Solaris file server front ending a a 1TByte disk array. Solaris is no longer supported at SLAC and the disk array is 13 years old so we need to migrate the data to GPFS. Les is working on this and plans to make the move in the next 2 weeks.
| Host | State | last seen | Status |
|---|---|---|---|
| Pakistan | See above. | ||
| rainbow.inp.nsk.su | Unable to gather data or ping host, Sent email 1/26/2018. | Dec 6, 2017 | Does not ping |
| pinger.ascr.doe.gov | Node changed to appsvr2.ascr.doe.gov, unable to ping or gather data, email sent 1/26/2018 | appsvr2 never seen | Does not ping |
| pingeramity.in | Unable to gather data, needs re-installing the MA. Working with Amity, emails Jan 12, Jan 16, Jan 26 | March 22, 2017 | |
| multivac.sdsc.edu | Disabled | Aug 13, 2017 | |
Next Meeting
Next meeting: Thursday, February 22nd 8pm March 28th 9pm Pacific time; Friday, February 23rd March 29th, 2018 9:00am Pakistan time; Friday, February 23rd 2018 12:00noon Malaysian and & Guangzhou .time; and 11am Thailand time.
...
Old information
GZHU (moved here 1/15/2018)
...