forked from wireshark/wireshark
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.capture
144 lines (108 loc) · 5.01 KB
/
README.capture
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
This document is an attempt, to bring some light to the things done, when
packet capturing is performed. There might be things missing, and others
maybe wrong :-( The following will concentrate a bit on the win32 gtk
port of wireshark.
XXX: when ongoing file reorganization will be completed, the following
two lists maybe won't be needed any longer!
libpcap related source files:
-----------------------------
capture-pcap-util.c
capture-pcap-util.h
capture-pcap-util-int.h
capture-pcap-util-unix.c
capture-wpcap.c
capture-wpcap.h
capture_wpcap_packet.c
capture_wpcap_packet.h
Capture related source files:
-----------------------------
capture.c
capture.h
capture_loop.c
capture_loop.h
capture_opts.c
capture-stop-conditions.c
capture-stop-conditions.h
capture_sync.c
capture_ui_utils.c
capture_ui_utils.h
conditions.c (XXX: is conditions generic or capture specific?)
conditions.h
Capture driver
--------------
Wireshark doesn't have direct access to the capture hardware. Instead of this,
it uses the Libpcap/Winpcap library to capture data from network cards.
On Win32, in capture-wpcap.c the function ws_module_open("wpcap.dll") is called
to load the wpcap.dll. This dll includes all functions needed for
packet capturing.
Capture File
------------
There are some kinds of targets to put the capture data into:
-temporary file
-user specified "single" capture file
-user specified "ringbuffer" capture file
Which kind of file is used depends on the user settings. In principle there
is no difference in handling these files, so if not otherwise notified,
it will be called the capture file.
The capture file is stored, using the wiretap library.
Overview
--------
Capturing is done using a two task model: the currently running (parent)
process will spawn a child process to do the real capture work, namely
controlling libpcap. This two task model is used because it's necessary
to split the capturing process (which should avoid packet drop) from the parent
process which might need significant time to display the data.
When a capture is started, the parent builds a "command line" and creates a
new child process with it. A pipe from the child to the parent is created
which is used to transfer control messages.
The child will init libpcap and send the parent a "new capture file is used"
control message through the pipe.
The child cyclically takes the packet data from libpcap and saves it to disk.
From time to time it will send the parent a "new packets" control message.
If the parent process receives this "new packets" message and the option
"Update list of packets in real time" is used, it will read the packet data
from the file, dissect and display it.
If the user wants to stop the capture, this can be done in two ways: by
menu/toolbar of the parent process or the Stop button of the child processes
dialog box (which obviously cannot be used it this dialog is hidden).
The Stop button will stop the capture itself, close the control pipe and then
closes itself. The parent will detect this and stop its part of the capture.
If the menu/toolbar is used, the parent will send a break signal to the child
which will lead to the same sequence as described above.
Win32 only: as the windows implementation of signals simply doesn't work,
another pipe from the parent to the child is used to send a "close capture"
message instead of a signal.
Start capture
-------------
A capture is started, by specifying to start the capture at the command line,
trigger the OK button in the "Capture Options" dialog box and some more. The
capture start is actually done by calling the capture_start() function in
capture.c.
Capture child (Loop)
--------------------
The capture child will open the target capture file, prepare pcap things,
init stop conditions, init the capture statistic dialog (if not hidden) and
start a loop which is running until the flag ld.go is FALSE.
Inside this loop,
-gtk main things are updated
-pcap_dispatch(capture_pcap_cb) is called
-the capture stop conditions are checked (ld.go is set to FALSE to finish)
-update the capture statistic dialog (if not hidden)
While this loop is running, the pcap_dispatch() will call capture_pcap_cb()
for every packet captured. Inside this, the packet data is converted into
wtap (wiretap) format and saved to file. Beside saving, it is trying to
do some basic dissecting (for the statistic window), by calling the
appropriate capture_xxx function.
When the user triggered a capture stop or one of the capture stop conditions
matched, the ld.go flag is set to FALSE, and the loop will stop shortly after.
Capture parent
--------------
In the capture parent the cap_pipe_input_cb() function is called "cyclically"
(unix:waiting for pipe, win32:timer,1000ms) to read data from the pipe and show
it on the main screen. While the capture is in progress, no other capture file
can be opened.
Updating
--------
The actual packet capturing inside the libpcap is done using its own task.
Catching and processing the packet data from the libpcap is done using the
pcap_dispatch() function.