-
-For each test case (except for the \emph{manual tests}) a file containing previously
-captured network traffic will be replayed using Wireshark and sent to the \emph{Java TCP driven echo server}. We will use Bit-Twist
-to update the prepared packets with the MAC address of the guest network
-adapter and provide them with a valid source address. This updating step is needed because the kernel would otherwise reject the packets and prevent them from reaching the SUT. The response packets sent by the \emph{Java TCP driven echo server} and passing trough the SUT will be recorded,
-analyzed and validated according to the \textit{RFC793} specification.
-The valid packets are build manually from the \textit{RFC793} specification.
-Invalid packets are generated from this valid traffic using Bit-Twist.
-The boundary values for the different parameters (fields in packets) are determined by hand. Automated scripts are used in order to generate packets with some fields replaced with these
+% Ja maar we geven de host gewoon geen interface?
+
+For each test case (except for the \emph{manual tests}) a file containing
+previously captured network traffic will be replayed using Wireshark and sent
+to the \emph{Java TCP driven echo server}. We will use Bit-Twist to update the
+prepared packets with the MAC address of the guest network adapter and provide
+them with a valid source address. This updating step is needed because the
+kernel would otherwise reject the packets and prevent them from reaching the
+SUT. The response packets sent by the \emph{Java TCP driven echo server} and
+passing trough the SUT will be recorded, analyzed and validated according to
+the \textit{RFC793} specification. The valid packets are build manually from
+the \textit{RFC793} specification. Invalid packets are generated from this
+valid traffic using Bit-Twist. The boundary values for the different
+parameters (fields in packets) are determined by hand. Automated scripts are
+used in order to generate packets with some fields replaced with these