Configuration

The option can be enabled in two ways:

Default profile: global configuration on the device, connected as a service without specifying a profile.

Named profile: connected as a service with the name of the profile.

For BRAS you have to use profiles named in the Radius-Accept attributes.

Default profile

Enable the configuration parameter in /etc/dpi/fastdpi.conf for the default profile without a named one:

cp_server=192.168.0.18/cp

Here 192.168.0.18 — is the name or the address of the information page1) additional parameters can be added (according to HTTP rules) only after ? or &, they must be specified in the URL for whitelisting and here you should think for DPI, otherwise DPI will assign /? .

This address may include a (partial) path. This allows using the same server for various kinds of services.

After the parameter is added you need to restart the service:

service fastdpi restart

In this case management is carried out through connecting service 5 without specifying a profile:

fdpi_ctrl load --service 5 --ip 192.168.0.1 fdpi_ctrl load --service 5 --login user01
The white lists from /var/lib/dpi directory are used. Preparing white list

Named profile

Find out how to configure the named profile in the next section.

Additional settings

The maximum number of profiles for whitelists is set by the configuration parameter in etc/dpi/fastdpi.conf

for allow lists (service 5)

max_profiles_white_list=4

where 4 is the default value and 65535 is the maximum possible value

for allow lists (service 16)

max_profiles_serv16=32

where 32 is the default value and 65535 is the maximum possible value

This is a cold parameter and requires a restart of fastdpi.