This is an old revision of the document!
Management
One can control start and stop of the recording on the platform by SM fdpi_ctrl utility when the parameter ajb_reserved=1 is set:
fdpi_ctrl setenv --ajb_save_url 1 fdpi_ctrl setenv --ajb_save_udpi 1
Recording subscriber traffic in PCAP1)
To activate:
fdpi_ctrl load --service 12 --ip 192.168.1.1 fdpi_ctrl load --service 12 --login USER101
To stop:
fdpi_ctrl del --service 12 --ip 192.168.1.1 fdpi_ctrl del --service 12 --login USER101
All subscriber traffic is recorded. The PCAP file is located according to the path specified in the basic ajb_udpi_path setting.
To quickly find data in a PCAP file, you can create a file with indexed data by turning on the settings in /etc/dpi/fastdpi.conf
ajb_pcap_ind_mask=1
Here:
- 0 - index is not created (default value)
- 1 - IPv4
- 2 - IPv6
- 3 - both IPv4 and IPv6.
If other recording methods are enabled for this subscriber (ajb_save_udpi or ajb_save_ip), then SESSION_ID will be not recorded to the resulting index.
1)
due to an error in version 8.3, you need to enable the ajb_save_ip=127.127.127.127 setting on a null address to initialize the recording subsystem