This is an old revision of the document!


Raptor Demos

Introduction

There are 3 demos (in order of setup difficulty)

  • Raptor Image Demo
  • Raptor FTP Demo
  • Raptor Live TV Demo

The image demo is just a standalone application and does not need networking. Live TV and FTP needs networking and various server setup in order to work.

Traffic Control Bridge

The live TV server, and the FTP server are behind a transparent bridge that allows to simulate various network conditions (namely random losses and packet delay). This is done using linux traffic control system.

In order to make it easy to use, there is a simple web-interface for managing it. The code (and the server) for the web interface is in a folder named “tc” inside cangiani's home directory. In general the server is always running inside a screen. If it is not, launch a screen and run ./script/server. The bridge is a simple alix machine. Therefore, the server takes few second to start.

Once the server is running, connect a browser to http://raptortc.epfl.ch:3000 in order to play around with it.

Raptor FTP Demo

The idea of this demo is to compare the speed of standard TCP (HTTP) against our own protocol making use of raptor for FEC. The code is here:

git clone ssh://cangiani@lth.epfl.ch/repos/git/RFTP

Server and client can be compiled with

./make server
./make demo

In order for the demo to work, we also need to setup the demo proxy and a simple web page made of links to files of various dimensions. This is done by running one of the deploy.sh scripts in the source directory. For example,

./deploy_raptordemo1.sh 

will install the proxy and the demo site to /var/www/html/rftp.

Once the proxy stuff is in place, you need to start the server. In raptordemo1.epfl.ch, this is done with

screen
./bin/linux/server -r /var/www/html/rftp/cache

The proxy is just a simple php script (proxy.php) that accepts an url parameter. It downloads the file linked to the url and store it locally. It then returns a key for the local file to be downloaded by the demo client. The demo client then uses either the raptor FTP server, or the standard Apache http server to get the cached file.

In order for the demo to work, its settings should look like the following: Raptor FTP Demo client Settings

Raptor Live TV

This is still badly work in progress and these notes are mostly for myself.

The server is in

ssh -l raptv raptortv0.epfl.ch

from there, we can reach the dvblast server with all the attached tuners.

ssh -l root dvblast0.epfl.ch

There are presently 3 DVB-T adapter connected. You can tune all of them and run dvblast automatically by going to /root/dvblast-conf, editing the first line of go.sh which looks like the following:

freq="562000000 626000000 570000000"

In this case, launching go.sh (ideally inside a screen), will start 3 istances of dvblast each using one of the tuner tuned on one of the above frequencies (562000000, 626000000, or 570000000).

Look into the corresponding server_channels_FREQ.ini file to see how the raptor TV server configuration should look like for each of the channels that will be available assuming that by default there is some raptor coding.