target/linux/etrax-2.6/image/e100boot/src/libpcap-0.4/INSTALL

   1 @(#) $Header: /usr/local/cvs/linux/tools/build/e100boot/libpcap-0.4/INSTALL,v 1.1 1999/08/26 10:05:18 johana Exp $ (LBL)
   2
   3 To build libpcap, first customize any paths in Makefile.in, then run
   4 "./configure" (a shell script). The configure script will determine
   5 your system attributes and generate an appropriate Makefile from
   6 Makefile.in. Next run "make". If everything goes well you can su to
   7 root and run "make install", "make install-incl" and "make
   8 install-man". However, you need not install libpcap if you just want to
   9 build tcpdump; just make sure the tcpdump and libpcap directory trees
  10 have the same parent directory.
  11
  12 If configure says:
  13
  14     configure: warning: cannot determine packet capture interface
  15     configure: warning: (see INSTALL for more info)
  16
  17 then your system either does not support packet capture or your system
  18 does support packet capture but libpcap does not support that
  19 particular type. (If you have HP-UX, see below.) If your system uses a
  20 packet capture not supported by libpcap, please send us patches; don't
  21 forget to include an autoconf fragment suitable for use in
  22 configure.in.
  23
  24 It is possible to override the default packet capture type, although
  25 the circumstance where this works are limited. For example if you have
  26 installed bpf under SunOS 4 and wish to build a snit libpcap:
  27
  28     ./configure --with-pcap=snit
  29
  30 Another example is to force a supported packet capture type in the case
  31 where the configure scripts fails to detect it.
  32
  33 You will need an ANSI C compiler to build libpcap. The configure script
  34 will abort if your compiler is not ANSI compliant. If this happens, use
  35 the GNU C compiler, available via anonymous ftp:
  36
  37         ftp://prep.ai.mit.edu/pub/gnu/gcc-*.tar.gz
  38
  39 Note well: If you use gcc, you may need to run its "fixincludes"
  40 script. Running fixincludes is not required with later versions of gcc
  41 and in some cases (e.g. Solaris 2.5) causes problems when run. The
  42 configure script will abort with:
  43
  44     checking for ANSI ioctl definitions... yes
  45     configure: error: see the INSTALL for more info
  46
  47 if it detects if the fixincludes needs to be run. If the fixincludes
  48 test in configure passes, you're probably ok.
  49
  50 If you use flex, you must use version 2.4.6 or higher. The configure
  51 script automatically detects the version of flex and will not use it
  52 unless it is new enough. You can use "flex -V" to see what version you
  53 have (unless it's really old). The current version of flex is available
  54 via anonymous ftp:
  55
  56         ftp://ftp.ee.lbl.gov/flex-*.tar.Z
  57
  58 As of this writing, the current version is 2.5.4.
  59
  60 If you use bison, you must use flex (and visa versa). The configure
  61 script automatically falls back to lex and yacc if both flex and bison
  62 are not found.
  63
  64 Sometimes the stock C compiler does not interact well with flex and
  65 bison. The list of problems includes undefined references for alloca.
  66 You can get around this by installing gcc or manually disabling flex
  67 and bison with:
  68
  69     ./configure --without-flex --without-bison
  70
  71 If your system only has AT&T lex, this is okay unless your libpcap
  72 program uses other lex/yacc generated code. (Although it's possible to
  73 map the yy* identifiers with a script, we use flex and bison so we
  74 don't feel this is necessary.)
  75
  76 Some systems support the Berkeley Packet Filter natively; for example
  77 out of the box OSF and BSD/OS have bpf. If your system does not support
  78 bpf, you will need to pick up:
  79
  80         ftp://ftp.ee.lbl.gov/bpf-*.tar.Z
  81
  82 Note well: you MUST have kernel source for your operating system in
  83 order to install bpf. An exception is SunOS 4; the bpf distribution
  84 includes replacement kernel objects for some of the standard SunOS 4
  85 network device drivers. See the bpf INSTALL document for more
  86 information.
  87
  88 If you use Solaris, there is a bug with bufmod(7) that is fixed in
  89 Solaris 2.3.2 (aka SunOS 5.3.2). Setting a snapshot length with the
  90 broken bufmod(7) results in data be truncated from the FRONT of the
  91 packet instead of the end.  The work around is to not set a snapshot
  92 length but this results in performance problems since the entire packet
  93 is copied to user space. If you must run an older version of Solaris,
  94 there is a patch available from Sun; ask for bugid 1149065. After
  95 installing the patch, use "setenv BUFMOD_FIXED" to enable use of
  96 bufmod(7). However, we recommend you run a more current release of
  97 Solaris.
  98
  99 If you use the SPARCompiler, you must be careful to not use the
 100 /usr/ucb/cc interface. If you do, you will get bogus warnings and
 101 perhaps errors. Either make sure your path has /opt/SUNWspro/bin
 102 before /usr/ucb or else:
 103
 104     setenv CC /opt/SUNWspro/bin/cc
 105
 106 before running configure. (You might have to do a "make distclean"
 107 if you already ran configure once).
 108
 109 Also note that "make depend" won't work; while all of the known
 110 universe uses -M, the SPARCompiler uses -xM to generate makefile
 111 dependencies.
 112
 113 If you are trying to do packet capture with a FORE ATM card, you may or
 114 may not be able to. They usually only release their driver in object
 115 code so unless their driver supports packet capture, there's not much
 116 libpcap can do.
 117
 118 If you get an error like:
 119
 120     tcpdump: recv_ack: bind error 0x???
 121
 122 when using DLPI, look for the DL_ERROR_ACK error return values, usually
 123 in /usr/include/sys/dlpi.h, and find the corresponding value.
 124
 125 Under OSF, packet capture must be enabled before it can be used. For
 126 instructions on how to enable packet filter support, see:
 127
 128         ftp://ftp.digital.com/pub/Digital/dec-faq/Digital-UNIX
 129
 130 Once you enable packet filter support, your OSF system will support bpf
 131 natively.
 132
 133 Under Ultrix, packet capture must be enabled before it can be used. For
 134 instructions on how to enable packet filter support, see:
 135
 136         ftp://ftp.digital.com/pub/Digital/dec-faq/ultrix
 137
 138 If you use HP-UX, you must have at least version 9 and either the
 139 version of cc that supports ANSI C (cc -Aa) or else use the GNU C
 140 compiler. You must also buy the optional streams package. If you don't
 141 have:
 142
 143     /usr/include/sys/dlpi.h
 144     /usr/include/sys/dlpi_ext.h
 145
 146 then you don't have the streams package. In addition, we believe you
 147 need to install the "9.X LAN and DLPI drivers cumulative" patch
 148 (PHNE_6855) to make the version 9 DLPI work with libpcap.
 149
 150 It's been reported that the DLPI streams package is standard starting
 151 with HP-UX 10.
 152
 153 The HP implementation of DLPI is a little bit eccentric. Unlike
 154 Solaris, you must attach /dev/dlpi instead of the specific /dev/*
 155 network pseudo device entry in order to capture packets. The ppa is
 156 based on the ifnet "index" number. Under HP-UX 9, it is necessary to
 157 read /dev/kmem and the kernel symbol file (/hp-ux). Under HP-UX 10,
 158 dlpi can provide information for determining the ppa. It does not seem
 159 to be possible to trace the loopback interface. Unlike other DLPI
 160 implementations, PHYS implies MULTI and SAP and you get an error if you
 161 try to enable more than one promiscous more than one promiscuous mode
 162 at a time. Finally, testing shows that there can't be more than one
 163 simultaneous dlpi user per network interface and you cannot capture
 164 outbound packets.
 165
 166 If you use Linux, this version of libpcap is known to compile and run
 167 under Red Hat 4.0 with the 2.0.25 kernel. It may work with earlier 2.X
 168 versions but is guaranteed not to work with 1.X kernels. Running more
 169 than one libpcap program at a time can cause problems since promiscuous
 170 mode is implemented by twiddlin the interface flags from the libpcap
 171 application. Also, packet timestamps aren't very good. This appears to
 172 be due to haphazard handling of the timestamp in the kernel.
 173
 174 Note well: there is rumoured to be a version of tcpdump floating around
 175 called 3.0.3 that includes libpcap and is supposed to support Linux.
 176 You should be advised that the Network Research Group at LBNL never
 177 generated a release with this version number. We note with interest
 178 that a standard cracker trick to get people to install trojans is to
 179 distribute bogus packages that have a version number higher than the
 180 current release. We also note with annoyance that 90% of the Linux
 181 related bug reports we get are due to changes made to unofficial
 182 versions of our page. If you are having trouble but aren't using a
 183 version that came from ftp.ee.lbl.gov, please try that before
 184 submitting a bug report!
 185
 186 If you use AIX, you may not be able to build libpcap from this release.
 187 Although AIX 4 ships with tcpdump, it is an old version that predates
 188 libpcap. We do not have an AIX system in house so it's impossible for
 189 us to test AIX patches submitted to us. We are told that you must link
 190 against /lib/pse.exp, that you must use AIX cc or a GNU C compiler
 191 newer than 2.7.2 and that you may need to run strload before running a
 192 libpcap application. Also, it may be necessary to run the configure
 193 script as root in order for it to detect that bpf is available. Another
 194 workaround is to use:
 195
 196     ./configure --with-pcap=bpf
 197
 198 If you use NeXTSTEP, you will not be able to build libpcap from this
 199 release. We hope to support this operating system in some future
 200 release of libpcap.
 201
 202 If you use SINIX, you should be able to build libpcap from this
 203 release. It is known to compile and run on SINIX-Y/N 5.42 with the C-DS
 204 V1.0 or V1.1 compiler. But note that in some releases of SINIX, yacc
 205 emits incorrect code; if grammar.y fails to compile, change every
 206 occurence of:
 207
 208         #ifdef YYDEBUG
 209
 210 to:
 211         #if YYDEBUG
 212
 213 Another workaround is to use flex and bison.
 214
 215 If you use SCO, you might have trouble building libpcap from this
 216 release. We do not have a machine running SCO and have not had reports
 217 of anyone successfully building on it. Since SCO apparently supports
 218 dlpi, it's possible the current version works. Meanwhile, sco provides
 219 a tcpdump binary as part of their "Network/Security Tools" package:
 220
 221     http://www.sco.com/technology/internet/goodies/#SECURITY
 222
 223 There is also a README that explains how to enable packet capture.
 224
 225 If you use UnixWare, you will not be able to build libpcap from this
 226 release. We hope to support this operating system in some future
 227 release of libpcap. Meanwhile, there appears to be an UnixWare port of
 228 libpcap 0.0 (and tcpdump 3.0) in:
 229
 230     ftp://ftp1.freebird.org/pub/mirror/freebird/internet/systools/
 231
 232 UnixWare appears to use a hacked version of DLPI.
 233
 234 If linking tcpdump fails with "Undefined: _alloca" when using bison on
 235 a Sun4, your version of bison is broken. In any case version 1.16 or
 236 higher is recommended (1.14 is known to cause problems 1.16 is known to
 237 work). Either pick up a current version from:
 238
 239         ftp://prep.ai.mit.edu/pub/gnu/bison.tar.gz
 240
 241 or hack around it by inserting the lines:
 242
 243         #ifdef __GNUC__
 244         #define alloca __builtin_alloca
 245         #else
 246         #ifdef sparc
 247         #include <alloca.h>
 248         #else
 249         char *alloca ();
 250         #endif
 251         #endif
 252
 253 right after the (100 line!) GNU license comment in bison.simple, remove
 254 grammar.[co] and fire up make again.
 255
 256 If you use SunOS 4, your kernel must support streams NIT. If you run a
 257 libpcap program and it dies with:
 258
 259     /dev/nit: No such device
 260
 261 You must add streams NIT support to your kernel configuration, run
 262 config and boot the new kernel.
 263
 264 If you are running a version of SunOS earlier than 4.1, you will need
 265 to replace the Sun supplied /sys/sun{3,4,4c}/OBJ/nit_if.o with the
 266 appropriate version from this distribution's SUNOS4 subdirectory and
 267 build a new kernel:
 268
 269         nit_if.o.sun3-sunos4            (any flavor of sun3)
 270         nit_if.o.sun4c-sunos4.0.3c      (SS1, SS1+, IPC, SLC, etc.)
 271         nit_if.o.sun4-sunos4            (Sun4's not covered by
 272                                             nit_if.o.sun4c-sunos4.0.3c)
 273
 274 These nit replacements fix a bug that makes nit essentially unusable in
 275 pre-SunOS 4.1.  In addition, our sun4c-sunos4.0.3c nit gives you
 276 timestamps to the resolution of the SS-1 clock (1 us) rather than the
 277 lousy 20ms timestamps Sun gives you  (tcpdump will print out the full
 278 timestamp resolution if it finds it's running on a SS-1).
 279
 280 FILES
 281 -----
 282 CHANGES         - description of differences between releases
 283 FILES           - list of files exported as part of the distribution
 284 INSTALL         - this file
 285 Makefile.in     - compilation rules (input to the configure script)
 286 README          - description of distribution
 287 SUNOS4          - pre-SunOS 4.1 replacement kernel nit modules
 288 VERSION         - version of this release
 289 aclocal.m4      - autoconf macros
 290 bpf/net         - copies of bpf_filter.c and bpf.h
 291 bpf_filter.c    - symlink to bpf/net/bpf_filter.c
 292 bpf_image.c     - bpf disassembly routine
 293 config.guess    - autoconf support
 294 config.sub      - autoconf support
 295 configure       - configure script (run this first)
 296 configure.in    - configure script source
 297 etherent.c      - /etc/ethers support routines
 298 ethertype.h     - ethernet protocol types and names definitions
 299 gencode.c       - bpf code generation routines
 300 gencode.h       - bpf code generation definitions
 301 grammar.y       - filter string grammar
 302 inet.c          - network routines
 303 install-sh      - BSD style install script
 304 lbl/gnuc.h      - gcc macros and defines
 305 lbl/os-*.h      - os dependent defines and prototypes
 306 linux-include/* - network include files missing on Linux
 307 mkdep           - construct Makefile dependency list
 308 nametoaddr.c    - hostname to address routines
 309 net             - symlink to bpf/net
 310 optimize.c      - bpf optimization routines
 311 pcap-bpf.c      - BSD Packet Filter support
 312 pcap-dlpi.c     - Data Link Provider Interface support
 313 pcap-enet.c     - enet support
 314 pcap-int.h      - internal libpcap definitions
 315 pcap-namedb.h   - public libpcap name database definitions
 316 pcap-nit.c      - Network Interface Tap support
 317 pcap-nit.h      - Network Interface Tap definitions
 318 pcap-null.c     - dummy monitor support (allows offline use of libpcap)
 319 pcap-pf.c       - Packet Filter support
 320 pcap-pf.h       - Packet Filter definitions
 321 pcap-snit.c     - Streams based Network Interface Tap support
 322 pcap-snoop.c    - Snoop network monitoring support
 323 pcap.3          - manual entry
 324 pcap.c          - pcap utility routines
 325 pcap.h          - public libpcap definitions
 326 ppp.h           - Point to Point Protocol definitions
 327 savefile.c      - offline support
 328 scanner.l       - filter string scanner