Exit Zen
1
../../exercises/trace.rst:6
English
Analyzing packet traces
0/230 · 23
2
../../exercises/trace.rst:8
English
When debugging networking problems or to figure out performance problems, it is sometimes useful to capture the segments that are exchanged between two hosts and to analyze them.
0/1780 · 178
3
../../exercises/trace.rst:10
English
Several packet trace analysis tools are available, either as commercial or open-source tools. These tools are able to capture all the packets exchanged on a link. Of course, capturing packets require administrator privileges. They can also analyze the content of the captured packets and display information about them. The captured packets can be stored in a file for offline analysis.
0/3860 · 386
4
../../exercises/trace.rst:12
English
tcpdump_ is probably one of the most well known packet capture software. It is able to both capture packets and display their content. tcpdump_ is a text-based tool that can display the value of the most important fields of the captured packets. Additional information about tcpdump_ may be found in :manpage:`tcpdump(1)`.
0/3220 · 322
5
../../exercises/trace.rst:15
English
As an illustration, let us use tcpdump_ to analyze the packets exchanged while executing the following command on a Linux host:
0/1270 · 127
6
../../exercises/trace.rst:28
English
The ``-6`` parameter passed to curl_ forces the utilization of IPv6. curl_ returns an HTML page that indicates that https must be used instead of http to access this web site.
0/1750 · 175
7
../../exercises/trace.rst:35
English
A first solution to analyze this trace is to use tcpdump_ on the command line. The `-n` disables the reverse DNS lookups that tcpdump_ does by default for all IP addresses. The `-r` argument is the name of the file contained the captured packets. The trace starts with the DNS request. This request was sent over IPv4 which is the default on this host. tcpdump_ indicates the query and the response returned by the local DNS resolver.
0/4340 · 434
8
../../exercises/trace.rst:45
English
The following three lines of the tcpdump_ output correspond to TCP's three-way handshake. There are several interesting points to note in this output. First, ``Flags [S]`` indicates that the `SYN` flag was set in the first and second segments. In this first segment, tcpdump_ indicates the initial sequence number (``2681184541``). In the second segment, tcpdump_ indicates both the initial sequence number (``3804204915``) and the acknowledgment number (``2681184542``). Both segments contain TCP options. Starting in the third segment, tcpdump_ shows relative sequence numbers. Thus, the acknowledgment that you observe in the third segment is an acknowledgment for the `SYN` returned by the server.
0/7010 · 701
9
../../exercises/trace.rst:59
English
The two lines above correspond to the request sent by the client and the acknowledgment returned by the server. Note that the first byte sent by the client has `1` as relative sequence number. In this example, the HTTP request has a total length of 92 bytes. This request is immediately acknowledged by the server.
0/3140 · 314
10
../../exercises/trace.rst:62
English
The server then sends its response, which fits inside a single segment. The client acknowledges the reception of this segment.
0/1260 · 126
11
../../exercises/trace.rst:71
English
The TCP connection is then closed by exchanging three segments, the first two having the `FIN` flag set.
0/1040 · 104
12
../../exercises/trace.rst:79
English
tcpdump_ can provide more detailed information about the packets by using the `-v` or `-vv` option.
0/990 · 99
13
../../exercises/trace.rst:82
English
wireshark_ is more recent than tcpdump_. It evolved from the ethereal packet trace analysis software. It can be used as a text tool like tcpdump_. For a TCP connection, wireshark_ can provide almost the same output as tcpdump_. The main advantage of wireshark_ is that it also includes a graphical user interface that allows performing various types of analysis on a packet trace.
0/3800 · 380
14
../../exercises/trace.rst:88
English
Wireshark : default window
0/260 · 26
15
../../exercises/trace.rst:94
English
The wireshark_ window is divided in three parts. The top part of the window is a summary of the first packets from the trace. By clicking on one of the lines, you can show the detailed content of this packet in the middle part of the window. The middle of the window allows you to inspect all the fields of the captured packet. The bottom part of the window is the hexadecimal representation of the packet, with the field selected in the middle window being highlighted.
0/4700 · 470
16
../../exercises/trace.rst:96
English
wireshark_ is very good at displaying packets, but it also contains several analysis tools that can be very useful. The first tool is `Follow TCP stream`. It is part of the `Analyze` menu and allows you to reassemble and display all the payload exchanged during a TCP connection. This tool can be useful if you need to analyze for example the commands exchanged during an HTTP or SMTP session.
0/3930 · 393
17
../../exercises/trace.rst:98
English
The second tool is the flow graph that is part of the `Statistics` menu. It provides a time sequence diagram of the packets exchanged with some comments about the packet contents. See below for an example.
0/2050 · 205
18
../../exercises/trace.rst:104
English
Wireshark : flow graph
0/220 · 22
19
../../exercises/trace.rst:107
English
Use wireshark to analyze the packet traces described earlier :download:`traces/simple-trace.pcap`.
0/980 · 98
20
../../exercises/trace.rst:109
English
When analyzing packet traces with wireshark_, it is often very useful to use `Display filters` that only show the packets that match some specific criteria. There filters are described in several online documents:
0/2130 · 213