WEXTOOL User Guide v1.0

1
WEXTOOL User Guide v1.0
E.P. PLANETEB.B.R.
2
Plan

• Introduction Architecture of Wextool
• Installation
• Scenario description
• Experimentation phase
• Saving/Synchronizing Traces
• Traces Analysis
• Results Storing

3
Introduction

• Wextool is a toolkit that allows to manage a
  wireless experimentation using a single
  interface.
• Wextool v1.0 provides the following functions
• Experimentation description
• Data capture
• Data filtering
• Data storing in DB
• Data post filtering analyzing
• Graphical generation

4
Architecture of Wextool
Pre-processing
Control
Execution
IHM
Storing
Description
DB manager
Filtering
Display
5
Installation

• First, 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

6
Installation

• Client 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.

7
Installation

• Server 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 server
• Create a database joomla in your DB server
• Create a database wextool in your DB server
• Use 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

8
Installation (a snapshot)
9
Scenario description

• To 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 )

10
Scenario description Node

• Node
• ltNodegt
• ltidgt1lt/idgt node
  identifier
• lthostgtwlab13lt/hostgt host name
• ltusergtuserlt/usergt user name
• ltpasswordgtXXXXXlt/passwordgt pwd
• ltportgt22lt/portgt port of
  connection
• ltrolegtstationlt/rolegt
  station,AP,probe
• lt/Nodegt

11
Scenario description Action

• Action example tshark
• ltActiongt
• ltidgt3lt/idgt action
  identifier
• ltnodeidgt1lt/nodeidgt node identifier
• ltapplicationgttsharklt/applicationgt
• 
  application name
• ltparamgt-slt/paramgt application options
• lt/Actiongt

12
Scenario description Act

• Act example tshark in node1
• ltActgt
• ltidgt1lt/idgt act
  identifier
• ltnbnodegt1lt/nbnodegt number of nodes
• ltnodeidgt1lt/nodeidgt node identifier
• ltactionidgt3lt/actionidgt action
  identifier
• ltstart_timegt10lt/start_timegt in seconds
• ltdurationgt36lt/durationgt in
  seconds
• lt/Actgt

13
Scenario description Scenario

• A Scenario
• ltScenariogt
• ltidgt1lt/idgt scenario
  identifier
• ltnbactgt4lt/nbactgt number of acts
• ltactidgt1lt/actidgt act identifier
• ltactidgt2lt/actidgt act identifier
• ltactidgt3lt/actidgt act identifier
• ltactidgt4lt/actidgt act identifier
• lt/Scenariogt

14
Scenario description Experiment

• Experiment
• ltExperimentgt
• ltidgt1lt/idgt
• ltrunsgt5lt/runsgt number of
  runs
• ltnbnodegt6lt/nbnodegt number of nodes
• ltnodeidgt1lt/nodeidgt node identifier
• ltnodeidgt2lt/nodeidgt node identifier
• ltnodeidgt3lt/nodeidgt node identifier
• ltnodeidgt4lt/nodeidgt node identifier
• ltnodeidgt5lt/nodeidgt node identifier
• ltnodeidgt6lt/nodeidgt node identifier
• ltScenarioidgt1lt/Scenarioidgt scenario id.
• lt/Experimentgt

15
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.

16
Wextool editor (available soon)
17
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

18
Experimentation phase a snapshot
19
Saving/synchronizing traces

• simplexml allows to both synchronize and store
  traces in the database.
• Storing can be distributed, every probe can run
  simplexml in the same database
• Synchronization 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_03
• User name, e.g. root
• User password, e.g. xxx
• DB server, e.g. localhost
• AP MAC address, e.g. 0620a64effed

20
Saving/synchronizing traces

• Saving synchronizing trace can be an action in
  your experimentation
• ltActiongt
• ltidgt4lt/idgt
• ltnodeidgt4lt/nodeidgt
• ltapplicationgtsimplexmllt/applicationgt
• ltparamgt/mnt/radio15/test_07070800.xml
  packet_03 root xxx localhost 0620a64effedlt/paramgt
• lt/Actiongt

21
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

22
Manage Data Phpmyadmin
23
Manage Data Fabrik
24
Graphical analysis the GUI
25
Graphical analysis a generated plot