From 28e545e149a553ee43ef7612ee70baa82db9a91d Mon Sep 17 00:00:00 2001 From: guy Date: Sat, 17 Nov 2001 21:29:58 +0000 Subject: Note that we now attempt to work around AIX BPF's weirdness, indicate that there may be compile-time or run-time problems with the workarounds, suggest that people send in a detailed report and fall back on DLPI if they have those problems, and suggest that if they construct fixes for the problems they send them to patches@tcpdump.org. Fix the white space. --- README.aix | 68 +++++++++++++++++++++++++++++++++++++------------------------- 1 file changed, 41 insertions(+), 27 deletions(-) (limited to 'README.aix') diff --git a/README.aix b/README.aix index c78a40b..ad2ce45 100644 --- a/README.aix +++ b/README.aix @@ -1,6 +1,20 @@ -(1) To configure libpcap under AIX 4.x, you should use DLPI instead - of BPF, since IBM's version of BPF includes some undocumented - and unsupported changes to the original 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 + 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). + + If you fix the problems yourself, please send to patches@tcpdump.org + a patch, so we can incorporate them into the next release. + + If you don't fix the problems yourself, you can, as a workaround, + make libpcap use DLPI instead of BPF. This can be done by specifying the flag: @@ -8,39 +22,39 @@ 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: +(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: - lslpp -l bos.rte.tty + lslpp -l bos.rte.tty - bos.rte.tty 4.3.2.4 COMMITTED Base TTY Support and Commands + 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/ + Updates for AIX filesets can be obtained from: + ftp://service.software.ibm.com/aix/fixes/ - These updates can be installed with the smit program. + These updates can be installed with the smit program. -(3) After compiling libpcap, you need to make sure that the DLPI driver - is loaded. Type: +(3) 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 + If the result is: + dlpi: yes - then the DLPI driver is loaded correctly. + then the DLPI driver is loaded correctly. - If it is: - dlpi: no + If it is: + dlpi: no - Then you need to type: - strload -f /etc/dlpi.conf + Then you need to type: + strload -f /etc/dlpi.conf - Check again with strload -q -d dlpi that the dlpi driver is loaded. + 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. + 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. -- cgit v1.2.3