From d06d2fde9020603249f53ffaa1f9f43c182ec124 Mon Sep 17 00:00:00 2001 From: Jeff Morriss Date: Fri, 11 Oct 2013 19:55:34 +0000 Subject: Fix https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8943 : List Windows Server 2012 (and a couple of Home Server versions) as supported OS. While at it, remove the list of the various "NT-based" Windows versions from a couple of other places (this effectively removes statements that we still support NT4.0 and 2000). svn path=/trunk/; revision=52549 --- docbook/wsug_src/WSUG_chapter_advanced.xml | 3 +- docbook/wsug_src/WSUG_chapter_build_install.xml | 354 ++++++++++++------------ docbook/wsug_src/WSUG_chapter_introduction.xml | 3 +- 3 files changed, 180 insertions(+), 180 deletions(-) (limited to 'docbook/wsug_src') diff --git a/docbook/wsug_src/WSUG_chapter_advanced.xml b/docbook/wsug_src/WSUG_chapter_advanced.xml index 8cd1f32d83..3825e316b6 100644 --- a/docbook/wsug_src/WSUG_chapter_advanced.xml +++ b/docbook/wsug_src/WSUG_chapter_advanced.xml @@ -542,8 +542,7 @@ format), and some other capture file formats, such as the Windows Sniffer, EtherPeek, AiroPeek, and Sun snoop formats, save the arrival time of packets as UTC values. UN*X systems, - and "Windows NT based" systems (Windows NT 4.0, 2000, XP, - Server 2003, Vista, Server 2008, 7) represent + and "Windows NT based" systems represent time internally as UTC. When Wireshark is capturing, no conversion is necessary. However, if the system time zone is not set correctly, the system's UTC time might not be diff --git a/docbook/wsug_src/WSUG_chapter_build_install.xml b/docbook/wsug_src/WSUG_chapter_build_install.xml index 0f17704830..2b02392773 100644 --- a/docbook/wsug_src/WSUG_chapter_build_install.xml +++ b/docbook/wsug_src/WSUG_chapter_build_install.xml @@ -6,7 +6,7 @@
Introduction - As with all things, there must be a beginning, and so it is with + As with all things, there must be a beginning, and so it is with Wireshark. To use Wireshark, you must: @@ -23,13 +23,13 @@ Currently, several Linux distributions ship Wireshark, but - they are commonly shipping an out-of-date version. No other versions - of UNIX ship Wireshark so far, and Microsoft does not ship it with any - version of Windows. For that reason, you will need to know where to + they are commonly shipping an out-of-date version. No other versions + of UNIX ship Wireshark so far, and Microsoft does not ship it with any + version of Windows. For that reason, you will need to know where to get the latest version of Wireshark and how to install it. - This chapter shows you how to obtain source and binary packages, + This chapter shows you how to obtain source and binary packages, and how to build Wireshark from source, should you choose to do so. @@ -37,13 +37,13 @@ - Download the relevant package for your needs, e.g. source or + Download the relevant package for your needs, e.g. source or binary distribution. - Build the source into a binary, if you have downloaded the + Build the source into a binary, if you have downloaded the source. @@ -58,55 +58,55 @@
- +
Obtaining the source and binary distributions - You can obtain both source and binary distributions from the Wireshark - web site: &WiresharkWebSite;. - Simply select the download link, and then select either the source - package or binary package of your choice from the mirror site closest + You can obtain both source and binary distributions from the Wireshark + web site: &WiresharkWebSite;. + Simply select the download link, and then select either the source + package or binary package of your choice from the mirror site closest to you. Download all required files! - 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 + 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. - Once you have downloaded the relevant files, you can go on to the + Once you have downloaded the relevant files, you can go on to the next step. Note! - 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 + 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. - For this reason, you might want to pull down the source distribution + For this reason, you might want to pull down the source distribution and build it, as the process is relatively simple.
- +
Before you build <application>Wireshark</application> under UNIX - Before you build Wireshark from sources, or install a binary package, + Before you build Wireshark from sources, or install a binary package, you must ensure that you have the following other packages installed: GTK+, The GIMP Tool Kit. - You will also need Glib. Both can be obtained from + You will also need Glib. Both can be obtained from www.gtk.org @@ -115,17 +115,17 @@ libpcap, the packet capture software that Wireshark uses. - You can obtain libpcap from + You can obtain libpcap from www.tcpdump.org - 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 + 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 form and build them. - If you have downloaded the source for GTK+, the instructions shown + If you have downloaded the source for GTK+, the instructions shown in may provide some help in building it: Building GTK+ from source @@ -145,20 +145,20 @@ make install Note! You may need to change the version number of GTK+ in - 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, - tar xvf - will show you the name of the + 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, + tar xvf - will show you the name of the directory you should change to. Note! - If you use Linux, or have GNU tar installed, + If you use Linux, or have GNU tar installed, you can use tar zxvf gtk+-2.21.1.tar.gz. It - is also possible to use gunzip -c or - gzcat rather than gzip -dc + is also possible to use gunzip -c or + gzcat rather than gzip -dc on many UNIX systems. @@ -171,15 +171,15 @@ make install - You should consult the GTK+ web site if any errors occur in carrying + You should consult the GTK+ web site if any errors occur in carrying out the instructions in . - If you have downloaded the source to libpcap, the general instructions - shown in will assist in building it. Also, - if your operating system does not support tcpdump, - you might also want to download it from the - tcpdump web site and + If you have downloaded the source to libpcap, the general instructions + shown in will assist in building it. Also, + if your operating system does not support tcpdump, + you might also want to download it from the + tcpdump web site and install it. Building and installing libpcap @@ -199,18 +199,18 @@ make install Note! - The directory you should change to will depend on the version of - libpcap you have downloaded. In all cases, - tar xvf - will show you the name of the + The directory you should change to will depend on the version of + libpcap you have downloaded. In all cases, + tar xvf - will show you the name of the directory that has been unpacked. - Under Red Hat 6.x and beyond (and distributions based on it, like - Mandrake) you can simply install each of the packages you need from - 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 + Under Red Hat 6.x and beyond (and distributions based on it, like + Mandrake) you can simply install each of the packages you need from + 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 will install all the needed RPMs if they are not already installed. @@ -228,14 +228,14 @@ rpm -ivh libpcap-0.4-19.i386.rpm </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 + 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> + <para> Under Debian you can install Wireshark using aptitude. aptitude will - handle any dependency issues for you. <xref linkend="Ch02Ex5"/> shows + 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 @@ -245,25 +245,25 @@ aptitude install wireshark-dev
- +
Building Wireshark from source under UNIX - Use the following general steps if you are building Wireshark from + Use the following general steps if you are building Wireshark from source under a UNIX operating system: - Unpack the source from its gzip'd - tar file. If you are using Linux, or your - version of UNIX uses GNU tar, you can use the + Unpack the source from its gzip'd + tar file. If you are using Linux, or your + version of UNIX uses GNU tar, you can use the following command: tar zxvf wireshark-&WiresharkCurrentVersion;-tar.gz - For other versions of UNIX, you will want to use the following + For other versions of UNIX, you will want to use the following commands: gzip -d wireshark-&WiresharkCurrentVersion;-tar.gz @@ -272,7 +272,7 @@ tar xvf wireshark-&WiresharkCurrentVersion;-tar Note! - The pipeline + The pipeline gzip -dc wireshark-&WiresharkCurrentVersion;-tar.gz | tar xvf - will work here as well. @@ -281,8 +281,8 @@ tar xvf wireshark-&WiresharkCurrentVersion;-tar Note! - If you have downloaded the Wireshark tarball under Windows, - you may find that your browser has created a file with + 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. @@ -295,21 +295,21 @@ tar xvf wireshark-&WiresharkCurrentVersion;-tar - Configure your source so it will build correctly for your + Configure your source so it will build correctly for your version of UNIX. You can do this with the following command: ./configure - If this step fails, you will have to rectify the problems and - rerun configure. Troubleshooting hints are + If this step fails, you will have to rectify the problems and + rerun configure. Troubleshooting hints are provided in . - Build the sources into a binary, with the make + Build the sources into a binary, with the make command. For example: make @@ -327,38 +327,38 @@ make install - Once you have installed Wireshark with make install - above, you should be able to run it by entering + Once you have installed Wireshark with make install + above, you should be able to run it by entering wireshark.
- +
Installing the binaries under UNIX - In general, installing the binary under your version of UNIX will be - specific to the installation methods used with your version of UNIX. - For example, under AIX, you would use smit to - install the Wireshark binary package, while under Tru64 UNIX + In general, installing the binary under your version of UNIX will be + specific to the installation methods used with your version of UNIX. + For example, under AIX, you would use smit to + install the Wireshark binary package, while under Tru64 UNIX (formerly Digital UNIX) you would use setld. - +
Installing from rpm's under Red Hat and alike - Use the following command to install the Wireshark RPM that you have + Use the following command to install the Wireshark RPM that you have downloaded from the Wireshark web site: 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 - for information on what RPMs you will need + If the above step fails because of missing dependencies, install the + dependencies first, and then retry the step above. See + for information on what RPMs you will need to have installed.
-
+
Installing from deb's under Debian, Ubuntu and other Debian derivatives If you can just install from the repository then use: @@ -385,9 +385,9 @@ dpkg -i wireshark-common_&WiresharkCurrentVersion;.0-1_i386.deb wireshark_&Wires
-
+
Installing from portage under Gentoo Linux - + Use the following command to install Wireshark under Gentoo Linux with all of the extra features: @@ -396,9 +396,9 @@ USE="adns gtk ipv6 portaudio snmp ssl kerberos threads selinux" emerge wireshark
-
+
Installing from packages under FreeBSD - + Use the following command to install Wireshark under FreeBSD: pkg_add -r wireshark @@ -407,53 +407,53 @@ pkg_add -r wireshark
- +
Troubleshooting during the install on Unix - A number of errors can occur during the installation process. + A number of errors can occur during the installation process. Some hints on solving these are provided here. - If the configure stage fails, you will need to find - out why. You can check the file config.log in the - source directory to find out what failed. The last few lines of this + If the configure stage fails, you will need to find + out why. You can check the file config.log in the + source directory to find out what failed. The last few lines of this file should help in determining the problem. - The standard problems are that you do not have GTK+ on your system, - or you do not have a recent enough version of GTK+. The - configure will also fail if you do not have libpcap + The standard problems are that you do not have GTK+ on your system, + or you do not have a recent enough version of GTK+. The + configure will also fail if you do not have libpcap (at least the required include files) on your system. - Another common problem is for the final compile and link stage to - terminate with a complaint of: Output too long. - This is likely to be caused by an antiquated sed - (such as the one shipped with Solaris). Since sed is - used by the libtool script to construct the final - link command, this leads to mysterious problems. This can be - resolved by downloading a recent version of sed from + Another common problem is for the final compile and link stage to + terminate with a complaint of: Output too long. + This is likely to be caused by an antiquated sed + (such as the one shipped with Solaris). Since sed is + used by the libtool script to construct the final + link command, this leads to mysterious problems. This can be + resolved by downloading a recent version of sed from . - If you cannot determine what the problems are, send an email to the - wireshark-dev mailing list explaining your problem, - and including the output from config.log and - anything else you think is relevant, like a trace of the + If you cannot determine what the problems are, send an email to the + wireshark-dev mailing list explaining your problem, + and including the output from config.log and + anything else you think is relevant, like a trace of the make stage.
- +
Building from source under Windows - It is recommended to use the binary installer for Windows, + It is recommended to use the binary installer for Windows, until you want to start developing Wireshark on the Windows platform. - For further information how to build Wireshark for Windows from the - sources, have a look at the Developer's Guide on the + For further information how to build Wireshark for Windows from the + sources, have a look at the Developer's Guide on the Documentation Page. @@ -462,26 +462,26 @@ pkg_add -r wireshark for the latest available development documentation.
- +
Installing Wireshark under Windows - In this section we explore installing Wireshark under Windows from the - binary packages. + In this section we explore installing Wireshark under Windows from the + binary packages.
Install Wireshark - You may acquire a binary installer of Wireshark named something like: + You may acquire a binary installer of Wireshark named something like: wireshark-winxx-&WiresharkCurrentVersion;.x.exe. - The Wireshark installer includes WinPcap, so you don't need to download + The Wireshark installer includes WinPcap, so you don't need to download and install two separate packages. Simply download the Wireshark installer from: - &WiresharkBinariesPage; + &WiresharkBinariesPage; and execute it. - Beside the usual installer options like where to install the program, + Beside the usual installer options like where to install the program, there are several optional components. Tip: Just keep the defaults! @@ -495,17 +495,17 @@ pkg_add -r wireshark Wireshark - Wireshark GTK - Wireshark is a GUI network protocol + Wireshark GTK - Wireshark is a GUI network protocol analyzer. - TShark - TShark is a command-line based network + TShark - TShark is a command-line based network protocol analyzer. - Plugins / Extensions (for the Wireshark and TShark + Plugins / Extensions (for the Wireshark and TShark dissection engines): @@ -515,33 +515,33 @@ pkg_add -r wireshark Tree Statistics Plugins - Plugins with some extended statistics. - Mate - Meta Analysis and Tracing Engine (experimental) - - user configurable extension(s) of the display filter engine, see + Mate - Meta Analysis and Tracing Engine (experimental) + - user configurable extension(s) of the display filter engine, see &WiresharkWikiPage;/Mate for details. - SNMP MIBs - SNMP MIBs for a more detailed SNMP + SNMP MIBs - SNMP MIBs for a more detailed SNMP dissection. - Tools (additional command line tools to work with + Tools (additional command line tools to work with capture files): - Editcap - Editcap is a program that reads a capture + Editcap - Editcap is a program that reads a capture file and writes some or all of the packets into another capture file. - Text2Pcap - Text2pcap is a program that reads in an + Text2Pcap - Text2pcap is a program that reads in an ASCII hex dump and writes the data into a libpcap-style capture file. - Mergecap - Mergecap is a program that combines multiple + Mergecap - Mergecap is a program that combines multiple saved capture files into a single output file. - Capinfos - Capinfos is a program that provides + Capinfos - Capinfos is a program that provides information on capture files. @@ -551,8 +551,8 @@ pkg_add -r wireshark User's Guide - - 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 + 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.
@@ -567,11 +567,11 @@ pkg_add -r wireshark Desktop Icon - add a Wireshark icon to the desktop. - Quick Launch Icon - add a Wireshark icon to the + Quick Launch Icon - add a Wireshark icon to the Explorer quick launch toolbar. - Associate file extensions to Wireshark - Associate + Associate file extensions to Wireshark - Associate standard network trace files to Wireshark. @@ -583,26 +583,26 @@ pkg_add -r wireshark The Wireshark installer contains the latest released WinPcap installer. - If you don't have WinPcap installed, you won't be able to capture live + 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. - Currently installed WinPcap version - the Wireshark - installer detects the currently installed WinPcap version. + Currently installed WinPcap version - the Wireshark + installer detects the currently installed WinPcap version. - Install WinPcap x.x - if the currently installed - version is older than the one which comes with the Wireshark installer + Install WinPcap x.x - 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. - Start WinPcap service "NPF" at startup - so users + Start WinPcap service "NPF" at startup - so users without administrative privileges can capture. - + More WinPcap info: @@ -612,7 +612,7 @@ pkg_add -r wireshark &WiresharkWikiPage;/WinPcap - General WinPcap info: + General WinPcap info: &WinPcapWebsite; @@ -621,7 +621,7 @@ pkg_add -r wireshark
Command line options - You can simply start the Wireshark installer without any command line + You can simply start the Wireshark installer without any command line parameters, it will show you the usual interactive installer. @@ -635,31 +635,31 @@ pkg_add -r wireshark - /S runs the installer or uninstaller silently with + /S runs the installer or uninstaller silently with default values. Please note: The silent installer won't install WinPCap! - /desktopicon installation of the desktop icon, - =yes - force installation, =no - + /desktopicon installation of the desktop icon, + =yes - force installation, =no - don't install, otherwise use defaults / user settings. - This option can be useful for a silent installer. + This option can be useful for a silent installer. - /quicklaunchicon installation of the quick launch icon, - =yes - force installation, =no - + /quicklaunchicon installation of the quick launch icon, + =yes - force installation, =no - don't install, otherwise use defaults / user settings. - /D 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 + /D 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. @@ -670,21 +670,21 @@ wireshark-win32-&WiresharkCurrentVersion;.0.exe /NCRC /S /desktopicon=yes /quicklaunchicon=no /D=C:\Program Files\Foo -
+
- +
Manual WinPcap Installation Note! - 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! + 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! - The following is only necessary if you want to - try a different version than the one included in the Wireshark installer, + 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. @@ -692,7 +692,7 @@ wireshark-win32-&WiresharkCurrentVersion;.0.exe /NCRC /S /desktopicon=yes can be downloaded from the following locations: - The main WinPcap site: + The main WinPcap site: &WinPcapWebsite; @@ -703,67 +703,67 @@ wireshark-win32-&WiresharkCurrentVersion;.0.exe /NCRC /S /desktopicon=yes - 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. + At the download page you will find a single installer exe called something + like "auto-installer", which can be installed under various Windows + systems.
- +
Update Wireshark 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 for details how to subscribe to this list. New versions of Wireshark usually become available every 4 to 8 months. - Updating Wireshark is done the same way as installing it, you simply + 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.
- +
Update WinPcap - 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 + 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. Warning! - If you have an older version of WinPcap installed, you must uninstall it - before installing the current version. Recent versions of the WinPcap + 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.
- +
Uninstall Wireshark - You can uninstall Wireshark the usual way, using the "Add or Remove - Programs" option inside the Control Panel. Select the "Wireshark" entry to + 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. - 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 + 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. - WinPcap won't be uninstalled by default, as other programs than Wireshark + WinPcap won't be uninstalled by default, as other programs than Wireshark may use it as well.
- +
Uninstall WinPcap - You can uninstall WinPcap independently of Wireshark, using the "WinPcap" + You can uninstall WinPcap independently of Wireshark, using the "WinPcap" entry in the "Add or Remove Programs" of the Control Panel. Note! @@ -776,6 +776,6 @@ wireshark-win32-&WiresharkCurrentVersion;.0.exe /NCRC /S /desktopicon=yes
- + diff --git a/docbook/wsug_src/WSUG_chapter_introduction.xml b/docbook/wsug_src/WSUG_chapter_introduction.xml index f2f08e572d..0b2dfab39a 100644 --- a/docbook/wsug_src/WSUG_chapter_introduction.xml +++ b/docbook/wsug_src/WSUG_chapter_introduction.xml @@ -223,7 +223,8 @@ Windows XP Home, XP Pro, XP Tablet PC, XP Media - Center, Server 2003, Vista, 2008, 7, or 2008 R2 + Center, Server 2003, Vista, Home Server, Server 2008, Server 2008 R2, + Home Server 2011, 7, or Server 2012. Any modern 32-bit x86 or 64-bit AMD64/x86-64 processor. -- cgit v1.2.3