nexmon – Blame information for rev 1
?pathlinks?
Rev | Author | Line No. | Line |
---|---|---|---|
1 | office | 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 | |||
5 | 1) Install and build the Septel software distribution by following the |
||
6 | instructions supplied with that package. |
||
7 | |||
8 | 2) Configure libcap. To allow the 'configure' script to locate the Septel |
||
9 | software distribution use the '--with-septel' option: |
||
10 | |||
11 | ./configure --with-septel=DIR |
||
12 | |||
13 | where DIR is the root of the Septel software distribution, for example |
||
14 | /var/src/septel. |
||
15 | |||
16 | By default (if you write only ./configure --with-septel) it takes |
||
17 | ./../septel as argument for DIR. |
||
18 | |||
19 | If the Septel software is correctly detected 'configure' will |
||
20 | report: |
||
21 | |||
22 | checking whether we have Septel API... yes |
||
23 | |||
24 | If 'configure' reports that there is no Septel API, the directory may have been |
||
25 | incorrectly specified or the Septel software was not built before configuring |
||
26 | libpcap. |
||
27 | |||
28 | See also the libpcap INSTALL.txt file for further libpcap configuration |
||
29 | options. |
||
30 | |||
31 | Building libpcap at this stage will include support for both the native |
||
32 | packet capture stream and for capturing from Septel cards. To build |
||
33 | libpcap with only Septel support specify the capture type as 'septel' |
||
34 | when configuring libpcap: |
||
35 | |||
36 | ./configure --with-septel=DIR --with-pcap=septel |
||
37 | |||
38 | Applications built with libpcap configured in this way will only detect Septel |
||
39 | cards and will not capture from the native OS packet stream. |
||
40 | |||
41 | Note: As mentioned in pcap-septel.c we should first edit the system.txt |
||
42 | file to change the user part example (UPE) module id to 0xdd instead of |
||
43 | 0x2d for technical reason. So this change in system.txt is crutial and |
||
44 | things will go wrong if it's not done. System.txt along with config.txt |
||
45 | are configuration files that are edited by the user before running the |
||
46 | gctload program that uses these files for initialising modules and |
||
47 | configuring parameters. |
||
48 | |||
49 | ---------------------------------------------------------------------- |
||
50 | for more information please contact me : gil_hoyek@hotmail.com |