summaryrefslogtreecommitdiffstats
path: root/contrib/libpcap/README.aix
diff options
context:
space:
mode:
Diffstat (limited to 'contrib/libpcap/README.aix')
-rw-r--r--contrib/libpcap/README.aix54
1 files changed, 36 insertions, 18 deletions
diff --git a/contrib/libpcap/README.aix b/contrib/libpcap/README.aix
index ad2ce45..dcddb61 100644
--- a/contrib/libpcap/README.aix
+++ b/contrib/libpcap/README.aix
@@ -1,11 +1,20 @@
+Using BPF:
+
(1) AIX 4.x's version of BPF is undocumented and somewhat unstandard; the
current BPF support code includes changes that should work around
- that, but, lacking an AIX machine on which to compile it, we don't
- know whether the BPF support for AIX will compile.
-
- If it doesn't, or if the workarounds fail to make it work correctly,
- you should send to tcpdump-workers@tcpdump.org a detailed bug report
- (if the compile fails, send us the compile error messages; if it
+ that; it appears to compile and work on at least one AIX 4.3.3
+ machine.
+
+ Note that the BPF driver and the "/dev/bpf" devices might not exist
+ on your machine; AIX's tcpdump loads the driver and creates the
+ devices if they don't already exist. Our libpcap should do the
+ same, and the configure script should detect that it's on an AIX
+ system and choose BPF even if the devices aren't there.
+
+(2) If libpcap doesn't compile on your machine when configured to use
+ BPF, or if the workarounds fail to make it work correctly, you
+ should send to tcpdump-workers@tcpdump.org a detailed bug report (if
+ the compile fails, send us the compile error messages; if it
compiles but fails to work correctly, send us as detailed as
possible a description of the symptoms, including indications of the
network link-layer type being wrong or time stamps being wrong).
@@ -22,39 +31,48 @@
to the "configure" script for libpcap.
-(2) Also, it is a good idea to have the latest version of the DLPI
- driver on your system, since certain versions may be buggy and
- cause your AIX system to crash. DLPI is included in the
- fileset bos.rte.tty. I found that the DLPI driver that came with
- AIX 4.3.2 was buggy, and had to upgrade to bos.rte.tty 4.3.2.4:
+If you use DLPI:
- lslpp -l bos.rte.tty
+(1) It is a good idea to have the latest version of the DLPI driver on
+ your system, since certain versions may be buggy and cause your AIX
+ system to crash. DLPI is included in the fileset bos.rte.tty. I
+ found that the DLPI driver that came with AIX 4.3.2 was buggy, and
+ had to upgrade to bos.rte.tty 4.3.2.4:
- bos.rte.tty 4.3.2.4 COMMITTED Base TTY Support and Commands
+ lslpp -l bos.rte.tty
+
+ bos.rte.tty 4.3.2.4 COMMITTED Base TTY Support and Commands
Updates for AIX filesets can be obtained from:
ftp://service.software.ibm.com/aix/fixes/
These updates can be installed with the smit program.
-(3) After compiling libpcap, you need to make sure that the DLPI driver
+(2) After compiling libpcap, you need to make sure that the DLPI driver
is loaded. Type:
- strload -q -d dlpi
+ strload -q -d dlpi
If the result is:
- dlpi: yes
+
+ dlpi: yes
then the DLPI driver is loaded correctly.
If it is:
- dlpi: no
+
+ dlpi: no
Then you need to type:
- strload -f /etc/dlpi.conf
+
+ strload -f /etc/dlpi.conf
Check again with strload -q -d dlpi that the dlpi driver is loaded.
Alternatively, you can uncomment the lines for DLPI in
/etc/pse.conf and reboot the machine; this way DLPI will always
be loaded when you boot your system.
+
+(3) There appears to be a problem in the DLPI code in some versions of
+ AIX, causing a warning about DL_PROMISC_MULTI failing; this might
+ be responsible for DLPI not being able to capture outgoing packets.
OpenPOWER on IntegriCloud