diff options
Diffstat (limited to 'docbook/wsug_src/WSUG_chapter_build_install.xml')
| -rw-r--r-- | docbook/wsug_src/WSUG_chapter_build_install.xml | 874 |
1 files changed, 437 insertions, 437 deletions
diff --git a/docbook/wsug_src/WSUG_chapter_build_install.xml b/docbook/wsug_src/WSUG_chapter_build_install.xml index ac0250f6e6..0f17704830 100644 --- a/docbook/wsug_src/WSUG_chapter_build_install.xml +++ b/docbook/wsug_src/WSUG_chapter_build_install.xml @@ -9,16 +9,16 @@ As with all things, there must be a beginning, and so it is with Wireshark. To use Wireshark, you must: <itemizedlist> - <listitem> - <para> - Obtain a binary package for your operating system, or - </para> - </listitem> - <listitem> - <para> - Obtain the source and build Wireshark for your operating system. - </para> - </listitem> + <listitem> + <para> + Obtain a binary package for your operating system, or + </para> + </listitem> + <listitem> + <para> + Obtain the source and build Wireshark for your operating system. + </para> + </listitem> </itemizedlist> </para> <para> @@ -35,26 +35,26 @@ <para> The following are the general steps you would use: <orderedlist> - <listitem> - <para> - Download the relevant package for your needs, e.g. source or - binary distribution. - </para> - </listitem> - <listitem> - <para> - Build the source into a binary, if you have downloaded the - source. - </para> - <para> - This may involve building and/or installing other necessary packages. - </para> - </listitem> - <listitem> - <para> - Install the binaries into their final destinations. - </para> - </listitem> + <listitem> + <para> + Download the relevant package for your needs, e.g. source or + binary distribution. + </para> + </listitem> + <listitem> + <para> + Build the source into a binary, if you have downloaded the + source. + </para> + <para> + This may involve building and/or installing other necessary packages. + </para> + </listitem> + <listitem> + <para> + Install the binaries into their final destinations. + </para> + </listitem> </orderedlist> </para> </section> @@ -71,10 +71,10 @@ <note> <title>Download all required files!</title> <para> - In general, unless you have already downloaded Wireshark - before, you will most likely need to download several source - packages if you are building Wireshark from source. This is - covered in more detail below. <!-- Make a ref --> + In general, unless you have already downloaded Wireshark + before, you will most likely need to download several source + packages if you are building Wireshark from source. This is + covered in more detail below. <!-- Make a ref --> </para> </note> <para> @@ -84,15 +84,15 @@ <note> <title>Note!</title> <para> - While you will find a number of binary packages available on the - Wireshark web site, you might not find one for your platform, and - they often tend to be several versions behind the current released - version, as they are contributed by people who have the platforms - they are built for. + While you will find a number of binary packages available on the + Wireshark web site, you might not find one for your platform, and + they often tend to be several versions behind the current released + version, as they are contributed by people who have the platforms + they are built for. </para> <para> - For this reason, you might want to pull down the source distribution - and build it, as the process is relatively simple. + For this reason, you might want to pull down the source distribution + and build it, as the process is relatively simple. </para> </note> </section> @@ -103,22 +103,22 @@ Before you build Wireshark from sources, or install a binary package, you must ensure that you have the following other packages installed: <itemizedlist> - <listitem> - <para>GTK+, The GIMP Tool Kit.</para> - <para> - You will also need Glib. Both can be obtained from - <ulink url="http://www.gtk.org">www.gtk.org</ulink> - </para> - </listitem> - <listitem> - <para> - libpcap, the packet capture software that Wireshark uses. - </para> - <para> - You can obtain libpcap from - <ulink url="&TcpdumpWebsite;">www.tcpdump.org</ulink> - </para> - </listitem> + <listitem> + <para>GTK+, The GIMP Tool Kit.</para> + <para> + You will also need Glib. Both can be obtained from + <ulink url="http://www.gtk.org">www.gtk.org</ulink> + </para> + </listitem> + <listitem> + <para> + libpcap, the packet capture software that Wireshark uses. + </para> + <para> + You can obtain libpcap from + <ulink url="&TcpdumpWebsite;">www.tcpdump.org</ulink> + </para> + </listitem> </itemizedlist> Depending on your system, you may be able to install these from binaries, e.g. RPMs, or you may need to obtain them in source code @@ -127,9 +127,9 @@ <para> If you have downloaded the source for GTK+, the instructions shown in <xref linkend="Ch02Ex1"/> may provide some help in building it: - <example id="Ch02Ex1"> - <title>Building GTK+ from source</title> - <programlisting> + <example id="Ch02Ex1"> + <title>Building GTK+ from source</title> + <programlisting> gzip -dc gtk+-2.21.1.tar.gz | tar xvf - <much output removed> cd gtk+-2.21.1 @@ -139,36 +139,36 @@ make <much output removed> make install <much output removed> - </programlisting> - </example> - <note> - <title>Note!</title> - <para> - You may need to change the version number of GTK+ in - <xref linkend="Ch02Ex1"/> to match the version of GTK+ you have - downloaded. The directory you change to will change if the - version of GTK+ changes, and in all cases, - <command>tar xvf -</command> will show you the name of the - directory you should change to. - </para> - </note> - <note> - <title>Note!</title> - <para> - If you use Linux, or have GNU <command>tar</command> installed, - you can use <command>tar zxvf gtk+-2.21.1.tar.gz</command>. It - is also possible to use <command>gunzip -c</command> or - <command>gzcat</command> rather than <command>gzip -dc</command> - on many UNIX systems. - </para> - </note> - <note> - <title>Note!</title> - <para> - If you downloaded GTK+ or any other tar file using Windows, - you may find your file called gtk+-2_21_1_tar.gz. - </para> - </note> + </programlisting> + </example> + <note> + <title>Note!</title> + <para> + You may need to change the version number of GTK+ in + <xref linkend="Ch02Ex1"/> to match the version of GTK+ you have + downloaded. The directory you change to will change if the + version of GTK+ changes, and in all cases, + <command>tar xvf -</command> will show you the name of the + directory you should change to. + </para> + </note> + <note> + <title>Note!</title> + <para> + If you use Linux, or have GNU <command>tar</command> installed, + you can use <command>tar zxvf gtk+-2.21.1.tar.gz</command>. It + is also possible to use <command>gunzip -c</command> or + <command>gzcat</command> rather than <command>gzip -dc</command> + on many UNIX systems. + </para> + </note> + <note> + <title>Note!</title> + <para> + If you downloaded GTK+ or any other tar file using Windows, + you may find your file called gtk+-2_21_1_tar.gz. + </para> + </note> </para> <para> You should consult the GTK+ web site if any errors occur in carrying @@ -177,13 +177,13 @@ make install <para> If you have downloaded the source to libpcap, the general instructions shown in <xref linkend="Ch2Ex2"/> will assist in building it. Also, - if your operating system does not support <command>tcpdump</command>, - you might also want to download it from the - <ulink url="&TcpdumpWebsite;">tcpdump</ulink> web site and - install it. - <example id="Ch2Ex2"> - <title>Building and installing libpcap</title> - <programlisting> + if your operating system does not support <command>tcpdump</command>, + you might also want to download it from the + <ulink url="&TcpdumpWebsite;">tcpdump</ulink> web site and + install it. + <example id="Ch2Ex2"> + <title>Building and installing libpcap</title> + <programlisting> gzip -dc libpcap-1.0.0.tar.Z | tar xvf - <much output removed> cd libpcap-1.0.0 @@ -193,16 +193,16 @@ make <much output removed> make install <much output removed> - </programlisting> - </example> + </programlisting> + </example> </para> <note> <title>Note!</title> <para> - The directory you should change to will depend on the version of - libpcap you have downloaded. In all cases, - <command>tar xvf -</command> will show you the name of the - directory that has been unpacked. + The directory you should change to will depend on the version of + libpcap you have downloaded. In all cases, + <command>tar xvf -</command> will show you the name of the + directory that has been unpacked. </para> </note> <para> @@ -211,38 +211,38 @@ make install RPMs. Most Linux systems will install GTK+ and GLib in any case, however you will probably need to install the devel versions of each of these packages. The commands shown in <xref linkend="Ch02Ex4"/> - will install all the needed RPMs if they are not already installed. - <example id="Ch02Ex4"> - <title> - Installing required RPMs under Red Hat Linux 6.2 and beyond - </title> - <programlisting> + will install all the needed RPMs if they are not already installed. + <example id="Ch02Ex4"> + <title> + Installing required RPMs under Red Hat Linux 6.2 and beyond + </title> + <programlisting> cd /mnt/cdrom/RedHat/RPMS rpm -ivh glib-1.2.6-3.i386.rpm rpm -ivh glib-devel-1.2.6-3.i386.rpm rpm -ivh gtk+-1.2.6-7.i386.rpm rpm -ivh gtk+-devel-1.2.6-7.i386.rpm rpm -ivh libpcap-0.4-19.i386.rpm - </programlisting> - </example> + </programlisting> + </example> </para> <note> <para> - If you are using a version of Red Hat later than 6.2, the required - RPMs have most likely changed. Simply use the correct RPMs from your - distribution. + If you are using a version of Red Hat later than 6.2, the required + RPMs have most likely changed. Simply use the correct RPMs from your + distribution. </para> </note> <para> Under Debian you can install Wireshark using aptitude. aptitude will handle any dependency issues for you. <xref linkend="Ch02Ex5"/> shows - how to do this. - <example id="Ch02Ex5"> - <title>Installing debs under Debian, Ubuntu and other Debian derivatives</title> - <programlisting> + how to do this. + <example id="Ch02Ex5"> + <title>Installing debs under Debian, Ubuntu and other Debian derivatives</title> + <programlisting> aptitude install wireshark-dev - </programlisting> - </example> + </programlisting> + </example> </para> </section> @@ -252,78 +252,78 @@ aptitude install wireshark-dev Use the following general steps if you are building Wireshark from source under a UNIX operating system: <orderedlist> - <listitem> - <para> - Unpack the source from its <command>gzip</command>'d - <command>tar</command> file. If you are using Linux, or your - version of UNIX uses GNU <command>tar</command>, you can use the - following command: - <programlisting> + <listitem> + <para> + Unpack the source from its <command>gzip</command>'d + <command>tar</command> file. If you are using Linux, or your + version of UNIX uses GNU <command>tar</command>, you can use the + following command: + <programlisting> tar zxvf wireshark-&WiresharkCurrentVersion;-tar.gz - </programlisting> - </para> - <para> - For other versions of UNIX, you will want to use the following - commands: - <programlisting> + </programlisting> + </para> + <para> + For other versions of UNIX, you will want to use the following + commands: + <programlisting> gzip -d wireshark-&WiresharkCurrentVersion;-tar.gz tar xvf wireshark-&WiresharkCurrentVersion;-tar - </programlisting> - <note> - <title>Note!</title> - <para> - The pipeline - <command> - gzip -dc wireshark-&WiresharkCurrentVersion;-tar.gz | tar xvf - - </command> will work here as well. - </para> - </note> - <note> - <title>Note!</title> - <para> - If you have downloaded the Wireshark tarball under Windows, - you may find that your browser has created a file with - underscores rather than periods in its file name. - </para> - </note> - </para> - </listitem> - <listitem> - <para> - Change directory to the Wireshark source directory. - </para> - </listitem> - <listitem> - <para> - Configure your source so it will build correctly for your - version of UNIX. You can do this with the following command: - <programlisting> + </programlisting> + <note> + <title>Note!</title> + <para> + The pipeline + <command> + gzip -dc wireshark-&WiresharkCurrentVersion;-tar.gz | tar xvf - + </command> will work here as well. + </para> + </note> + <note> + <title>Note!</title> + <para> + If you have downloaded the Wireshark tarball under Windows, + you may find that your browser has created a file with + underscores rather than periods in its file name. + </para> + </note> + </para> + </listitem> + <listitem> + <para> + Change directory to the Wireshark source directory. + </para> + </listitem> + <listitem> + <para> + Configure your source so it will build correctly for your + version of UNIX. You can do this with the following command: + <programlisting> ./configure - </programlisting> - </para> - <para> - If this step fails, you will have to rectify the problems and - rerun <command>configure</command>. Troubleshooting hints are - provided in <xref linkend="ChBuildInstallUnixTrouble"/>. - </para> - </listitem> - <listitem> - <para> - Build the sources into a binary, with the <command>make</command> - command. For example: - <programlisting> + </programlisting> + </para> + <para> + If this step fails, you will have to rectify the problems and + rerun <command>configure</command>. Troubleshooting hints are + provided in <xref linkend="ChBuildInstallUnixTrouble"/>. + </para> + </listitem> + <listitem> + <para> + Build the sources into a binary, with the <command>make</command> + command. For example: + <programlisting> make - </programlisting> - </para> - </listitem> - <listitem> - <para> - Install the software in its final destination, using the command: - <programlisting> + </programlisting> + </para> + </listitem> + <listitem> + <para> + Install the software in its final destination, using the command: + <programlisting> make install - </programlisting> - </para> - </listitem> + </programlisting> + </para> + </listitem> </orderedlist> </para> <para> @@ -354,7 +354,7 @@ rpm -ivh wireshark-&WiresharkCurrentVersion;.i386.rpm If the above step fails because of missing dependencies, install the dependencies first, and then retry the step above. See <xref linkend="Ch02Ex4"/> for information on what RPMs you will need - to have installed. + to have installed. </para> </section> @@ -376,8 +376,8 @@ dpkg -i wireshark-common_&WiresharkCurrentVersion;.0-1_i386.deb wireshark_&Wires dpkg doesn't take care of all dependencies, but reports what's missing. </para> <note><title>Note!</title> - <para> - By installing Wireshark packages non-root users won't gain rights + <para> + By installing Wireshark packages non-root users won't gain rights automatically to capture packets. To allow non-root users to capture packets follow the procedure described in <ulink url="file:///usr/share/doc/wireshark-common/README.Debian">/usr/share/doc/wireshark-common/README.Debian</ulink> @@ -448,18 +448,18 @@ pkg_add -r wireshark <section id="ChBuildInstallWinBuild"> <title>Building from source under Windows</title> <para> - It is recommended to use the binary installer for Windows, - until you want to start developing Wireshark on the Windows platform. + It is recommended to use the binary installer for Windows, + until you want to start developing Wireshark on the Windows platform. </para> <para> - For further information how to build Wireshark for Windows from the - sources, have a look at the Developer's Guide on the - <ulink url="&WiresharkWebSite;/docs/">Documentation Page</ulink>. + For further information how to build Wireshark for Windows from the + sources, have a look at the Developer's Guide on the + <ulink url="&WiresharkWebSite;/docs/">Documentation Page</ulink>. </para> <para> - You may also want to have a look at the Development Wiki: - <ulink url="&WiresharkWikiPage;/Development">&WiresharkWikiPage;/Development</ulink> - for the latest available development documentation. + You may also want to have a look at the Development Wiki: + <ulink url="&WiresharkWikiPage;/Development">&WiresharkWikiPage;/Development</ulink> + for the latest available development documentation. </para> </section> @@ -468,311 +468,311 @@ pkg_add -r wireshark <para> In this section we explore installing Wireshark under Windows from the binary packages. - </para> + </para> <section id="ChBuildInstallWireshark"> <title>Install Wireshark</title> - <para> - You may acquire a binary installer of Wireshark named something like: - <filename>wireshark-winxx-&WiresharkCurrentVersion;.x.exe</filename>. - The Wireshark installer includes WinPcap, so you don't need to download - and install two separate packages. - </para> - <para> + <para> + You may acquire a binary installer of Wireshark named something like: + <filename>wireshark-winxx-&WiresharkCurrentVersion;.x.exe</filename>. + The Wireshark installer includes WinPcap, so you don't need to download + and install two separate packages. + </para> + <para> Simply download the Wireshark installer from: <ulink url="&WiresharkBinariesPage;">&WiresharkBinariesPage;</ulink> - and execute it. - Beside the usual installer options like where to install the program, - there are several optional components. + and execute it. + Beside the usual installer options like where to install the program, + there are several optional components. </para> <tip><title>Tip: Just keep the defaults!</title> - <para> - If you are unsure which settings to select, just keep the defaults. + <para> + If you are unsure which settings to select, just keep the defaults. </para> - </tip> + </tip> <section id="ChBuildInstallComponents"> <title>"Choose Components" page</title> <para> - <command>Wireshark</command> - <itemizedlist> - <listitem><para> - <command>Wireshark GTK</command> - Wireshark is a GUI network protocol - analyzer. - </para></listitem> - </itemizedlist> - </para> - <para> - <command>TShark</command> - TShark is a command-line based network - protocol analyzer. - </para> - <para> - <command>Plugins / Extensions</command> (for the Wireshark and TShark - dissection engines): - <itemizedlist> - <listitem><para> - <command>Dissector Plugins</command> - Plugins with some extended dissections. - </para></listitem> - <listitem><para> - <command>Tree Statistics Plugins</command> - Plugins with some extended statistics. - </para></listitem> - <listitem><para> - <command>Mate - Meta Analysis and Tracing Engine (experimental)</command> - - user configurable extension(s) of the display filter engine, see - <ulink url="&WiresharkWikiPage;/Mate">&WiresharkWikiPage;/Mate</ulink> - for details. - </para></listitem> - <listitem><para> - <command>SNMP MIBs</command> - SNMP MIBs for a more detailed SNMP - dissection. - </para></listitem> - </itemizedlist> - <command>Tools</command> (additional command line tools to work with - capture files): - <itemizedlist> - <listitem><para> - <command>Editcap</command> - Editcap is a program that reads a capture - file and writes some or all of the packets into another capture file. - </para></listitem> - <listitem><para> - <command>Text2Pcap</command> - Text2pcap is a program that reads in an - ASCII hex dump and writes the data into a libpcap-style capture file. - </para></listitem> - <listitem><para> - <command>Mergecap</command> - Mergecap is a program that combines multiple - saved capture files into a single output file. - </para></listitem> - <listitem><para> - <command>Capinfos</command> - Capinfos is a program that provides - information on capture files. - </para></listitem> - <listitem><para> - <command>Rawshark</command> - Rawshark is a raw packet filter. - </para></listitem> - </itemizedlist> - </para> - <para> - <command>User's Guide</command> - - Local installation of the User's Guide. The Help buttons on most dialogs - will require an internet connection to show help pages if the User's Guide - is not installed locally. - </para> + <command>Wireshark</command> + <itemizedlist> + <listitem><para> + <command>Wireshark GTK</command> - Wireshark is a GUI network protocol + analyzer. + </para></listitem> + </itemizedlist> + </para> + <para> + <command>TShark</command> - TShark is a command-line based network + protocol analyzer. + </para> + <para> + <command>Plugins / Extensions</command> (for the Wireshark and TShark + dissection engines): + <itemizedlist> + <listitem><para> + <command>Dissector Plugins</command> - Plugins with some extended dissections. + </para></listitem> + <listitem><para> + <command>Tree Statistics Plugins</command> - Plugins with some extended statistics. + </para></listitem> + <listitem><para> + <command>Mate - Meta Analysis and Tracing Engine (experimental)</command> + - user configurable extension(s) of the display filter engine, see + <ulink url="&WiresharkWikiPage;/Mate">&WiresharkWikiPage;/Mate</ulink> + for details. + </para></listitem> + <listitem><para> + <command>SNMP MIBs</command> - SNMP MIBs for a more detailed SNMP + dissection. + </para></listitem> + </itemizedlist> + <command>Tools</command> (additional command line tools to work with + capture files): + <itemizedlist> + <listitem><para> + <command>Editcap</command> - Editcap is a program that reads a capture + file and writes some or all of the packets into another capture file. + </para></listitem> + <listitem><para> + <command>Text2Pcap</command> - Text2pcap is a program that reads in an + ASCII hex dump and writes the data into a libpcap-style capture file. + </para></listitem> + <listitem><para> + <command>Mergecap</command> - Mergecap is a program that combines multiple + saved capture files into a single output file. + </para></listitem> + <listitem><para> + <command>Capinfos</command> - Capinfos is a program that provides + information on capture files. + </para></listitem> + <listitem><para> + <command>Rawshark</command> - Rawshark is a raw packet filter. + </para></listitem> + </itemizedlist> + </para> + <para> + <command>User's Guide</command> - + Local installation of the User's Guide. The Help buttons on most dialogs + will require an internet connection to show help pages if the User's Guide + is not installed locally. + </para> </section> <section id="ChBuildInstallAdditionalTasks"> <title>"Additional Tasks" page</title> <para> - <itemizedlist> - <listitem><para> - <command>Start Menu Shortcuts</command> - add some start menu shortcuts. - </para></listitem> - <listitem><para> - <command>Desktop Icon</command> - add a Wireshark icon to the desktop. - </para></listitem> - <listitem><para> - <command>Quick Launch Icon</command> - add a Wireshark icon to the - Explorer quick launch toolbar. - </para></listitem> - <listitem><para> - <command>Associate file extensions to Wireshark</command> - Associate - standard network trace files to Wireshark. - </para></listitem> - </itemizedlist> - </para> - </section> - <section id="ChBuildInstallWinPcap"> + <itemizedlist> + <listitem><para> + <command>Start Menu Shortcuts</command> - add some start menu shortcuts. + </para></listitem> + <listitem><para> + <command>Desktop Icon</command> - add a Wireshark icon to the desktop. + </para></listitem> + <listitem><para> + <command>Quick Launch Icon</command> - add a Wireshark icon to the + Explorer quick launch toolbar. + </para></listitem> + <listitem><para> + <command>Associate file extensions to Wireshark</command> - Associate + standard network trace files to Wireshark. + </para></listitem> + </itemizedlist> + </para> + </section> + <section id="ChBuildInstallWinPcap"> <title>"Install WinPcap?" page</title> <para> - The Wireshark installer contains the latest released WinPcap installer. - </para> - <para> - If you don't have WinPcap installed, you won't be able to capture live - network traffic, but you will still be able to open saved capture files. - </para> - <para> - <itemizedlist> - <listitem><para> - <command>Currently installed WinPcap version</command> - the Wireshark - installer detects the currently installed WinPcap version. - </para></listitem> - <listitem><para> - <command>Install WinPcap x.x</command> - if the currently installed - version is older than the one which comes with the Wireshark installer - (or WinPcap is not installed at all), this will be selected by default. - </para></listitem> - <listitem><para> - <command>Start WinPcap service "NPF" at startup</command> - so users - without administrative privileges can capture. - </para></listitem> - </itemizedlist> - - </para> - <para> - More WinPcap info: - <itemizedlist> - <listitem><para> - Wireshark related: - <ulink url="&WiresharkWikiPage;/WinPcap">&WiresharkWikiPage;/WinPcap</ulink> - </para></listitem> - <listitem><para> - General WinPcap info: - <ulink url="&WinPcapWebsite;">&WinPcapWebsite;</ulink> - </para></listitem> - </itemizedlist> - </para> - </section> - <section id="ChBuildInstallWiresharkCommandLine"> + The Wireshark installer contains the latest released WinPcap installer. + </para> + <para> + If you don't have WinPcap installed, you won't be able to capture live + network traffic, but you will still be able to open saved capture files. + </para> + <para> + <itemizedlist> + <listitem><para> + <command>Currently installed WinPcap version</command> - the Wireshark + installer detects the currently installed WinPcap version. + </para></listitem> + <listitem><para> + <command>Install WinPcap x.x</command> - if the currently installed + version is older than the one which comes with the Wireshark installer + (or WinPcap is not installed at all), this will be selected by default. + </para></listitem> + <listitem><para> + <command>Start WinPcap service "NPF" at startup</command> - so users + without administrative privileges can capture. + </para></listitem> + </itemizedlist> + + </para> + <para> + More WinPcap info: + <itemizedlist> + <listitem><para> + Wireshark related: + <ulink url="&WiresharkWikiPage;/WinPcap">&WiresharkWikiPage;/WinPcap</ulink> + </para></listitem> + <listitem><para> + General WinPcap info: + <ulink url="&WinPcapWebsite;">&WinPcapWebsite;</ulink> + </para></listitem> + </itemizedlist> + </para> + </section> + <section id="ChBuildInstallWiresharkCommandLine"> <title>Command line options</title> <para> - You can simply start the Wireshark installer without any command line - parameters, it will show you the usual interactive installer. - </para> - <para> - For special cases, there are some command line parameters available: - </para> - <itemizedlist> - <listitem> - <para> - <command>/NCRC</command> disables the CRC check - </para> - </listitem> - <listitem> - <para> - <command>/S</command> runs the installer or uninstaller silently with - default values. Please note: The silent installer won't install WinPCap! - </para> - </listitem> - <listitem> - <para> - <command>/desktopicon</command> installation of the desktop icon, - <command>=yes</command> - force installation, <command>=no</command> - - don't install, otherwise use defaults / user settings. - This option can be useful for a silent installer. - </para> - </listitem> - <listitem> - <para> - <command>/quicklaunchicon</command> installation of the quick launch icon, - <command>=yes</command> - force installation, <command>=no</command> - - don't install, otherwise use defaults / user settings. - </para> - </listitem> - <listitem> - <para> - <command>/D</command> sets the default installation directory - ($INSTDIR), overriding - InstallDir and InstallDirRegKey. It must be the last parameter used in - the command line and must not contain any quotes, even if the path - contains spaces. - </para> - </listitem> - </itemizedlist> - <para> Example: + You can simply start the Wireshark installer without any command line + parameters, it will show you the usual interactive installer. + </para> + <para> + For special cases, there are some command line parameters available: + </para> + <itemizedlist> + <listitem> + <para> + <command>/NCRC</command> disables the CRC check + </para> + </listitem> + <listitem> + <para> + <command>/S</command> runs the installer or uninstaller silently with + default values. Please note: The silent installer won't install WinPCap! + </para> + </listitem> + <listitem> + <para> + <command>/desktopicon</command> installation of the desktop icon, + <command>=yes</command> - force installation, <command>=no</command> - + don't install, otherwise use defaults / user settings. + This option can be useful for a silent installer. + </para> + </listitem> + <listitem> + <para> + <command>/quicklaunchicon</command> installation of the quick launch icon, + <command>=yes</command> - force installation, <command>=no</command> - + don't install, otherwise use defaults / user settings. + </para> + </listitem> + <listitem> + <para> + <command>/D</command> sets the default installation directory + ($INSTDIR), overriding + InstallDir and InstallDirRegKey. It must be the last parameter used in + the command line and must not contain any quotes, even if the path + contains spaces. + </para> + </listitem> + </itemizedlist> + <para> Example: <programlisting> wireshark-win32-&WiresharkCurrentVersion;.0.exe /NCRC /S /desktopicon=yes /quicklaunchicon=no /D=C:\Program Files\Foo - </programlisting> - </para> - </section> + </programlisting> + </para> + </section> </section> <section id="ChBuildInstallWinPcapManually"> <title>Manual WinPcap Installation</title> <note><title>Note!</title> - <para> - <command>As mentioned above, the Wireshark installer - takes care of the installation of WinPcap, - so usually you don't have to worry about WinPcap at all!</command> + <para> + <command>As mentioned above, the Wireshark installer + takes care of the installation of WinPcap, + so usually you don't have to worry about WinPcap at all!</command> </para> - </note> + </note> <para> - The following is only necessary if you want to - try a different version than the one included in the Wireshark installer, - e.g. because a new WinPcap (beta) version was released. + The following is only necessary if you want to + try a different version than the one included in the Wireshark installer, + e.g. because a new WinPcap (beta) version was released. </para> <para> - Additional WinPcap versions (including newer alpha or beta releases) - can be downloaded from the following locations: - <itemizedlist> - <listitem><para> + Additional WinPcap versions (including newer alpha or beta releases) + can be downloaded from the following locations: + <itemizedlist> + <listitem><para> The main WinPcap site: - <ulink url="&WinPcapWebsite;">&WinPcapWebsite;</ulink> - </para></listitem> - <listitem><para> + <ulink url="&WinPcapWebsite;">&WinPcapWebsite;</ulink> + </para></listitem> + <listitem><para> The Wiretapped.net mirror: - <ulink url="http://www.mirrors.wiretapped.net/security/packet-capture/winpcap"> - http://www.mirrors.wiretapped.net/security/packet-capture/winpcap</ulink> - </para></listitem> - </itemizedlist> + <ulink url="http://www.mirrors.wiretapped.net/security/packet-capture/winpcap"> + http://www.mirrors.wiretapped.net/security/packet-capture/winpcap</ulink> + </para></listitem> + </itemizedlist> </para> <para> - At the download page you will find a single installer exe called something - like "auto-installer", which can be installed under various Windows - systems, including NT4.0/2000/XP/2003/Vista/7/2008. - </para> + At the download page you will find a single installer exe called something + like "auto-installer", which can be installed under various Windows + systems, including NT4.0/2000/XP/2003/Vista/7/2008. + </para> </section> <section id="ChBuildInstallWinWiresharkUpdate"> <title>Update Wireshark</title> - <para> - From time to time you may want to update your installed Wireshark to a more - recent version. If you join Wireshark's announce mailing list, you will be - informed about new Wireshark versions, see <xref - linkend="ChIntroMailingLists"/> for details how to subscribe to this list. + <para> + From time to time you may want to update your installed Wireshark to a more + recent version. If you join Wireshark's announce mailing list, you will be + informed about new Wireshark versions, see <xref + linkend="ChIntroMailingLists"/> for details how to subscribe to this list. </para> <para> - New versions of Wireshark usually become available every 4 to 8 months. - Updating Wireshark is done the same way as installing it, you simply - download and start the installer exe. A reboot is usually not required and - all your personal settings remain unchanged. + New versions of Wireshark usually become available every 4 to 8 months. + Updating Wireshark is done the same way as installing it, you simply + download and start the installer exe. A reboot is usually not required and + all your personal settings remain unchanged. </para> </section> <section id="ChBuildInstallWinPcapUpdate"> <title>Update WinPcap</title> <para> - New versions of WinPcap are less frequently available, maybe only once in a - year. You will find WinPcap update instructions where you can download new - WinPcap versions. Usually you have to reboot the machine after installing - a new WinPcap version. - </para> - <warning><title>Warning!</title> - <para> - If you have an older version of WinPcap installed, you must uninstall it - before installing the current version. Recent versions of the WinPcap - installer will take care of this. - </para> - </warning> + New versions of WinPcap are less frequently available, maybe only once in a + year. You will find WinPcap update instructions where you can download new + WinPcap versions. Usually you have to reboot the machine after installing + a new WinPcap version. + </para> + <warning><title>Warning!</title> + <para> + If you have an older version of WinPcap installed, you must uninstall it + before installing the current version. Recent versions of the WinPcap + installer will take care of this. + </para> + </warning> </section> <section id="ChBuildInstallWinUninstall"> <title>Uninstall Wireshark</title> <para> - You can uninstall Wireshark the usual way, using the "Add or Remove - Programs" option inside the Control Panel. Select the "Wireshark" entry to - start the uninstallation procedure. + You can uninstall Wireshark the usual way, using the "Add or Remove + Programs" option inside the Control Panel. Select the "Wireshark" entry to + start the uninstallation procedure. </para> <para> - The Wireshark uninstaller will provide several options as to which things are to be - uninstalled; the default is to remove the core components but keep the personal - settings, WinPcap and alike. + The Wireshark uninstaller will provide several options as to which things are to be + uninstalled; the default is to remove the core components but keep the personal + settings, WinPcap and alike. </para> <para> - WinPcap won't be uninstalled by default, as other programs than Wireshark - may use it as well. + WinPcap won't be uninstalled by default, as other programs than Wireshark + may use it as well. </para> </section> <section id="ChBuildInstallWinPcapUninstall"> <title>Uninstall WinPcap</title> <para> - You can uninstall WinPcap independently of Wireshark, using the "WinPcap" - entry in the "Add or Remove Programs" of the Control Panel. + You can uninstall WinPcap independently of Wireshark, using the "WinPcap" + entry in the "Add or Remove Programs" of the Control Panel. </para> - <note><title>Note!</title> + <note><title>Note!</title> <para> - After uninstallation of WinPcap you can't capture anything with Wireshark. + After uninstallation of WinPcap you can't capture anything with Wireshark. </para> - </note> + </note> <para> - It might be a good idea to reboot Windows afterwards. + It might be a good idea to reboot Windows afterwards. </para> </section> </section> |