...
Prof Abhay Basal, A. Sai Sabitha, Shiv Rajappa, Rohan - Amity; Les, Bebo SLAC
PingER MA - Les
Installation Overview.This is proceeding. They have a working pinger2.pl. They have a public DNS pingeramity.it. They have installed ping_data.pl, it is working:
They fixed one problem by registering pingeramit.on and changing:
...
[cottrell@pinger ~]$ nslookup pingeramity.in
Server: 134.79.111.111
Address: 134.79.111.111#53
Non-authoritative answer:
Name: pingeramity.in
Address: 202.12.103.71
Name: pingeramity.in
Address: 173.193.105.245
The host has been un-pingable for the last two days. They have been experiencing Ethernet problems that they hope to solve in the coming day. Then we will retest.
Traceroute/ping servers - Les
...
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. A There is a document containing these patterns has been attached.
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 attached in the document titled "Basic Ping Output Conversion.docx"
Code Block $ 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
...