HTTPS is now needed to download the pkg-config source.

[metze/wireshark/wip.git] / README

diff --git a/README b/README
index c5a3962004a1654972538c234c50008648ceb2bc..6ef85151e051b3f2fe73aa2d3b51e3ace7293269 100644 (file)
--- a/README
+++ b/README
@@ -1,5 +1,3 @@
-$Id$
-
 General Information
 ------- -----------
 
@@ -34,7 +32,7 @@ Wireshark is known to compile and run on the following systems:
   - FreeBSD (2.2.5 and later)
   - NetBSD
   - OpenBSD
-  - Mac OS X (10.2 and later)
+  - OS X (10.2 and later)
   - HP-UX (10.20, 11.00, 11.11)
   - Sequent PTX v4.4.5  (Nick Williams <njw@sequent.com>)
   - Tru64 UNIX (formerly Digital UNIX) (3.2 and later)
@@ -52,27 +50,24 @@ Wireshark 0.99.4, and Windows 95, 98, and ME are supported by Ethereal 0.99.0.
 
 NOTE: the Makefile appears to depend on GNU "make"; it doesn't appear to
 work with the "make" that comes with Solaris 7 nor the BSD "make".
-Perl is also needed to create the man page.
+
+Both Perl and Python are needed, the former for building the man pages.
 
 If you decide to modify the yacc grammar or lex scanner, then
 you need "flex" - it cannot be built with vanilla "lex" -
 and either "bison" or the Berkeley "yacc". Your flex
 version must be 2.5.1 or greater. Check this with 'flex -V'.
 
-If you decide to modify the NetWare Core Protocol dissector, you
-will need python, as the data for packet types is stored in a python
-script, ncp2222.py.
-
-You must therefore install Perl, GNU "make", "flex", and either "bison" or
-Berkeley "yacc" on systems that lack them.
+You must therefore install Perl, Python, GNU "make", "flex", and either "bison"
+or Berkeley "yacc" on systems that lack them.
 
 Full installation instructions can be found in the INSTALL file.
-         
+
 See also the appropriate README.<OS> files for OS-specific installation
 instructions.
 
 Usage
------          
+-----
 
 In order to capture packets from the network, you need to make the
 dumpcap program set-UID to root, or you need to have access to the
@@ -95,38 +90,10 @@ The wiretap library is a packet-capture library currently under
 development parallel to wireshark.  In the future it is hoped that
 wiretap will have more features than libpcap, but wiretap is still in
 its infancy. However, wiretap is used in wireshark for its ability
-to read multiple file types. You can read the following file
-formats:
-
-libpcap (tcpdump -w, etc.) - this is Wireshark's native format
-snoop and atmsnoop
-Shomiti/Finisar Surveyor
-Novell LANalyzer
-Network General/Network Associates DOS-based Sniffer (compressed and
-    uncompressed)
-Microsoft Network Monitor
-AIX's iptrace
-Cinco Networks NetXray
-Network Associates Windows-based Sniffer
-AG Group/WildPackets EtherPeek/TokenPeek/AiroPeek/EtherHelp
-RADCOM's WAN/LAN Analyzer
-Lucent/Ascend access products
-HP-UX's nettl
-Toshiba's ISDN routers
-ISDN4BSD "i4btrace" utility
-Cisco Secure Intrusion Detection System iplogging facility
-pppd logs (pppdump-format files)
-VMS's TCPIPtrace utility
-DBS Etherwatch for VMS
-Traffic captures from Visual Networks' Visual UpTime
-CoSine L2 debug output
-Output from Accellent's 5Views LAN agents
-Endace Measurement Systems' ERF format
-Linux Bluez Bluetooth stack "hcidump -w" traces
-Network Instruments Observer version 9
-Trace files for the EyeSDN USB S0
-
-In addition, it can read gzipped versions of any of these files
+to read multiple file types.  See the Wireshark man page or the
+Wireshark User's Guide for a list of supported file formats.
+
+In addition, it can read gzipped versions of any of those files
 automatically, if you have the zlib library available when compiling
 Wireshark. Wireshark needs a modern version of zlib to be able to use
 zlib to read gzipped files; version 1.1.3 is known to work.  Versions
@@ -149,7 +116,7 @@ file if it's small and contains non-sensitive data.
 Support for Lucent/Ascend products is limited to the debug trace output
 generated by the MAX and Pipline series of products.  Wireshark can read
 the output of the "wandsession" "wandisplay", "wannext", and "wdd"
-commands. 
+commands.
 
 Wireshark can also read dump trace output from the Toshiba "Compact Router"
 line of ISDN routers (TR-600 and TR-650). You can telnet to the router
@@ -161,8 +128,8 @@ debug output, get in the diags mode first and then use
 layer-2 category. For more detail how to use these commands, you
 should examine the help command by "layer-2 create ?" or "layer-2 apply ?".
 
-To use the Lucent/Ascend, Toshiba and CoSine traces with Wireshark, you must 
-capture the trace output to a file on disk.  The trace is happening inside 
+To use the Lucent/Ascend, Toshiba and CoSine traces with Wireshark, you must
+capture the trace output to a file on disk.  The trace is happening inside
 the router and the router has no way of saving the trace to a file for you.
 An easy way of doing this under Unix is to run "telnet <ascend> | tee <outfile>".
 Or, if your system has the "script" command installed, you can save