Time & date 

Thurs June 16th 2016 ~8:30pm Pacific Standard Time, Friday June17th 2016  09:00am India time

This was a Skype meeting.

Coordinates of team members:

Attendees

Invitees:

Prof Abhay Basal, A. Sai Sabitha, ... - Amity; Les+, Bebo+ SLAC

Actual attendees:

Prof Abhay Basal, A. Sai Sabitha, Shiv Rajappa, Rohan - Amity; Les, Bebo SLAC

PingER MA - Les

Traceroute/ping servers - Les

As of 6/16/2016 202.12.103.7 the PingER MA and traceroute host was unpingable from SLAC

http://202.12.103.71/cgi-bin/traceroute.pl  gives “the web page below:

However clicking on Yes gives:

I.e. the target address is a private Internet address (RFC 1918).  One gets a similar result for http://202.12.103.71/cgi-bin/traceroute.pl?function=ping

This was at least partially due to the host's environment variable REMOTE_ADDR=10.0.253.1 whereas it should be the public address of the remote host but. 10.0.253.1 is a private address so here is no way to traceroute to it. THis has probably been fixed with the pingeramity.in DNS registration. However the host is unpingable.

They will look at setting the REMOTE_ADDR environment variable.

Android implementation of Pinger Measurement Agent - Sabitha

A Github repository has been set up at https://github.com/PingerAmity/PingerAmity

 PingerAmity/PingerAmity <https://github.com/PingerAmity/PingerAmity>

  • A method is being tested where Perl is compiled on Android and pinger2.pl involving Root access and Busybox installation
  • Another method of modifying the output from the standard ping command is also being worked on
  • There have been some irregularities in the output saved on the device running the app mentioned on github. Both the data and a few noted irregularities have been attached
  • It has also been noted that the standard Notepad provided on Windows machines is not ideal for viewing such data (using something like gVim, 010 Editor, EmEditor, etc would be better)
  • Regex Patterns have been tried to capture appropriate values from a given string. There is a  document containing these patterns.

  • Parsing of output of ping commands has been attempted. The ideal case conversion of the command "ping -s 100 -c 10 yahoo.com" results in the following. Please acknowledge if it is in the correct format. More information is in the document titled "Basic Ping Output Conversion.docx"  

    $ ping -s 100 -c 10 yahoo.com
PING yahoo.com (98.139.183.24) 100(128) bytes of data.
[1461422353.807137] 108 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=1 ttl=52 time=254 ms
[1461422354.756784] 108 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=2 ttl=52 time=253 ms
[1461422355.759227] 108 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=3 ttl=52 time=254 ms
[1461422356.760669] 108 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=4 ttl=52 time=254 ms
[1461422357.761238] 108 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=5 ttl=52 time=253 ms
[1461422358.763935] 108 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=6 ttl=52 time=254 ms
[1461422359.764643] 108 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=7 ttl=52 time=253 ms
[1461422360.766194] 108 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=8 ttl=52 time=253 ms
[1461422361.768163] 108 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=9 ttl=52 time=253 ms
[1461422362.769090] 108 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=10 ttl=52 time=254 ms
--- yahoo.com ping statistics ---
 10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 253.745/254.076/254.636/0.387 ms

Scope Overview of PingER Linked Open Data (LOD) and Web Observatory - Bebo

See here.

Other Projects

Action items:

Next Meeting

Old Information

Work in Pakistan placed here 6/16/2016

See here. Also see the notes from the meeting on PingER/Android with Sara and Saqib in Pakistan who are working on this.

They have put together an app written in java that can take a list of hosts and make a set of pings to each in turn. The output appears as:

Pinger2.pl uses the standard Linux ping to make up to 30 pings stopping when it has received 10 responses, so the ping command will need modifying (hopefully there is a java ping option to support this). In addition the output will need to be parsed to produce the pinger2.pl output format. It may be easier to take the pinger2.pl code and run a it under a perl interpreter. This is the approach Sara is taking in Pakistan. They will examine this. If they find serious problems they will communicate that so it can be shared with Sara. Also they will need to check the pinger2.pl documentation to ensure that a java version does the exactly same thing and has the same features.

They do not believe there is a problem with running the equivalent of a cron job to schedule the measurements each half hour.

Apart from this they will look at putting together a proxy that the Android can send the recent data to. Then the SLAC archive site can gather the data from the proxy. The proxy could be replicated at a second site for high availability. Depending on reliability the android should preserve a cache of the most recent data so it can be re-sent later. The least recently used data can be flushed asynchronously.

Student availability

There are two students (Jahin and Ankit Singh)  will be at at the University of Florida who have F1 US visas and will finish at Florida in the 1st week in May. They are then free to come directly to SLAC. They will then continue their studies in the US in August 2016, hence they will be available at SLAC for ~ 3 months. Low cost housing could be an issue. Most of the other students are BTech students at Amity who will graduate in May.  Once we have their names and mutual interest we can start the paper work to get started on invitations. Aditya Pan and Anwesha Mal who graduate in May with a BTech are going to the National University of Singapore. (I am unsure if this  means they are going to University of Singapore after they graduate in May, or before then. Are they candidates to come to SLAC?)

PingER students

The following have written papers on PingER:

  • Aditya Pan has started work on the Android port of the PingER MA
  • Anwesha has started work on looking at the PinGER data and using cluster analysis on it
  • Jahin and Aditya have started work on looking at the PingER data and correlation analysis

Les has copies of these three and has reviewed the Android and cluster analysis papers.  It would help if he could be provided with a copy in word so he could mark up corrections before they go to publication via IEEE.  These students will be working remotely with Les and Bebo at SLAC between now and May.

 

  • No labels