diff options
| author | Jeff Morriss <jeff.morriss.ws@gmail.com> | 2014-08-12 18:02:11 -0400 |
|---|---|---|
| committer | Evan Huus <eapache@gmail.com> | 2014-08-12 23:59:12 +0000 |
| commit | 61d522ffee30fb4cbade91b9f0311bf9001730ac (patch) | |
| tree | d3796060a4ccc6a3d5f11882e3e976e05566ffcb /README | |
| parent | 65ac652a07bf4c1cd0748e3f19c5215c9f1341bd (diff) | |
| download | wireshark-61d522ffee30fb4cbade91b9f0311bf9001730ac.tar.gz | |
Indicate that Python is required to compile Wireshark.
Remove some trailing white space at the same time.
(The ./configure options in INSTALL are significantly out of date--that will
be the subject of a separate commit.)
Change-Id: I3c03f90dab099e6d3386a235f35b691e7ff671be
Reviewed-on: https://code.wireshark.org/review/3563
Reviewed-by: Daniel Black <danielblack@fedoraproject.org>
Reviewed-by: Evan Huus <eapache@gmail.com>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 21 |
1 files changed, 9 insertions, 12 deletions
@@ -50,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 @@ -119,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 @@ -131,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 |