Service and channel management for subscribers with dynamically assigned IP address is performed by a codemane (LOGIN), which is specified in the control commands by corresponding --login long option. To support the DPI login binding feature you need to activate the UDR.

If the dynamic IP addresses assignment is performed by the Radius server, it is recommended to use the "Radius event monitor", which will automatically transmit to the dpi the information on the IP addresses being assigned and released. In this case, the User-Name attribute in the Radius requests is used as a login.

To integrate with other platforms, it is necessary to support the custom scripts triggered by the events of IP address assignment and releasing (for example, this feature is present in the standard dhcp linux server). In this case, the IP address and LOGIN binding as well as the deletion of the bind are performed using special commands.

IP address and LOGIN bind

fdpi_ctrl load --bind --user subscriber_name:ip_address

The example:

fdpi_ctrl load --bind --user test_user:191.168.1.1
fdpi_ctrl load --bind --user test_user:2a00:0:0:0:7aac:c0ff:fea7:d4c/64

To delete the IP ↔ login bind

fdpi_ctrl del --bind --login subscriber_name

To list the binded subscriber IP address

fdpi_ctrl list --bind --login subscriber_name

To list all the subscribers having binded IP

fdpi_ctrl list all --bind

The next section discusses the binding of subscribers with an arbitrary IP addresses number. An important difference between bind semantics and bind_multi one is:

1. load --bind replaces the address previously assigned to the subscriber, while load --bind_multi adds it
2. load --bind automatically takes the assigned address from another subscriber
3. load --bind uses the database more efficiently