WEXTOOL User Guide v1.0

Download WEXTOOL User Guide v1.0

Post on 07-Jan-2016




0 download

Embed Size (px)


WEXTOOL User Guide v1.0. E.P. PLANETE B.B.R. Plan. Introduction & Architecture of Wextool Installation Scenario description Experimentation phase Saving/Synchronizing Traces Traces Analysis Results Storing. Introduction. - PowerPoint PPT Presentation


  • WEXTOOL User Guide v1.0


  • PlanIntroduction & Architecture of WextoolInstallation Scenario descriptionExperimentation phaseSaving/Synchronizing TracesTraces AnalysisResults Storing

  • IntroductionWextool is a toolkit that allows to manage a wireless experimentation using a single interface.

    Wextool v1.0 provides the following functions:Experimentation descriptionData captureData filteringData storing in DBData post filtering & analyzingGraphical generation

  • Architecture of WextoolIHMDB managerStoringPre-processingControlFilteringDisplayDescriptionExecution

  • InstallationFirst, make sure that:

    Clients/server stations have the following libs installed: glib2.0 or newer and libxml2.0 or newer. The server station has a php server (Apache or other) and a mysql server

  • InstallationClient side:It is responsible for executing the experimentation scenario on this node

    It is available as a rpm so, the installation can be done by your software manager.

    You should install the CREATE_DB (rpm) in your clients in order to allow distributed management of the DB.

  • InstallationServer side It is composed of three part: mysql file, a web site and the application CREATE_DB

    To install the server:Create a database scheduler in your DB serverCreate a database joomla in your DB serverCreate a database wextool in your DB serverUse your client mysql to execute the DB files.Deploy the web site in your php server (e.g. in www/wextool, this will correspond to your homepage)After deployment of the web site, you must configure two configuration files: configure.php in the root directory and configure.php in wextool/Create_Schedule

  • Installation (a snapshot)

  • Scenario descriptionTo describe the scenario corresponding to your experimentation, you need to define the following parameters using an XML format.

    Nodes (Stations involved in the experimentation)Acts (software that a node can execute )Actions (one Act and its environment parameters)Scenario (a group of Actions)Experimentation (a group of nodes and its scenario )

  • Scenario description: NodeNode: 1 # node identifier wlab13 # host name user # user name XXXXX # pwd 22 # port of connection station # station,AP,probe

  • Scenario description: ActionAction example: tshark 3 # action identifier 1 # node identifier tshark # application name -s # application options

  • Scenario description: ActAct example : tshark in node1 1 # act identifier 1 # number of nodes 1 # node identifier 3 # action identifier 10 # in seconds 36 # in seconds

  • Scenario description: ScenarioA Scenario :

    1 # scenario identifier 4 # number of acts 1 # act identifier 2 # act identifier 3 # act identifier 4 # act identifier

  • Scenario description: ExperimentExperiment

    1 5 # number of runs 6 # number of nodes 1 # node identifier 2 # node identifier 3 # node identifier 4 # node identifier 5 # node identifier 6 # node identifier 1 # scenario id.

  • How to generate XML scenarios? You can write your XML files using your favorite editor, based on xml samples provided. A tool will be available soon to automatically generate XML using a graphical interface. Later on, python script will be another option.

  • Wextool editor (available soon)

  • Experimentation phase

    The experimentation phase corresponds to the execution of your scenario

    Do not forget to include probes in your scenario. You can use the templates provided along with the sample scripts to configure your hardware and driver

  • Experimentation phase: a snapshot

  • Saving/synchronizing tracessimplexml allows to both synchronize and store traces in the database.Storing can be distributed, every probe can run simplexml in the same databaseSynchronization is automatic because simplexml ensures that the packet exists before possible insertion in the database.

    Parameters used:File name, e.g. /mnt/radio15/test_07070800.xml DB name, e.g. packet_03User name, e.g. rootUser password, e.g. xxxDB server, e.g. localhostAP MAC address, e.g. 0620a64effed

  • Saving/synchronizing tracesSaving & synchronizing trace can be an action in your experimentation: 4 4 simplexml /mnt/radio15/test_07070800.xml packet_03 root xxx localhost 0620a64effed

  • Manage Data Traces

    Data traces can be easily handled using two different tools:

    Phpmyadmin: the usual mysql admin

    Fabrik : a plugin that allows you to specify how you want to represent your data

  • Manage Data: Phpmyadmin

  • Manage Data: Fabrik

  • Graphical analysis: the GUI

  • Graphical analysis: a generated plot