From 5112e3f5f69fcc0acac9b90ebb8aa7de4b35dafb Mon Sep 17 00:00:00 2001
From: MOLANO ORTIZ Fernando <fernando.molano-ortiz@inria.fr>
Date: Mon, 30 Jan 2023 23:05:20 +0000
Subject: [PATCH] Update README.md

---
 ansible/tasks/README.md | 29 +++++++++++++++++++----------
 1 file changed, 19 insertions(+), 10 deletions(-)

diff --git a/ansible/tasks/README.md b/ansible/tasks/README.md
index f96aa26..d38102a 100644
--- a/ansible/tasks/README.md
+++ b/ansible/tasks/README.md
@@ -4,13 +4,6 @@ Ansible[^1] involves a common set of concepts and tools for system automation. A
 
 [^1]: https://www.ansible.com/
 
-#<center>
-#<figure>
-#  <img src="https://gitlab.inria.fr/fmorlano/mitik_management/-/raw/main/Figures/ansible.png" alt="ansible_architecture"/>
-#  <figcaption>Figure 1. Ansible architecture.</figcaption>
-#</figure>
-#</center>
-
 The proposed topology is shown in Figure 1. One goal of using Ansible-based automation is to configure all sniffers simultaneously to guarantee that all nodes receive the same configuration, in addition to facilitating the manipulation of each device to be configured.
 
 <center>
@@ -45,7 +38,7 @@ SSH key-based is used as authentication method between the sniffer manager and t
 
 ### **Sniffer Identification**
 
-Since each sniffer uses the OS from [1], _playbook_hostname_ and _playbook_hosts_ to redefine the hostname and local DNS of each sniffer based on the _inventory_ file and the static IP defined there.
+Since each sniffer uses the O.S. from [1], _playbook_hostname_ and _playbook_hosts_ to redefine the hostname and local DNS of each sniffer based on the _inventory_ file and the static IP defined there.
 
 ### **GPS Synchronization**
 
@@ -71,11 +64,27 @@ ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb",  KERNELS=="1-1.1",       NAM
 ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb",  KERNELS=="1-1.2",       NAME="wlan4"
 ```
 
-It is also defined a wireless network to connect each sniffer to the remote server through wlan0. These parameters are defined in _playbook_NIC_config_.
+It is also defined a wireless network to connect each sniffer to the remote server through wlan0. These parameters are defined in _playbook_NIC_config_. It is worth noting that all wireless interfaces used to sniff must be connected in the same USB port for all sniffers.
 
 ## **Role 2. Sniffer parameters**
 
-# ------------------todo-------------------
+Unlike the single execution tasks of role 1, the tasks of role 2 can be executed multiple times, as long as they correspond to execution variables of the sniffer script. It is necessary to enter the online parameters to run the sniffer described in [1]. Host variables are defined in _playbook_scapy-sniffer_. Also, a timeout to stop sniffer execution has been added. By last, a job scheduling utility has been added to ensure that network time protocol set by Chrony is up to date for all sniffers. 
+
+To start the sniffers, following parameters must be defined:
+
+- Hour to start the experiment,
+- Minutes to start the experiment,
+- Runtime duration in seconds,
+- Wireless interface (by default, wlan1),
+- Packet capture filter (by default, probe-req, probe-resp, beacon),
+- Channel (by default, system),
+- Hash funtion (by default, MD5),
+- Hash pattern (by default, 15),
+- Folder destination.
+
+The capture filename structure produced by sniffers will have the next format: packet_capture_{sniffer_i-super-sniffer_id}-ts-{timestamp}-ch{channel}-gps{lat/lon}.pcap
+
+On the other hand, each single capture file from the sniffers is sent via SSH connection to the Mitik laptop or Mitik server to be analyzed in the **Trace handling engine** and the **Trace production engine**. The _playbook_data_transfer_ contains the instructions to send the data to the Mitik laptop or Mitik server. 
 
 # ------------------ **TODO** --------------------
 
-- 
GitLab