README.aix 3.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  1. Using BPF:
  2. (1) AIX 4.x's version of BPF is undocumented and somewhat unstandard; the
  3. current BPF support code includes changes that should work around
  4. that; it appears to compile and work on at least one AIX 4.3.3
  5. machine.
  6. Note that the BPF driver and the "/dev/bpf" devices might not exist
  7. on your machine; AIX's tcpdump loads the driver and creates the
  8. devices if they don't already exist. Our libpcap should do the
  9. same, and the configure script should detect that it's on an AIX
  10. system and choose BPF even if the devices aren't there.
  11. Also note that tcpdump _binary_ compiled on AIX 4 may have a problem
  12. doing the initial loading of the BPF driver if copied to AIX 5 and
  13. run there (GH #52). tcpdump binary natively compiled on AIX 5 should
  14. not have this issue.
  15. (2) If libpcap doesn't compile on your machine when configured to use
  16. BPF, or if the workarounds fail to make it work correctly, you
  17. should send to tcpdump-workers@lists.tcpdump.org a detailed bug
  18. report (if the compile fails, send us the compile error messages;
  19. if it compiles but fails to work correctly, send us as detailed as
  20. possible a description of the symptoms, including indications of the
  21. network link-layer type being wrong or time stamps being wrong).
  22. If you fix the problems yourself, please submit a patch by forking
  23. the branch at
  24. https://github.com/the-tcpdump-group/libpcap/issues
  25. and issuing a pull request, so we can incorporate the fixes into the
  26. next release.
  27. If you don't fix the problems yourself, you can, as a workaround,
  28. make libpcap use DLPI instead of BPF.
  29. This can be done by specifying the flag:
  30. --with-pcap=dlpi
  31. to the "configure" script for libpcap.
  32. If you use DLPI:
  33. (1) It is a good idea to have the latest version of the DLPI driver on
  34. your system, since certain versions may be buggy and cause your AIX
  35. system to crash. DLPI is included in the fileset bos.rte.tty. I
  36. found that the DLPI driver that came with AIX 4.3.2 was buggy, and
  37. had to upgrade to bos.rte.tty 4.3.2.4:
  38. lslpp -l bos.rte.tty
  39. bos.rte.tty 4.3.2.4 COMMITTED Base TTY Support and Commands
  40. Updates for AIX filesets can be obtained from:
  41. ftp://service.software.ibm.com/aix/fixes/
  42. These updates can be installed with the smit program.
  43. (2) After compiling libpcap, you need to make sure that the DLPI driver
  44. is loaded. Type:
  45. strload -q -d dlpi
  46. If the result is:
  47. dlpi: yes
  48. then the DLPI driver is loaded correctly.
  49. If it is:
  50. dlpi: no
  51. Then you need to type:
  52. strload -f /etc/dlpi.conf
  53. Check again with strload -q -d dlpi that the dlpi driver is loaded.
  54. Alternatively, you can uncomment the lines for DLPI in
  55. /etc/pse.conf and reboot the machine; this way DLPI will always
  56. be loaded when you boot your system.
  57. (3) There appears to be a problem in the DLPI code in some versions of
  58. AIX, causing a warning about DL_PROMISC_MULTI failing; this might
  59. be responsible for DLPI not being able to capture outgoing packets.