WEXTOOL User Guide v1.0
description
Transcript of WEXTOOL User Guide v1.0
WEXTOOL User Guide v1.0
E.P. PLANETEB.B.R.
Plan
Introduction & Architecture of Wextool Installation Scenario description Experimentation phase Saving/Synchronizing Traces Traces Analysis Results Storing
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
Architecture of Wextool
IHM
DB manager
Storing
Pre-processingControl
FilteringDisplay
Description
Execution
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
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.
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
Installation (a snapshot)
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 )
Scenario description: Node
Node: <Node> <id>1</id> # node identifier <host>wlab13</host> # host name <user>user</user> # user name <password>XXXXX</password> # pwd <port>22</port> # port of connection <role>station</role> # station,AP,probe </Node>
Scenario description: Action
Action example: tshark <Action> <id>3</id> # action identifier <nodeid>1</nodeid> # node identifier <application>tshark</application> # application name <param>-s</param> # application options </Action>
Scenario description: Act
Act example : tshark in node1 <Act> <id>1</id> # act identifier <nbnode>1</nbnode> # number of nodes <nodeid>1</nodeid> # node identifier <actionid>3</actionid> # action identifier <start_time>10</start_time> # in seconds <duration>36</duration> # in seconds </Act>
Scenario description: Scenario
A Scenario : <Scenario> <id>1</id> # scenario identifier <nbact>4</nbact> # number of acts <actid>1</actid> # act identifier <actid>2</actid> # act identifier <actid>3</actid> # act identifier <actid>4</actid> # act identifier </Scenario>
Scenario description: Experiment
Experiment <Experiment> <id>1</id> <runs>5</runs> # number of runs <nbnode>6</nbnode> # number of nodes <nodeid>1</nodeid> # node identifier <nodeid>2</nodeid> # node identifier <nodeid>3</nodeid> # node identifier <nodeid>4</nodeid> # node identifier <nodeid>5</nodeid> # node identifier <nodeid>6</nodeid> # node identifier <Scenarioid>1</Scenarioid> # scenario id. </Experiment>
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 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
Saving/synchronizing traces
Saving & synchronizing trace can be an action in your experimentation: <Action> <id>4</id> <nodeid>4</nodeid> <application>simplexml</application> <param>/mnt/radio15/test_07070800.xml
packet_03 root xxx localhost 0620a64effed</param>
</Action>
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