Changes between Version 9 and Version 10 of BaseInstall


Ignore:
Timestamp:
Jan 22, 2009, 9:24:31 PM (16 years ago)
Author:
Christoph Mayer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BaseInstall

    v9 v10  
    2626}}}
    2727
    28 == Running the PingPong Sample ==
     28== Running the !PingPong Sample ==
    2929
    30 -configs anpassen etc
     30The PingPong binary {{{pingpong}}} is installed in {{{build/bin}}}. It has one parameter, a configuration file. You can find sample configuration files in the {{{etc/pingpongconfig}}} folder. Three configuration files are provided. You can start the initiator as follows:
     31
     32{{{
     33> ./pingpong ../../etc/pingpongconfig/settings_initiator.cnf
     34}}}
     35
     36If this will fail to find the {{{libariba}} you may have to set the {{{LD_LIBRARY_PATH} correct:
     37{{{
     38> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/user/ariba/build/lib
     39}}}
     40
     41When running the {{{pingpong}}} application it will output a large number of log messages and the initiator will wait for other nodes to join. YOu can start them using the configuration files {{{settings_node1}}} and {{{settings_node2}}}. You may need to adjust the configurations files. Currently both node1 and node2 try to join the initiator on the local machine. This will only work if you start all instances on a local machine.
     42
     43The following configuration entries are of interest:
     44
     45 * {{{GENERAL_Initiator}}} - this tells the pingpong application whether to create or join a spovnet - sample value: {{{true}}} or {{{false}}}
     46 * {{{BASE_nodeid}}} - the nodeid that the node will have. If this entry is not present, the node will choose a random nodeid - sample value: {{{3}}}
     47 * {{{BASE_bootstrapIP}}} - that IP and port of the initiator so the node can start the join process -  sample value: {{{127.0.0.1:5002}}}
     48 * {{{BASE_port}}} - the local port the node should bind on. If this entry is not present, the node will bind on a default Ariba port -  sample value: {{{5010}}}
     49
     50Once the PingPong sample is running and the nodes have connected, the initiator will send ping messages to the joined nodes every 2 seconds. You can now e.g. test mobility of Ariba and change the IP address of a node, or swith from LAN connection to WLAN. The Links established by the PingPong sample through Ariba are mobility invariant and automatically repaired.
    3151
    3252== Prequisites ==
     
    7999}}}
    80100
    81 This will compile the Ariba library with simulation support and the PingPong sample with simulation support. Note, that the PingPong example will now be compiled as a shared library and reside in {{{build/lib}}}. Details on how to run the simulated PingPong sample are detailed in the next section.
     101This will compile the Ariba library with simulation support and the !PingPong sample with simulation support. Note, that the !PingPong example will now be compiled as a shared library and reside in {{{build/lib}}}. Details on how to run the simulated !PingPong sample are detailed in the next section.
    82102
    83 == Running the Simulated PingPong Sample ==
     103== Running the Simulated !PingPong Sample ==
     104
     105Compiling Ariba for simulations will result in {{{libariba}}} and {{{libpingpong}}} being placed into the {{{build/lib}}} folder. You can find exemplary simulation files in the {{{etc/simulation/omnet3}}} folder of the Ariba distribution.
     106
     107You have to adjust some path in the {{{omnetpp.ini}}} file. Fix the path in {{{preload-ned-files}}}. The load-libs path should be correct, in case you did not change the Ariba package.
     108
     109Next, start the {{{INET}}} binary in the {{{etc/simulation/omnet3}}}. This will start up the simulation that contains 3 router and 15 nodes that have Ariba nodes with the PingPong application on it.
    84110
    85111== Overview of special {{{configure}}} options ==