osmocom
/
wireshark
11
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Include dumpcap in the description. 

svn path=/trunk/; revision=35333
This commit is contained in:
Jaap Keuter 2011-01-03 07:40:21 +00:00
parent cff9f14959
commit 71136a917f
3 changed files with 29 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docbook/wsdg_graphics/ws-function-blocks.dia
View File

Binary file not shown.

BIN
docbook/wsdg_graphics/ws-function-blocks.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 7.9 KiB

After

Width:  |  Height:  |  Size: 28 KiB

44
docbook/wsdg_src/WSDG_chapter_works.xml
View File

@ -25,7 +25,7 @@
<para>
The function blocks in more detail:
<variablelist>
<varlistentry><term><command>GTK 1/2</command></term>
<varlistentry><term><command>GTK+ 2</command></term>
<listitem>
<para>
Handling of all user input/output (all windows, dialogs and such).
@ -44,9 +44,8 @@
<varlistentry><term><command>Epan</command></term>
<listitem>
<para>
Ethereal Packet ANalyzer (XXX - is this correct?) the packet
analyzing engine. Source code can be found in the
<filename>epan</filename> directory.
Ethereal Packet ANalyzer - the packet analyzing engine.
Source code can be found in the <filename>epan</filename> directory.
</para>
<itemizedlist>
<listitem>
@ -62,8 +61,8 @@
</listitem>
<listitem>
<para>
Plugins - Some of the protocol dissectors are implemented as plugins. Source
code can be found at <filename>plugins</filename>.
Dissector-Plugins - Some of the protocol dissectors are implemented
as plugins. Source code can be found in <filename>plugins</filename>.
</para>
</listitem>
<listitem>
@ -75,24 +74,33 @@
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry><term><command>Capture</command></term>
<listitem>
<para>
Capture engine.
</para>
</listitem>
</varlistentry>
<varlistentry><term><command>Wiretap</command></term>
<listitem>
<para>
The wiretap library is used to read/write capture files in libpcap
The wiretap library is used to read/write capture files in libpcap
and a lot of other file formats. Source code in the
<filename>wiretap</filename> directory.
</para>
</listitem>
</varlistentry>
<varlistentry><term><command>Capture</command></term>
<listitem>
<para>
The interface with the capture engine. Source code in the
root directory.
</para>
</listitem>
</varlistentry>
<varlistentry><term><command>Dumpcap</command></term>
<listitem>
<para>
The capture engine itself. This is the only part that is to execute
with elevated privileges. Source code in the root directory.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>Win-/libpcap (not part of the Wireshark package)</command></term>
<term><command>WinPcap / libpcap (not part of the Wireshark package)</command></term>
<listitem>
<para>
The platform dependent packet capture library, including the capture
@ -112,6 +120,12 @@
on your harddisk.
</para>
<para>
Since raw network adapter access requires elevated privileges these functions
are isolated into the dumpcap program. It's only this program that needs these
privileges, allowing the main part of the code (dissectors, user interface,
etc) to run as normal user program.
</para>
<para>
To hide all the lowlevel machine dependent details from
Wireshark, the libpcap/WinPcap (see <xref linkend="ChLibsPcap"/>) library
is used. This library provides a general purpose interface to capture