-@(#) $Header: /tcpdump/master/libpcap/INSTALL.txt,v 1.1 2001-05-05 00:57:10 mcr Exp $ (LBL)
+@(#) $Header: /tcpdump/master/libpcap/INSTALL.txt,v 1.2 2001-06-05 03:45:53 guy Exp $ (LBL)
To build libpcap, run "./configure" (a shell script). The configure
script will determine your system attributes and generate an
this.
If you use AIX, you may not be able to build libpcap from this release.
-libpcap. We do not have an AIX system in house so it's impossible for
-us to test AIX patches submitted to us. We are told that you must link
-against /lib/pse.exp, that you must use AIX cc or a GNU C compiler
-newer than 2.7.2 and that you may need to run strload before running a
-libpcap application.
+We do not have an AIX system in house so it's impossible for us to test
+AIX patches submitted to us. We are told that you must link against
+/lib/pse.exp, that you must use AIX cc or a GNU C compiler newer than
+2.7.2, and that you may need to run strload before running a libpcap
+application.
Read the README.aix file for information on installing libpcap and
configuring your system to be able to support libpcap.
-@(#) $Header: /tcpdump/master/libpcap/README,v 1.23 2001-04-11 05:18:28 guy Exp $ (LBL)
+@(#) $Header: /tcpdump/master/libpcap/README,v 1.24 2001-06-05 03:45:55 guy Exp $ (LBL)
LIBPCAP 0.6.2
Now maintained by "The Tcpdump Group"
Anonymous CVS is available via:
- cvs -d cvs.tcpdump.org:/tcpdump/master login
+ cvs -d :pserver:tcpdump@cvs.tcpdump.org:/tcpdump/master login
(password "anoncvs")
- cvs -d cvs.tcpdump.org:/tcpdump/master checkout libpcap
+ cvs -d :pserver:tcpdump@cvs.tcpdump.org:/tcpdump/master checkout libpcap
Version 0.6.2 of LIBPCAP can be retrieved with the CVS tag "libpcap_0_6rel2":
- cvs -d cvs.tcpdump.org:/tcpdump/master checkout -r libpcap_0_6rel2 libpcap
+ cvs -d :pserver:tcpdump@cvs.tcpdump.org:/tcpdump/master checkout -r libpcap_0_6rel2 libpcap
should stick to the standard.
- The source files should be better documented. There is no official
- design guideline what is done where. There should be a common coding
- style (okay, you can guess that bye looking at the code) and a guideline
+ design guideline for what is done where. There should be a common coding
+ style (okay, you can guess that by looking at the code) and a guide for
what needs to be documented.
Linux kernel interface
- Currently there is a race condition in that a socket is activated at the
- same time when it is opened - before applying a filter. This has to
+ same time it is opened - before applying a filter. This has to
be corrected so that capture starts when pcap_read is called for the
first time.
- Better documentation and cleanup of the interface. I am seeing a few
problems at the first glance which needs fixing:
+ pcap_lookupnet makes little to no sense with protocols != IPv4
- + not very suited for interactive programs (think ethereal). There should
- be a way for the application to get a file descriptor which it has to
- monitor and a callback in pcap which has to be called on activity
+ + not very well suited for interactive programs (think ethereal). There
+ should be a way for the application to get a file descriptor which it
+ has to monitor and a callback in pcap which has to be called on
+ activity (XXX - "pcap_fileno()" handles the first part, although
+ "select()" and "poll()" don't work on BPF devices on most BSDs, and
+ you can call "pcap_dispatch()" as the dispatch routine after putting
+ the descriptor into non-blocking mode)
+ too many functions. There are a lot of functions for everything which
violates the KISS principle. Why do we need pcap_strerror, pcap_perror
and pcap_geterr?