Data Collection for Latency, Goodput & Jitter - Demo Pt 5.2

Everyone who I have spoken to about my work since yesterday, has asked me the same question. Why are you writing this in Java ? The answer is that I am going on the Google European Android Development Camp in a few weeks so I am using Java were possible in my work so that I can get familiar with the basics again.

To ensure that the server (my laptop) and the client (my android phone) can address each other I ensure that they are behind the same NAT so that private IP addresses can be used. This ensures that both devices can initialize an connect with the other

My Java code for analyzing and comparing Signpost Diagnostic Application to the results generated by Iperf and Ping, requires the following files:

• SignOutput.txt - this is generated by the Signpost Diagnostic Application, It can be generated by:
• Hard coding the server IP address into the application code, found here
• Uninstall previous versions of the application and connect the android phone via USB
• Within eclipse, load the application onto the android phone
• cd into Downloads/android-sdk-linux/platform-tools
• In another terminal, cd into the location of the demo server and start server using ./server.native
• use "./adb logcat-s SIGPST >> SignOutput.txt"
• The location of the file SignOutput.txt is now Downloads/android-sdk-linux/platform-tools, copy the file to /TestingSignpostAppOutput
• IperfOutput.txt - this is generated by a remote shell on the Android phone, it can be generated by:
• (In terminal 1) cd into Downloads/android-sdk-linux/platform-tools
• connect android phone via USB
• use "./adb shell" to start a remote shell 
• in another terminal (terminal 2), cd into /TestingSignpostAppOutput so output file is loaded straight into correct directory
• (In terminal 2) use  iperf -s -u >> IperfOutput.txt
• (In terminal 1) use iperf -u -c {insert laptop IP}
• PingDownstreamOutput.txt - this is generated by the server sending pings to the client (the android phone), it can be generated by:
• cd into  /TestingSignpostAppOutput so output file is loaded straight into correct directory
• Run a bash script containing the following:
• #!/bin/bash
  
  for i in {1..10}
  do
    ping {insert phone IP} -c 10 -n -q >> PingDownstreamOutput.txt;
  done
• PingUpstreamOutput.txt - this is generated by the client (android phone) sending pings to the server, it can be generated by:
• cd into Downloads/android-sdk-linux/platform-tools
• Save a bash script (lets call it pingUp) containing the following
• #!/bin/bash
  
  for i in {1..10}
  do
    ping {insert laptop IP} -c 10 -n -q >> PingUpstreamOutput.txt;
  done
• Connect android phone via USB and copy script to SD cards using  "./adb push pingUp / sdcard/   "
•  use "./adb shell" to start a remote shell 
• In the remote shell cd into /sdcard
• In the remote shell run the script using ./pingUp
• exit the remote shell
• cd into  /TestingSignpostAppOutput
• copy the PingUpstreamOutput.txt file to the laptop from the android phone using "./adb pull /sdcard/PingUpstreamOutput.txt  

Once you have generated all of these files then you can run my program SignpostOutputAnalysis.java found here which should output the average true and estimated latency, goodput and jitter.


The code in SignpostOutputAnalysis.java is still incomplete and untested, I also have not yet tested my instructions for generating the correct files at the correct locations for the java code to be ran. I will be doing this testing next...

I'm back from brussels

From this ...

I arrived in the back in Cambridge yesterday afternoon after the IBM EMEA Best Student Recognition Event 2012 in Brussels, Belgium. The theme of this years 3 day event was "Data Analytics". The highlight for me on Wednesday 4th July was the a semenar by Prof. Bart Goethals, a lecturer at University Antwerp on data mining and machine learning in data analytics. For Thursday 5th July my highlights were a talk by Corinna Schulze from the IBM Governmental Program on privacy and a talk by Robert-Jan Sips focusing on how data analytics is being applied to water management in the Netherlands.  And for the final day was highlights was a talk by Guy Lefever on the application of Watson to future medical care. Overall I really enjoyed the event and I would throughly recommend attending if you get the opportunity to go.

It looks as if I'm going to have some new work on Signposts next week but I don't know as yet what this will be so over the weekend I intend to review some of the new material that I've learned over the my first few weeks on the Undergraduate Research Opportunities Project (UROP) here at the William Gates Building, Cambridge. My initial project brief was:

" Signposts - the virtual personal internet 

Users with multiple networked devices are having a hard time linking them up when said devices reside at more than one location. Simple example is trying to synch your android phone while on the bus to the laptop in your office and the Mac Mini at home. NATs and Firewalls and other obstacles to symmetric communication abound, and obstruct. Point solutions (Dropbox, iCloud) do not deal with many cases (different OS) and only work if you pay (with money or eyeball time on adverts). In any case, they are not acceptable to privacy conscious users.

Instead, we are building a system called signposts. This is the smallest conceivable virtual machine that sits in the public internet, and looks after your personal namespace of devices. Registration and lookup of names is "effectful", in other words, has side effects. The side effect is to use a set of possible tactics to rendezvous between the devices (various techniques for NAT traversal, for example) including possible multiple simultaneous path use, and also allowing for constraints, such as battery life, and price of use of connections. The system sits on top of DNSSEC, but more interestingly, as a piece of Computer Science, makes use of the new Cloud OS software being developed in CL, called Mirage (see http://www.openmirage.org/ and https://github.com/avsm/signpostd

This project is to help with the documentation and testing "in the wild" of signposts. We expect to uncover a lot of problems with different oddities (see http://conferences.sigcomm.org/imc/2011/docs/p181.pdf for examples) that appear, and we need to have good stories to account for what we are doing to the public and to security people. OCaml programming is pretty essential, as well as at least basic understanding of development tools (including git etc) "

Over the last few weeks, I had used a wide range of tools that are new or that I had not previously used to this extent including (in no particular order):

• Unix command line - although this is something that i typically use, I have definitely used it more and for a wider range of applications that ever before
• Git & GitHub - for my 2nd year group project PROTON, we took the (controversial) decision to use Mercurial and BitBucket instead of Git and GitHub like most other group so it been interesting to see how they compare
• Tor - As alot of my work over the last few weeks has been looking at testing the performance of tools for online anonymity, I've made extensively use of the onion router
• Orbot - Tor for android
• Tails - An OS build around tor  
• Iperf - As just explained as I've been working with testing network performance Iperf has been an invaluable tool (though I have recently discovered Torperf)
• Amazon Elastic Compute Cloud - I've been using this a server when testing network performance, its really use as it provides as global domain name and IP address and avoid pathological cases that could be created by having other cleint and server on the same network
• SHH - for remote access to the other computers I am testing with locally and the virtual machine on Amazon EC2
• dig-host - command line tools for performing DNS queries, just generally useful
• CyanogenMod - the OS on my android phone which allows easy using of proxies and tethering
• Privoxy - heavy customizable non-caching web proxy
• Hamachi - used with privoxy so set up encrypted VPN access
• OpenVPN - easy set up of VPNs
• Texmaker - a nice LaTeX editor, that I would throughly recommend which I have been using to keep the notes on my work over the last few weeks
• Mozilla Firefox & addons - previously a Chrome user myself, I've opted to use Firefox since the research project begin for a change and during this time I have experimented with a range of addons for privacy including: HTTPS Everywhere, NoScript,  AdBlock Plus, DoNotTrackPlus, Collusion ...
• Eclipse & Android Development tools - getting to grips with the basics of Android development in preparation for the Google European Android Camp 
• Telnet - for commend line control of Tor
• Wireshark - very useful for learning about computer networking, allows you to watch the packets on the network
• TraceRoute - brillient tools which used TTL to should the route that a packet takes to its destination
• Ocaml - the main project that I'm working with over the summer makes extensive use of Ocaml

I plan to use this list to visit some of the material that I've learned over the last few weeks in preparation for new work next week.