diff --git a/ansible/tasks/README.md b/ansible/tasks/README.md
index a5fd94c8cf67ee2aada5397e3a8625dc45ea015f..10f2a2d98309b75d6bfd7a228f473ebc9e77d813 100644
--- a/ansible/tasks/README.md
+++ b/ansible/tasks/README.md
@@ -1,8 +1,80 @@
+# **Sniffers' configuration**
+
+Ansible[^1] involves a common set of concepts and tools for system automation. An inventory to define the hosts and groups of hosts participants that will be operated by the playbooks. Once the inventory has been defined, a set of playbooks have been programmed to perform tasks on the sniffers. The execution of the playbooks depends on the modules available in the Ansible platform. Finally, the system global interpreter is based on Python. 
+
+[^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 2. 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>
+<figure>
+  <img src="https://gitlab.inria.fr/fmorlano/mitik_management/-/raw/main/Figures/mitik_topology.png" alt="mitik_topology"/>
+  <figcaption>Figure 2. Topology of Mitik project.</figcaption>
+</figure>
+</center>
+
+The Sniffers' configuration requires two configuration environments to be developed. A single configuration environment has been created to perform the installation and configuration tasks required on the hardware and the OS. A second environment executes the tasks necessary to start the sniffer according to the required parameters, in addition to synchronizing the data with the sniffer manager and the mitik server.
+
+## **Phase 1. Hardware and OS requirements**
+
+A modified version of Raspian has been provided [1], as part of the experiments evaluating the performance of low-level libraries to capture network traffic in the sniffer. However, it is necessary to carry out additional configurations in the sniffer to add new functionalities in it.
+
+## **Sniffer manager**
+
+A sniffer manager is defined in a Mitik laptop (Macbook Pro). All the instructions executed in the sniffers are defined in the sniffer manager. To establish communication with the sniffers, an inventory with specific parameters is defined.Each sniffer is assigned a static IP. Besides that, sniffers are organized in groups (super-sniffers). _inventory.yml_ shows the definition for each sniffer. Four groups (super-sniffers) are defined (ss1 to ss4), and each one contains five sniffers (sniffer#-ss#). 
+
+In addition to the inventory, the sniffer manager sends all the instructions and configurations contained in the playbooks to be executed in each sniffer. 
+
+### **Authentication**
+
+SSH key-based is used as authentication method between the sniffer manager and the sniffers. It is indispensable for the secure exchange information and data between the entities (sniffer manager and sniffers), besides of the execution of specific functions that requires SSH authentication. To enable the SSH Key-based authentication setup between the sniffer manager and the sniffers, _playbook_SSH_Keygen_ generates the public key of each sniffer, and also copy their SSH public keys to the sniffer manager.
+
+### **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.
+
+### **GPS Synchronization**
+
+Each step described in [README](https://gitlab.inria.fr/fmorlano/mitik_management/-/blob/main/docs/Installation%20manual.md) is executed in _playboork_GPS_sync_. 
+
+### **Wireless Interfaces**
+
+To avoid randomness in the network interface names, the **Predictable network interface names** is disabled, and new udev rules are defined for assigning static interface names for each USB port. 
+```
+#
+# +---------------+
+# | wlan1 | wlan3 |
+# +-------+-------+
+# | wlan2 | wlan4 |
+# +---------------+ (RPI USB ports distribution)
+#
+# | wlan0 | (onboard wifi)
+#
+ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="sdio", ATTR{address}=="<MAC address onboard antenna>", KERNELS=="brcmfmac", NAME="wlan0"
+ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb",  KERNELS=="1-1.3",       NAME="wlan1"
+ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb",  KERNELS=="1-1.4",       NAME="wlan2"
+ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb",  KERNELS=="1-1.1",       NAME="wlan3"
+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_.
+
+## **Phase 2. Sniffer parameters**
+
+# ------------------todo-------------------
+
 # ------------------ **TODO** --------------------
 
 Tasks:
 
 - [x] UPLOAD FUNCTIONAL PLAYBOOKS OF THE FIRST TESTBED
-- [ ] SPECIFY FEATURES OF EACH PLAYBOOK
+- [x] SPECIFY FEATURES OF EACH PLAYBOOK
 - [ ] ORGANIZE FEATURES IN PLAYBOOKS BY TASK TYPE
 - [ ] CREATE MAIN.YML TO EXECUTE ALL THE PLAYBOOKS