1. Python must be installed
http://python.org/
-2. omniidl from the the omniORB package must be available.
+2. omniidl from the omniORB package must be available.
http://omniorb.sourceforge.net/
3 Of course you need wireshark installed to compile the
system or interface on which you're capturing might silently limit the
capture buffer size to a lower value or raise it to a higher value.
-This is available on on UNIX systems with libpcap 1.0.0 or later and on
+This is available on UNIX systems with libpcap 1.0.0 or later and on
Windows. It is not available on UNIX systems with earlier versions of
libpcap.
system or interface on which you're capturing might silently limit the
capture buffer size to a lower value or raise it to a higher value.
-This is available on on UNIX systems with libpcap 1.0.0 or later and on
+This is available on UNIX systems with libpcap 1.0.0 or later and on
Windows. It is not available on UNIX systems with earlier versions of
libpcap.
system or interface on which you're capturing might silently limit the
capture buffer size to a lower value or raise it to a higher value.
-This is available on on UNIX systems with libpcap 1.0.0 or later and on
+This is available on UNIX systems with libpcap 1.0.0 or later and on
Windows. It is not available on UNIX systems with earlier versions of
libpcap.
<appendix id="AppGPL">
<!-- $Id$ -->
<title>This Document's License (GPL)</title>
- <para>As with the original licence and documentation distributed
+ <para>As with the original license and documentation distributed
with Wireshark, this document is covered by the GNU General Public
- Licence (GNU GPL).</para>
+ License (GNU GPL).</para>
<para>If you haven't read the GPL before, please do so. It
explains all the things that you are allowed to do with this
your Internet connection might use an HTTP proxy. Some Internet
providers use such a proxy and it is common in many company
networks today. Wireshark's setup script will try to discover
- your proxy settings automatically, but you you may need to set
+ your proxy settings automatically, but you may need to set
the environment variable HTTP_PROXY by hand before using wget.
For example, if you are behind proxy.com which is listening on
port 8080, you have to set it to something like:</para>
end
end
- -- using this function we register our fuction
+ -- using this function we register our function
-- to be called when the user selects the Tools->Test->Packets menu
register_menu("Test/Packets", menuable_tap, MENU_TOOLS)
end
substitution in the "location" value. For example, if
the database section contains
<programlisting>
-locatoin = http://www.example.com/proto?cookie=${cookie}&path=${PATH}
+location = http://www.example.com/proto?cookie=${cookie}&path=${PATH}
</programlisting>
then setting
<programlisting>
url_template=http://${language}.wikipedia.org/wiki/${PATH}
# Substitution data for the location template.
-# Each occurence of the keys below in the locaton template will be
+# Each occurence of the keys below in the location template will be
# substituted with their corresponding values. For example, "${license}"
# in the URL template above will be replaced with the value of "license"
# below.
<para>
Text2pcap also allows the user to read in dumps of application-level
data, by inserting dummy L2, L3 and L4 headers before each packet.
- Possiblities include inserting headers such as Ethernet, Ethernet + IP,
+ Possibilities include inserting headers such as Ethernet, Ethernet + IP,
Ethernet + IP + UDP, or Ethernet + Ip + TCP before each packet.
This allows Wireshark or any other full-packet decoder to handle these dumps.
</para>
</listitem>
<listitem>
<para>
- omniidl from the the omniORB package must be available. See
+ omniidl from the omniORB package must be available. See
<ulink url="http://omniorb.sourceforge.net/"/>
</para>
</listitem>
</section>
<section><title>Remote Capture Settings</title>
<para>
- The remote capture can be furhter fine tuned to match your situation.
+ The remote capture can be further fine tuned to match your situation.
The <command>Remote Settings</command> button gives you this option.
It pops up the dialog shown in
<xref linkend="ChCapInterfaceRemoteSettingsDialog"/>.
<listitem>
<para>
Win32 only: set capture buffer size (in MB, default is 1MB). This
- is used by the the capture driver to buffer packet data until that
+ is used by the capture driver to buffer packet data until that
data can be written to disk. If you encounter packet drops while
capturing, try to increase this size.
</para>
character dump). Any hex numbers in this text are also ignored. An offset of zero
is indicative of starting a new packet, so a single text file with a series of
hexdumps can be converted into a packet capture with multiple packets. Packets may
- be preseded by a timestamp. These are interpreted according to the format
+ be preceded by a timestamp. These are interpreted according to the format
given. If not the first packet is timestamped with the current time the import
takes place. Multiple packets are read in with timestamps differing by one
microsecond each. In general, short of these restrictions, Wireshark is pretty
<para>
Here you can select which type of frames you are importing. This all depends on
from what type of medium the dump to import was taken. It lists all types that
- Wirshark understands, so as to pass the capture file contents to the right dissector.
+ Wireshark understands, so as to pass the capture file contents to the right dissector.
</para>
</listitem>
</varlistentry>
<listitem>
<para>
<command>Endpoint distinction:</command> Use MAC addresses or IP
- time-to-live values to determine connection enpoints.
+ time-to-live values to determine connection endpoints.
</para>
</listitem>
<listitem>
git.samba.org / obnox / wireshark / wip.git / commitdiff