timing issue with packet flow measurements fixed

master
Frederik Maaßen 2 years ago
parent 82b3172455
commit ce8f8ea620
  1. 4
      implementation/mininet_controller.py
  2. 2
      thesis/content/evaluation/minimal_network.tex

@ -144,7 +144,7 @@ def get_packet_counter_log_file_name(device, table, flag):
def read_packet_counter(delay, length, net, device, table, counter, flag, test_prefix, test_type, timestamp):
info(f"\nStarted packet counter thread for {device}")
executions = int(length / delay)
execution_counter = 1
execution_counter = 0
current_time = 0
running = True
initial_run = True
@ -176,7 +176,7 @@ def read_packet_counter(delay, length, net, device, table, counter, flag, test_p
current_time = round(current_time + delay, 1)
log_output = int(relevant_output) - last_value
last_value = int(relevant_output)
log_file_object.write(f"{current_time - 1} {str(log_output)}\n")
log_file_object.write(f"{current_time} {str(log_output)}\n")
if execution_counter >= executions:
running = False

@ -251,7 +251,7 @@ To show the amount of TCP packets being forwarded on each router, we measured th
\label{fig:evaluation_minimal_packet_flow_concurrent_wo_sc}
\end{figure}
The results in the network before a failure are as to be expected and can be seen in \cref{minimal_packet_flow_wo_sc_a}
The results in the network before a failure are as to be expected and can be seen in \cref{minimal_packet_flow_wo_sc_a}. Each router on the route from H1 to H4, which includes R1, R2 and R4, report the same amount of packets at each point of measurement.
\subsubsection{With FRR and ShortCut}
\label{minimal_packet_flow_with_frr_and_shortcut}