Changes between Initial Version and Version 1 of Old/ARuba


Ignore:
Timestamp:
Dec 13, 2005, 6:16:58 AM (19 years ago)
Author:
Surya Satyavolu
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Old/ARuba

    v1 v1  
     1= Using Aruba sniffers =
     2
     3== Purpose ==
     4The ORBIT grid has four Aruba sniffers at the four corners that can be configured to sniff specific channels and report '''every''' sniffed packet to the database.
     5This gives the experimenters an independent framework to correlate 802.11 traffic during the course of the experiment for sanity checking as well as verifying the expected outcome of the experiment.
     6
     7== Nomenclature ==
     8The sniffers have been assigned the following IP addresses
     9
     10|| Sniffer || IP || Position ||
     11|| aruba1-1 || 10.2.1.1 || Near node1-20 ||
     12|| aruba1-4 || 10.2.1.4 || Near node1-4 ||
     13|| aruba4-1 || 10.2.4.1 || Near node20-20 ||
     14|| aruba4-4 || 10.2.4.4 || Near node20-1 ||
     15
     16== Usage ==
     17Sniffers are already up and running. '''Currently they work only on b/g channels'''. Sniffers can be set to listen to a specific channel by using the following command
     18from internal4 or idb1
     19
     20{{{
     21telnet 10.2.1.4
     22#> echo "Channel: 11" >> /proc/net/wifi0/Config
     23}}}
     24
     25== Backend data collection ==
     26
     27In order to start collecting frames in the database, you need to be on '''internal4.orbit-lab.org'''
     28
     29 * Download the following file to your local directory and call it config.xml
     30  {{{
     31    <project id="monitor">
     32      <measurements>
     33        <db id="monitor" host="10.10.0.50" user="orbit" password="orbit"/>
     34        <multicast-channel addr="224.10.10.1" port="7000" iface="eth1"/>
     35      </measurements>
     36    </project>
     37  }}}
     38
     39 * Launch the following application from local directory
     40  {{{
     41   monitor -c config.xml -n internal4 -i eth2
     42  }}}
     43
     44The sniffed packets are reported to the database named ''monitor'' under the table ''frames''
     45
     46 == Capture Schema ==
     47
     48|| Field             || Type         ||
     49
     50|| id                || mediumint(9) ||
     51|| monitor_id        || varchar(32)  ||
     52|| channel           || int(11)      ||
     53|| flag              || int(11)      ||
     54|| rate              || int(11)      ||
     55|| snr               || int(11)      ||
     56|| type              || int(11)      ||
     57|| sub_type          || int(11)      ||
     58|| duration          || varchar(32)  ||
     59|| dst_addr          || varchar(32)  ||
     60|| src_addr          || varchar(32)  ||
     61|| receiver_addr     || varchar(32)  ||
     62|| frag_num          || int(11)      ||
     63|| seq_num           || int(32)      ||
     64|| timestamp         || varchar(32)  ||
     65|| frame_description || varchar(32)  ||
     66|| beacon_timestamp  || varchar(32)  ||
     67|| ssid              || varchar(32)  ||
     68