Italiano English
Modifica History Actions

Differenze per "ObampDocsEnglish"

Differenze tra le versioni 1 e 7 (in 6 versioni)
Versione 1 del 2007-04-17 21:46:10
Dimensione: 3145
Autore: ZioPRoTo
Commento:
Versione 7 del 2007-04-26 15:08:56
Dimensione: 3299
Autore: ZioPRoTo
Commento:
Le cancellazioni sono segnalate in questo modo. Le aggiunte sono segnalate in questo modo.
Linea 21: Linea 21:
Export the ANT_HOME variable and update your PATH variable. We assume you have already installed a JDK and correctly exported the JAVA_HOME variable Export the {{{ANT_HOME}}} variable and update your {{{PATH}}} variable. We assume you have already installed a JDK and correctly exported the JAVA_HOME variable
Linea 23: Linea 23:
For example, if ant_home is the directory where you untarred Apache Ant and java_home is the directory where is your Java JDK: For example, if {{{ant_home}}} is the directory where you untarred Apache Ant and {{{java_home}}} is the directory where is your Java JDK:
Linea 39: Linea 39:
At this point go with your shell into the trunk directory of the source code ( {{{ OBAMPxP\trunk }}} At this point go with your shell into the trunk directory of the source code {{{ OBAMPxP\trunk }}}
Linea 47: Linea 47:
When the compiling process is finished you will find a bin directory with all the compiled classes and a dist directory with the binary distribution OBAMPxP.jar and the needed configuration files When the compiling process is finished you will find a bin directory with all the compiled classes and a dist directory with the binary distribution {{{OBAMPxP.jar}}} and the needed configuration files.
Linea 49: Linea 49:
== Compilare in Gentoo Quick Guide == == Compile on Gentoo Quick Guide ==
Linea 51: Linea 51:
Prima come root emergete Apache Ant As root emerge the Apache Ant ebuild
Linea 57: Linea 57:
Poi con il vostro utente scaricate compilate ed eseguite! Now with your normal user you can compile and execute!
Linea 60: Linea 60:
cd /home/utente cd
Linea 68: Linea 68:
Ora leggete il resto della documentazione per i dettagli! Gentoo specific guidelines are over... follow the rest of the documentation!
Linea 70: Linea 70:
== Esecuzione del proxy OBAMPxP == == Using OBAMPxP proxy ==
Linea 72: Linea 72:
Prima di avviare il proxy, bisogna editare correttamente i file di
configurazione "obamp.cfg" e "obamp_nodes.txt".
Nel primo file le uniche modificche importanti da fare sono inserire il
corretto indirizzo IP della macchina su cui si vuol far girare il
protocollo ed il sistema operativo usato (Windows o Linux), sono le voci
incluse tra i tag <local_address> e <Operative_System>.
Nel secondo file invece va inserita la lista dei possibili indirizzi
IP partecipanti alla sessione di multicast.
Before starting the proxy, you must edit the following files:
Linea 81: Linea 74:
Una volta settati corretamente questi parametri, si può eseguire il
file OBAMPxP.jar con un semplice click del mouse, oppure da
shell con il seguente comando:
        java -jar OBAMPxP.jar
Per avviare la sessione, premere il pulsante Join sulla GUI di OBAMPxP.
{{{
obamp.cfg
obamp_nodes.txt
}}}
Linea 87: Linea 79:
== Invio e ricezione di dati multicast == In the first file insert the IP address of your machine, and the operating system you are using.
Currently only ipv4 is supported
Currently only Windows and Linux are supported.
Mac OS X and BSD support is coming soon.
Linea 89: Linea 84:
Le porte locali per la ricezione e l'invio dei dati sull'albero di
multicast sono rispettivamente la 9000 e la 9002.
Se per esempio vogliamo trasmettere una canzone tramite VLC
al gruppo di multicast dobbiamo settare VLC in modo che trasmetti
all'indirizzo della macchina locale (localhost) sulla porta 9002. Per
la ricezione invece dobbiamo mettere in ascolto VLC in locale sulla
porta 9000.
{{{
<local_address>
<Operative_System>
}}}

In the second file we have to write the list of the IP addresses that are running OBAMP on the network
This file must be exactly the same on every PC partecipating to the multicast session, so it could be a good idea to place it on a web server on a RSS feed stuff.

I know this sounds stupid, but a patch is on the way to avoid this step.

Once parameters are set correcty you can execute the OBAMPxP.jar clicking
on it with the mouse or opening a shell
{{{
java -jar OBAMPxP.jar
}}}

To start the OBAMP session click on the Join button on the GUI

== Sending and receiving multicast data ==

Local ports for sending and receiving on the multicast overlay tree are

sending 9000
receiving 9002

For example if you want to trasmit data with VLC to the multicast group
you have to set VLC so that it trasmits to localhost on port 9000

To receive data we have to set VLC to listen on localhost on port 9002

Of course ALL ports mentioned are UDP

OBAMP

Overlay Borůvka Based Ad-hoc Multicast Protocol BR

Project home page: http://www.radiolabs.it/obamp/ BR

The source code of OBAMP is on our SVN server

You can use the nice Trac interface http://test.ninux.org/svntrac/browser/OBAMPxP/trunk

Or you can checkout the code

svn co http://test.ninux.org/svn/OBAMPxP/trunk

Compile the sources with Apache Ant

First download the last version of Ant at the following URL: http://ant.apache.org/bindownload.cgi Untar the file somewhere in your file system. Export the ANT_HOME variable and update your PATH variable. We assume you have already installed a JDK and correctly exported the JAVA_HOME variable

For example, if ant_home is the directory where you untarred Apache Ant and java_home is the directory where is your Java JDK:

1) On a Linux Box:

export ANT_HOME=/usr/local/ant_home
export JAVA_HOME=/usr/local/jdk_home
export PATH=${PATH}:${ANT_HOME}/bin:${JAVA_HOME}/bin

2) On a Windows PC:

set ANT_HOME=C:\ant_home
set JAVA_HOME=C:\jdk_home
set PATH=%PATH%;%ANT_HOME%\bin;%JAVA_HOME%\bin

At this point go with your shell into the trunk directory of the source code  OBAMPxP\trunk  and execute

ant dist

to compile automatically all the sources

When the compiling process is finished you will find a bin directory with all the compiled classes and a dist directory with the binary distribution OBAMPxP.jar and the needed configuration files.

Compile on Gentoo Quick Guide

As root emerge the Apache Ant ebuild

emerge dev-java/ant

Now with your normal user you can compile and execute!

cd
svn co http://test.ninux.org/svn/OBAMPxP/trunk/ obamp
cd obamp
ant dist
cd dist
java -jar OBAMPxP.jar 

Gentoo specific guidelines are over... follow the rest of the documentation!

Using OBAMPxP proxy

Before starting the proxy, you must edit the following files:

obamp.cfg
obamp_nodes.txt

In the first file insert the IP address of your machine, and the operating system you are using. Currently only ipv4 is supported Currently only Windows and Linux are supported. Mac OS X and BSD support is coming soon.

<local_address> 
<Operative_System>

In the second file we have to write the list of the IP addresses that are running OBAMP on the network This file must be exactly the same on every PC partecipating to the multicast session, so it could be a good idea to place it on a web server on a RSS feed stuff.

I know this sounds stupid, but a patch is on the way to avoid this step.

Once parameters are set correcty you can execute the OBAMPxP.jar clicking on it with the mouse or opening a shell

java -jar OBAMPxP.jar

To start the OBAMP session click on the Join button on the GUI

Sending and receiving multicast data

Local ports for sending and receiving on the multicast overlay tree are

sending 9000 receiving 9002

For example if you want to trasmit data with VLC to the multicast group you have to set VLC so that it trasmits to localhost on port 9000

To receive data we have to set VLC to listen on localhost on port 9002

Of course ALL ports mentioned are UDP