1 \subsection{Preflight checklist
}
2 Before actual certification is commenced we perform a manual test using a
4 If any of the checks fail we immediately reject the product.
5 The checklist is given in the table below. All commands in
\texttt{monospace
}
6 are to be run in a terminal. Commands prefixed with a
\texttt{\#
} should be run
7 with root permissions. Commands prefixed with a
\texttt{\$
} should be run with
10 \begin{longtable
}{|l|rp
{.8\linewidth}|
}
12 Check
1 &
\multicolumn{2}{l|
}{Get the SUT in a workable state.
}\\
14 \multirow{3}{*
}{Course of action
}
15 &
1. & Import the VirtualBox image into VirtualBox.\\
17 &
3. & Verify the SUT booted successfully and the network modules are
20 Passed &
\multicolumn{2}{l|
}{\textit{Yes/No
}}\\
22 Check
2 &
\multicolumn{2}{l|
}{Verify the SUT is complete.
}\\
24 \multirow{5}{*
}{Course of action
}
25 &
1. & Boot the SUT as in
\emph{Check
1}.\\
26 &
2. & Verify the loopback device exists by running
27 \texttt{\$ ifconfig
}.\\
28 &
3. & Verify the
\emph{echo-server
} is present on the system by running
29 \texttt{\$ file code/server/Main.java
}\\
30 &
4. & Verify
\emph{Scapy
} is present on the system by running
32 &
5. & Verify all scripts used for testing are present on the system.\\
34 Passed &
\multicolumn{2}{l|
}{\textit{Yes/No
}}\\
36 Check
3 &
\multicolumn{2}{l|
}{Initialize the testing environment..
}\\
38 \multirow{6}{*
}{Course of action
}
39 &
1. & Boot the SUT as in
\emph{Check
1}.\\
40 &
2. & Setup iptables by executing
41 \texttt{\# code/iptables.sh
}~
\footnote{The IPTables script ensures
42 that the OS does not drop packets due to an the unknown source.
}\\
43 &
3. & Navigate to the working directory by running
44 \texttt{\$ cd /home/student/tt2015
}\\
45 &
4. & Compile the echo server by running
46 \texttt{\# cd code/server \&\& make
}\\
47 &
5. & Start the echo server by running
48 \texttt{\# cd code/server \&\& java Main
}\\
49 &
6. & Generate all test cases by running
50 \texttt{\$ python code/client/gen.py
}\\
52 Passed &
\multicolumn{2}{l|
}{\textit{Yes/No
}}\\
54 Check
4 &
\multicolumn{2}{l|
}{Test the tool environment.
}\\
56 \multirow{3}{*
}{Course of action
}
57 &
1. & Initialize the SUT as in
\emph{Check
3}\\
58 &
2. & Execute the test script by running
59 \texttt{\# code/client/helloworld.py
}\\
60 &
3. & Verify the console displays a success message.\\
62 Passed &
\multicolumn{2}{l|
}{\textit{Yes/No
}}\\
64 Check
5 &
\multicolumn{2}{l|
}{All test inputs and scripts are present.
}\\
66 \multirow{2}{*
}{Course of action
}
67 &
1. & Boot the SUT as in
\emph{Check
1}.\\
68 &
2. & Verify that the test generation script is present by running
69 \texttt{\$ file code/client/test.py
}\\
71 Passed &
\multicolumn{2}{l|
}{\textit{Yes/No
}}\\
73 \caption{Preflight checklist
\label{tbl:preflight
}}
76 \subsection{Testing of SUT
}
77 The SUT is a series of services for other computer programs with no end-user
78 facing interface. Therefore the SUT will be tested solely by calling it's
79 services through various automated scripts. An automated test suite will be
80 available which executes all these automated scripts and aggregates their
81 results to asses whether or not the SUT has passed the test.
83 The implementation of the SUT is tested using black box testing techniques. A
84 series of tests asses the correctness of the implementation with regards to the
85 TCP specification. These tests are specified in Table~
\ref{tbl:testpairs
}. The test cases aim to cover the most interesting parts of the TCP
88 In this test suite the behavior of the outwards (network) interface of the SUT
89 is assessed. This is, the behavior of the SUT as
90 observed by another system on the network trying to communicate with (a system
91 running on the same host as the SUT using) the SUT. This is achieved by running
93 echo-server on the system which runs the SUT (a virtual machine) which
94 echos back all messages received to the sender. The test scripts will send
95 packets to the echo-server and then checks the received
96 response to asses whether or not the SUT is preforming as expected.
98 To cover the TCP specification as complete as possible while still maintaining
99 a feasible test suite the tests are divided into equivalence partitions. Below
100 these partitions are given.
103 \item \emph{Number of segments
} in request~
\footnote{A request is
104 considered establishing a connection (handshake) and a number of
107 \item 0 payload segments
108 \item 1 payload segments
109 \item n=small payload segments (
1 byte)
110 \item n=big payload segments (
65495 bytes)
112 \item \emph{source port
}
117 \item \emph{destination port
}
122 \item Bit errors in
\emph{payload
}
124 \item Correct payload
125 \item Payload with bit flips that do not show in checksum
126 \item Payload with bit flips that do show in checksum
128 \item \emph{checksum
}
133 \item \emph{Segment order
}
137 \item Missing Segments
141 These partitions were chosen since they correspond to key parts of the TCP
145 % één na laatste packket, moet dit B+3 of B+2 zijn?
148 TCP segments are send over a TCP connection from a
\emph{source
} to a
\emph{destination port
}. Therefore segments which are received that have a
149 source or destination port set to an incorrect value should not be regarded
150 as segments belonging to the connection by the SUT.
152 TCP uses a
\emph{checksum
} to catch any error introduced in headers, when this
153 checksum does not match the actual computed checksum the SUT should
154 disregard the received segment.
156 The TCP checksum is also an inherently weak one, as it is simply the
157 bitwise negation of the addition, in ones complement arithmetic,
158 of all
16 bit words in the header and data of the segment (excluding the
159 checksum itself). Therefore any
\emph{bit error
} where the ones complement value
161 increases by one, and the value of another decreases by one, is undetected.
162 The SUT should exhibit the same behavior and accept packets where these type
165 TCP guarantees that segments are delivered
\emph{in order
}
166 , even when they are received
167 out of order and that missing segments are resend. The SUT should
168 exhibit the same behavior. If segments are received out of order it should
169 either reassemble them when the missing packet has arrived or request them to
170 be resend when the Missing segments should be re-requested (by ACK-ing
171 the correct sequence number).
173 A single request consists of a number of packets that are sent
174 to the
\emph{echo-server
} and back. The TCP specification states that such a
175 transaction requires the following messages.
178 Script $-$ SYN $A$ $
\rightarrow$ SUT \\
179 Script $
\leftarrow$ SYN-ACK $(A+
1)$ $B$ $-$ SUT \\
180 Script $-$ ACK $(A+
1)$ $(B+
1)$ $
\rightarrow$ SUT \\
181 Script $-$ ACK-PUSH $(A+
1)$ $(B+
2)$
\emph{msg
} $
\rightarrow$ SUT \\
182 Script $
\leftarrow$ ACK $(A+
2+msg_
{length
})$ $(B+
3)$ $-$ SUT \\
183 Script $
\leftarrow$ ACK-PUSH $(A+
2+msg_
{length
})$ $(B+
3)$
\emph{msg
} $-$ SUT
190 When the
\emph{SUT
} has received the ACK containing the message it's passed
191 trough to the
\emph{echo-server
}. The
\emph{echo-server
} will proceed by ordering
192 the
\emph{SUT
} to respond by sending the exact same message. When this happens
193 the
\emph{SUT
} has to construct the last packet in the transaction listed above.
197 Partitions
2 to
6 are tested using pairwise testing to keep the number of test
198 cases feasible. The pairs are then all *except some where it does not make sense
199 to do so) tested with the different request sizes of partition
1.
201 This is expressed in Table~
\ref{tbl:testpairs
}. In this table the first five
202 columns represent the different options for the partitions
2 to
6 of the above
203 enumeration. The last four columns are the different number segments as
204 described in the partition
1 of the above enumeration. These cells identify
205 individual test cases by a number. An
\xmark in the cell indicates that this
206 test case can not be created as it is not possible with that number of segments
207 (eg. sending segments out of order when the number of segments is
1).
212 \begin{tabular
}{|l|l|l|l|l|l||l|l|l|l|
}
214 &
\multicolumn{9}{c|
}{\textbf{Partition
}}\\
216 &
4 &
5 &
3 &
6 &
2 &
1a &
1b &
1c &
1d\\
218 \multirow{9}{*
}{Instance
}
219 & a & a & a & a & a &
\doTCC &
\doTCC &
\doTCC &
\doTCC\\
220 & a & b & b & c & b &
\xmark &
\xmark &
\doTCC &
\doTCC\\
221 & c & a & b & a & b &
\xmark &
\xmark &
\doTCC &
\doTCC\\
222 & c & b & a & c & a &
\xmark &
\xmark &
\doTCC &
\doTCC\\
223 & b & a & b & c & a &
\xmark &
\xmark &
\xmark &
\doTCC\\
224 & b & b & a & b & b &
\xmark &
\xmark &
\xmark &
\doTCC\\
225 & c & b & b & a & b &
\xmark &
\doTCC &
\doTCC &
\doTCC\\
226 & b & b & b & a & b &
\xmark &
\xmark &
\xmark &
\doTCC\\
227 & a & b & b & b & a &
\xmark &
\xmark &
\doTCC &
\doTCC\\
230 \caption{Combinations of test cases
}
231 \label{tbl:testpairs
}
234 \subsection{Quality, completeness and coverage of tests
}
236 The network packets used in testing are constructed from prerecorded, known to
237 be correct, network traffic. These packets are then modified with well used and
238 field tested tools. Due to this the chance of errors in the test cases is quite
239 low. However, no formal proof of correctness of the test cases is present, this
240 means that any defects found might not be the result of a fault in the SUT.
241 Therefore detected defects should only indicate there is a high chance that
242 there is a fault in the SUT and can not result directly in the conclusion that
243 there actually is one.
247 Due to the nature of black-box testing coverage of the code in the
248 implementation of the SUT is unknown. However completeness of the tests over
249 the specification of the SUT can be assessed.
253 Due to the clear and exhaustive specification of TCP the completeness of the
254 test suite can be clearly assessed.
256 As always, $
100\%$ completeness is not feasible, therefore test cases are
257 carefully selected to cover the most interesting parts of the TCP specification
258 to ensure a complete but feasible test suite.
260 To further increase the coverage of the test suites tests are randomized. The
261 tests which test the handling of
\emph{bit errors
}, changes in the
\emph{packet
262 order
} and
\emph{dropped packets
} randomize where they introduce an error. The
263 test suite runs these tests multiple times to increase the likelihood that they
264 discover a fault which is only present when an error occurs in a certain
267 To further decrease the number of tests needed test cases are divided into
268 equivalence partitions and the combination of cases as described in
269 Table~
\ref{tbl:testpairs
} ensures that all partitions are
270 covered and the number of individual tests is still feasible.
274 % wat ik ook probeer ik krijg de eerste collum
275 % zijn tekst niet verticaal gecentered
279 \subsection{Test suite
}
281 Before executing the test suite the test environment has to be initialized.
284 \item Boot the vm using VirtualBox.
285 \item Setup iptables by executing
\texttt{\# code/iptables.sh
}
286 \item Navigate to the working directory by running
287 \texttt{\$ cd /home/student/tt2015
}
288 \item Start the echo server by running
289 \texttt{\# cd code/server \&\& Java Main
}
292 \subsubsection{Preflight checks
}
293 The we do the preflight checks as defined in Table~
\ref{tbl:preflight
}.
295 \subsubsection{Test Cases
}
296 If the SUT passes the preflight checks the actual test cases can be executed.
297 Table~
\ref{tbl:testcases
} shows the expected results of each of the test cases
298 described in Table~
\ref{tbl:testpairs
}.
303 \begin{tabular
}{|l|p
{.7\linewidth}|
}
305 Test number & Expected results\\
307 \doTCC & An ACK\# of the sequence number of the SYN packet +
1. \\
\hline
308 \doTCC & An ACK\# of the send sequence number +
1.\\
\hline
309 \doTCC & An ACK\# of the sequence number of the last send segment + the
310 size of the payload of that segment.\\
\hline
311 \doTCC & An ACK\# of the sequence number of the last send segment + the
312 size of the payload of that segment.\\
\hline
313 \doTCC & An ACK\# of the sequence number of the last send segment + the
314 size of the payload of that segment.\\
\hline
315 \doTCC & An ACK\# of the sequence number of the swapped packet with the lowest sequence number. \\
\hline
316 \doTCC & The ACK\# for the SEQ\# of the first segments which is
317 corrupted is received for each consecutive segment send.\\
320 \doTCC & The ACK\# for the SEQ\# of the first segments which is
321 corrupted is received for each consecutive segment send.\\
\hline
322 \doTCC & An ACK\# of the sequence number of the last send segment + the
323 size of the payload of that segment.\\
\hline
324 % \doTCC & The segment is not attributed to the current connection
325 % and therefore no ACK\# is received. \\ \hline
326 % \doTCC & The ACK\# for the SEQ\# of the first segments which is
327 % corrupted is received for each consecutive segment send.\\ \hline
328 % \doTCC & The ACK\# for the SEQ\# of the first segments which is
329 % corrupted is received for each consecutive segment send.\\ \hline
330 % \doTCC & The segment is not attributed to the current connection
331 % and therefore no ACK\# is received. \\ \hline
332 % \doTCC & The ACK\# for the SEQ\# of the first segments which is
333 % corrupted is received for each consecutive segment send.\\ \hline
334 % \doTCC & The ACK\# for the SEQ\# of the first segments which is
335 % corrupted is received for each consecutive segment send.\\ \hline
336 % \doTCC & The ACK\# for the SEQ\# of the first segments which is
337 % corrupted is received for each consecutive segment send.\\ \hline
338 % \doTCC & The ACK\# for the SEQ\# of the first segments which is
339 % corrupted is received for each consecutive segment send.\\ \hline
341 \caption{Expected results of test cases
}
342 \label{tbl:testcases
}
345 % Bij Ramons afwezigheid
346 % Paul Vitero (linkerkant lange gang)
347 % verdieping Mercator
350 \begin{longtable
}{|p
{.2\linewidth}|p
{.8\linewidth}|
}
354 Title & Connect to the
\emph{echo-server
} without sending a payload. \\
\hline
355 Input & Generated packets. \\
\hline
356 Expected output &
\emph{Echo-server
} accepts the connection. \\
\hline
357 \multirow{2}{*
}{Course of action
}
358 &
1. Use the steps listed above in order to start the SUT. \\
359 &
2. Execute the script by running
\texttt{\# code/client/tests/
1.py
} \\
\hline
360 Valid trace & Verify that the script prints 'Success'. \\
\hline
364 Title & Single valid request with
1byte payload. \\
\hline
365 Input & Generated packets. \\
\hline
366 Expected output & Packets echoed back by Echo-Server. \\
\hline
367 \multirow{2}{*
}{Course of action
}
368 &
1. Use the steps listed above in order to start the SUT. \\
369 &
2. Execute the script by running
\texttt{\# code/client/tests/
1.py
} \\
\hline
370 Valid trace & Verify that the script prints 'Success'. \\
\hline
374 % Title & Single valid request with 65495bytes payload. \\\hline
375 % Input & Generated packets. \\\hline
376 % Expected output & Packets echoed back by Echo-Server. \\\hline
377 % \multirow{2}{*}{Course of action}
378 % & 1. Use the steps listed above in order to start the SUT. \\
379 % & 2. Execute the script by running \texttt{\# code/client/tests/2.py} \\\hline
380 % Valid trace & Verify that the script prints 'Success'. \\\hline
384 Title &
5 valid requests with
1byte payload. \\
\hline
385 Input & Generated packets. \\
\hline
386 Expected output & Packets echoed back by Echo-Server, in the same order as the client sent them. \\
\hline
387 \multirow{2}{*
}{Course of action
}
388 &
1. Use the steps listed above in order to start the SUT. \\
389 &
2. Execute the script by running
\texttt{\# code/client/tests/
3.py
} \\
\hline
390 Valid trace & Verify that the script prints 'Success'. \\
\hline
394 Title &
5 valid requests with
65495bytes payload. \\
\hline
395 Input & Generated packets with
65495bytes payload. \\
\hline
396 Expected output & Packets echoed back by Echo-Server, in the same order as the client sent them. \\
\hline
397 \multirow{2}{*
}{Course of action
}
398 &
1. Use the steps listed above in order to start the SUT. \\
399 &
2. Execute the script by running
\texttt{\# code/client/tests/
4.py
} \\
\hline
400 Valid trace & Verify that the script prints 'Success'. \\
\hline
404 Title &
5 requests with
1byte payload with corrupted source port, destination port and checksum. The second segment is omitted in order to simulate a packet drop on the client side. \\
\hline
405 Input & Generated packets with
1byte payload, two packets are swapped in position. \\
\hline
406 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
407 \multirow{2}{*
}{Course of action
}
408 &
1. Use the steps listed above in order to start the SUT. \\
409 &
2. Execute the script by running
\texttt{\# code/client/tests/
5.py
} \\
\hline
410 Valid trace & Verify that the script prints 'Success'. \\
\hline
414 Title &
5 requests with
65495byte payload with corrupted source port, destination port and checksum. The second segment is omitted in order to simulate a packet drop on the client side. \\
\hline
415 Input & Generated packets with
65495byte payload, second generated packet is removed. \\
\hline
416 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
417 \multirow{2}{*
}{Course of action
}
418 &
1. Use the steps listed above in order to start the SUT. \\
419 &
2. Execute the script by running
\texttt{\# code/client/tests/
6.py
} \\
\hline
420 Valid trace & Verify that the script prints 'Success'. \\
\hline
426 Title &
5 requests with
1byte corrupted payload, corrupted source and destination port. \\
\hline
427 Input & Generated packets with
1byte payload, in these packets the payload byte, source and destination ports are increased by one. \\
\hline
428 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
429 \multirow{2}{*
}{Course of action
}
430 &
1. Use the steps listed above in order to start the SUT. \\
431 &
2. Execute the script by running
\texttt{\# code/client/tests/
7.py
} \\
\hline
432 Valid trace & Verify that the script prints 'Success'. \\
\hline
436 Title &
5 requests with
65495byte corrupted payload, corrupted source and destination port. \\
\hline
437 Input & Generated packets with
65495byte payload, in these packets one of the payload bytes, source and destination ports are increased by one. \\
\hline
438 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
439 \multirow{2}{*
}{Course of action
}
440 &
1. Use the steps listed above in order to start the SUT. \\
441 &
2. Execute the script by running
\texttt{\# code/client/tests/
8.py
} \\
\hline
442 Valid trace & Verify that the script prints 'Success'. \\
\hline
447 Title &
5 requests with
1byte corrupted payload, invalid checksum and the second packet is dropped. \\
\hline
448 Input & Generated packets with
1byte payload, in these packets the payload byte and checksum are increased by one. \\
\hline
449 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
450 \multirow{2}{*
}{Course of action
}
451 &
1. Use the steps listed above in order to start the SUT. \\
452 &
2. Execute the script by running
\texttt{\# code/client/tests/
9.py
} \\
\hline
453 Valid trace & Verify that the script prints 'Success'. \\
\hline
457 Title &
5 requests with
65495byte corrupted payload, invalid checksum and the second packet is dropped. \\
\hline
458 Input & Generated packets with
65495byte payload, in these packets one of the payload bytes and the checksum are increased by one. \\
\hline
459 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
460 \multirow{2}{*
}{Course of action
}
461 &
1. Use the steps listed above in order to start the SUT. \\
462 &
2. Execute the script by running
\texttt{\# code/client/tests/
10.py
} \\
\hline
463 Valid trace & Verify that the script prints 'Success'. \\
\hline
467 Title &
5 requests with
65495byte corrupted payload that doesn't show up in checksum and corrupted destination port. The second packet is dropped. \\
\hline
468 Input & Generated packets with
65495byte payload, in these packets one
16bit word in the payload is increased by
1 and another
16bit word is decreased by
1. The destination port is also increase by one and the second packet is removed. \\
\hline
469 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
470 \multirow{2}{*
}{Course of action
}
471 &
1. Use the steps listed above in order to start the SUT. \\
472 &
2. Execute the script by running
\texttt{\# code/client/tests/
11.py
} \\
\hline
473 Valid trace & Verify that the script prints 'Success'. \\
\hline
478 Title &
5 requests with
65495byte corrupted payload that doesn't show up in checksum and corrupted source port and checksum. The
2nd and
3rd packets are swapped. \\
\hline
479 Input & Generated packets with
65495byte payload, in these packets one
16bit word in the payload, the source port and checksum are increased by one. A different
16bit word in the payload is decreased by one. The
2nd and
3rd packets are swapped in order to simulate a out-of-order transmission. \\
\hline
480 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
481 \multirow{2}{*
}{Course of action
}
482 &
1. Use the steps listed above in order to start the SUT. \\
483 &
2. Execute the script by running
\texttt{\# code/client/tests/
12.py
} \\
\hline
484 Valid trace & Verify that the script prints 'Success'. \\
\hline
489 Title & Single request with
1byte corrupted payload and corrupted source port, destination port and checksum. \\
\hline
490 Input & Generated packet with
1byte payload, in this packet one byte in the payload, the source port and checksum are increased by one. \\
\hline
491 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
492 \multirow{2}{*
}{Course of action
}
493 &
1. Use the steps listed above in order to start the SUT. \\
494 &
2. Execute the script by running
\texttt{\# code/client/tests/
13.py
} \\
\hline
495 Valid trace & Verify that the script prints 'Success'. \\
\hline
499 Title &
5 requests with
1byte corrupted payload and corrupted source port, destination port and checksum. \\
\hline
500 Input & Generated packets with
1byte payload, in these packet one byte in the payload, the source port and checksum are increased by one. \\
\hline
501 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
502 \multirow{2}{*
}{Course of action
}
503 &
1. Use the steps listed above in order to start the SUT. \\
504 &
2. Execute the script by running
\texttt{\# code/client/tests/
14.py
} \\
\hline
505 Valid trace & Verify that the script prints 'Success'. \\
\hline
509 Title &
5 requests with
65495byte corrupted payload and corrupted source port, destination port and checksum. \\
\hline
510 Input & Generated packets with
65495byte payload, in these packets one byte in the payload, the source port and checksum are increased by one. \\
\hline
511 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
512 \multirow{2}{*
}{Course of action
}
513 &
1. Use the steps listed above in order to start the SUT. \\
514 &
2. Execute the script by running
\texttt{\# code/client/tests/
15.py
} \\
\hline
515 Valid trace & Verify that the script prints 'Success'. \\
\hline
519 Title &
5 requests with
65495byte corrupted payload that doesn't show up in the checksum, corrupted source port, destination port and checksum. \\
\hline
520 Input & Generated packets with
65495byte payload, in these packets one
16bit word in the payload, the source port and checksum are increased by one. Another
16bit word in the payload is decreased by
1. \\
\hline
521 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
522 \multirow{2}{*
}{Course of action
}
523 &
1. Use the steps listed above in order to start the SUT. \\
524 &
2. Execute the script by running
\texttt{\# code/client/tests/
16.py
} \\
\hline
525 Valid trace & Verify that the script prints 'Success'. \\
\hline
530 Title &
5 requests with
1byte payload, corrupted destination port and checksum. The
2nd and
3rd packets are swapped \\
\hline
531 Input & Generated packets with
1byte payload, in these packets the destination port and checksum are increased by one. The
2nd and
3rd packets are swapped in order to simulate an out-of-order transmission. \\
\hline
532 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
533 \multirow{2}{*
}{Course of action
}
534 &
1. Use the steps listed above in order to start the SUT. \\
535 &
2. Execute the script by running
\texttt{\# code/client/tests/
17.py
} \\
\hline
536 Valid trace & Verify that the script prints 'Success'. \\
\hline
541 Title &
5 requests with
65495byte payload, corrupted destination port and checksum. The
2nd and
3rd packets are swapped \\
\hline
542 Input & Generated packets with
65495byte payload, in these packets the destination port and checksum are increased by one. The
2nd and
3rd packets are swapped in order to simulate an out-of-order transmission. \\
\hline
543 Expected output & All packets are dropped resulting in a connection time-out. \\
\hline
544 \multirow{2}{*
}{Course of action
}
545 &
1. Use the steps listed above in order to start the SUT. \\
546 &
2. Execute the script by running
\texttt{\# code/client/tests/
18.py
} \\
\hline
547 Valid trace & Verify that the script prints 'Success'. \\
\hline
551 %\begin{tabularx}{\linewidth}{| l | X|}
554 %Title & Single valid request. \\\hline
555 %Input & Pcap file with prerecorded valid packets. \\\hline
556 %Expected output & Pcap file with valid response to request. \\\hline
557 %Course of action & \begin{enumerate}
558 % \item Execute \emph{./scripts/tests/case1-single-valid.sh}
559 % \item Load \emph{output/case1.pcap} with ...
560 %\end{enumerate} \\\hline
561 %Valid trace & \begin{enumerate}
562 % \item \textbf{Hier packets benoemen?}
563 %\end{enumerate} \\\hline
566 %\begin{tabularx}{\linewidth}{| l | X|}
569 %Title & Single request with corrupted checksum. \\\hline
570 % Input & Pcap file used as \emph{test-case 1} input. \\\hline
571 % Expected output & No response from SUT, logs with rejected packets. \\\hline
572 % Course of action & \begin{enumerate}
573 % \item Load input pcap file into ....
574 % \item Corrupt checksum of loaded packets.
575 % \item Save resulting packets as pcap file.
576 % \item Load new pcap file into ...
577 % \item Replay new pcap file.
578 % \item Record SUT response using...
579 % \item Extract log with rejected packets.
580 % \item Save recorded packets as a pcap file.
581 % \item Analyze packets in resulting file.
582 % \end{enumerate} \\\hline
583 % Valid trace & \begin{enumerate}
584 % \item \textbf{Aangeven welke packets corrupted zijn?}
585 % \end{enumerate} \\\hline