## 4 Test-Bed Implementation Setup
### Test-Bed Parameters  
Table 3 summarizes the earlier discussed and other parameters necessary to be set up for the reproduction of the results. An explanation of some of the parameters was discussed in previous sections.  
The experiment was conducted in a lab environment with consecutive labs in a corridor situated on the first floor in the Telecommunication Department of NED University of Engineering and Technology. The map of the experiment's location is presented in Figure 8. It is important to note that there are several configurations where different numbers of nodes were deployed. Therefore, Figure 8 contains a legend that shows the configurations of nodes and placement in a tabular manner. The nodes were placed such that a smaller number of nodes cover the entire area provided for this experiment. After covering the entire lab area of 4896 sq ft. with only eight nodes, an additional number of nodes were  
\begin{table}
\begin{tabular}{c l} \hline \hline
**S no.** & **Task** \\ \hline
1 & Disable _wpa_supplicant_ module from loading at boot \\
2 & Add _batman-adv_ module to the Linux kernel \\
3 & Turn off the wireless interface \\
4 & Set the required MTU for wireless interface \\
5 & Change the wireless interface mode to ad hoc \\
6 & Assign the essid to the wireless interface \\
7 & Allow wireless interface to join any open access point with same essid \\
8 & Set the wireless interface channel (same for every node) \\
9 & Choose the batman-adv routing algorithm \\
10 & Wait for the kernel module to change the routing algorithm \\
11 & Turn on the wireless interface \\
12 & Wait for the wireless interface to turn on \\
13 & Add the physical wireless interface to the virtual _batman-adv_ interface \\
14 & Turn on the virtual _batman-adv_ interface \\
15 & Assign static IP address to the virtual _batman-adv_ interface \\
16 & Set the appropriate transmit power for wireless interface \\ \hline \hline \end{tabular}
\end{table}
Table 2: Pseudocode for bash script executed on node boot.  
\begin{table}
\begin{tabular}{l l} \hline \hline
**Description** & **Value** \\ \hline Lab Size & \(24^{\prime}\times 56^{\prime},24^{\prime}\times 36^{\prime}\) \\ Total Area covered & \(1344+1344+1344+864=4896\) sq ft. (545.8533 sq meter) \\ Number of nodes & 2, 4, 6, 8, 10, 12, 14 \\ WLAN transmit power & 0, 10, 20, 30 (dBm) \\ K1, K2, K3, and K4 & 1 (all) \\ Tests conducted & Latency (delay), packet loss, throughput, Jitter, Packet Delivery Ratio \\ Number of ping tests per experiment & 100 \\ Number of throughput tests per experiment & 3 \\ Duration for throughput test & 10 s \\ Transport layer protocol used & TCP, UDP \\ WLAN band & 2.4 GHz \\ WLAN bandwidth & 20 MHz \\ WLAN channel & 9 (4252 MHz) \\ Debian Version & 10 (Buster) \\ Linux Kernel Version & 5.15.32-v7l+ \\ Batman-adv version & 2022.0-13-ge009 ae23-dirty \\ \hline \hline \end{tabular}
\end{table}
Table 3: BATMAN-adv experimental (test-bed) parameters.  
placed in between the nodes, which caused multiple paths between source and destination with a relatively good transmission quality metric.  
Since there is always clutter in the lab (compared to the experimental setup), e.g., computers, furniture, electrical components fittings, and other lab equipment and trainers, it is essential to attach images with this report to achieve a better idea of every lab part of the experiment. The following images, including Figure 9, were captured during the conduction of the experiment.