README.septel 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
  1. The following instructions apply if you have a Linux platform and want
  2. libpcap to support the Septel range of passive network monitoring cards
  3. from Intel (http://www.intel.com)
  4. 1) Install and build the Septel software distribution by following the
  5. instructions supplied with that package.
  6. 2) Configure libcap. To allow the 'configure' script to locate the Septel
  7. software distribution use the '--with-septel' option:
  8. ./configure --with-septel=DIR
  9. where DIR is the root of the Septel software distribution, for example
  10. /var/src/septel.
  11. By default (if you write only ./configure --with-septel) it takes
  12. ./../septel as argument for DIR.
  13. If the Septel software is correctly detected 'configure' will
  14. report:
  15. checking whether we have Septel API... yes
  16. If 'configure' reports that there is no Septel API, the directory may have been
  17. incorrectly specified or the Septel software was not built before configuring
  18. libpcap.
  19. See also the libpcap INSTALL.txt file for further libpcap configuration
  20. options.
  21. Building libpcap at this stage will include support for both the native
  22. packet capture stream and for capturing from Septel cards. To build
  23. libpcap with only Septel support specify the capture type as 'septel'
  24. when configuring libpcap:
  25. ./configure --with-septel=DIR --with-pcap=septel
  26. Applications built with libpcap configured in this way will only detect Septel
  27. cards and will not capture from the native OS packet stream.
  28. Note: As mentioned in pcap-septel.c we should first edit the system.txt
  29. file to change the user part example (UPE) module id to 0xdd instead of
  30. 0x2d for technical reason. So this change in system.txt is crucial and
  31. things will go wrong if it's not done. System.txt along with config.txt
  32. are configuration files that are edited by the user before running the
  33. gctload program that uses these files for initialising modules and
  34. configuring parameters.
  35. ----------------------------------------------------------------------
  36. for more information please contact me : gil_hoyek@hotmail.com