en:dpi:dpi_components:platform:dpi_dynamicip:start [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks

    • Differences

    This shows you the differences between two versions of the page.

    Link to this comparison view

    Both sides previous revisionPrevious revision
    Next revision    		Previous revision
    en:dpi:dpi_components:platform:dpi_dynamicip:start [2023/08/29 07:26] – edrudichgmailcomen:dpi:dpi_components:platform:dpi_dynamicip:start [2024/06/10 13:44] (current) – removed elena.krasnobryzh
    Line 1: Line 1:
    -====== Dynamic IP subscribers' support ====== 
    -{{indexmenu_n>7}} 
    -The nominal name (LOGIN) is used to control services and a channel for each subscriber that uses dynamic IP. This name is specified in [[en:dpi:dpi_components:platform:subscriber_management:subsman_cmd:start|control instructions]] by the respective parameter --login. [[en:dpi:dpi_components:platform:dpi_admin:admin_db:start#Activating the built-in database|UDR activation]] is required to support login name binding in DPI. 
      
    -We recommend to use "Radius Events Monitor" if dynamic addresses are assigned by Radius server. "Radius Events Monitor" automatically sends to DPI the information about assigned and released IP addresses. The attribute User-Name is used as login in Radius queries. 
    - 
    -Execution of user's scripts by events of assignment and release of IP address has to be supported by other platforms for successful integration. For example the common DHCP server of Linux supports this functionality. Binding of IP address with LOGIN and removing of this link is handled by special commands. 
    - 
    -Binding IP address and LOGIN: 
    -<code> 
    -fdpi_ctrl load --bind --user subscribers_name:ip_адрес 
    - 
    -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 
    -</code>  
    -Removing of the link IP <-> login 
    -<code> 
    -fdpi_ctrl del --bind --login subscribers_name 
    -</code>   
    - 
    -To check the binded IP subscriber: 
    -<code> 
    -fdpi_ctrl list --bind --login subscribers_name 
    -</code>   
    - 
    -List all subscribers with binded IPs: 
    -<code> 
    -fdpi_ctrl list all --bind 
    -</code>   
    - 
    -The next section discusses the connection of subscribers with an arbitrary number of IP addresses. An important difference between bind and bind_multi semantics is: - load –bind replaces the address previously assigned to the subscriber, while load –bind_multi adds it — load –bind automatically takes the assigned address from the other subscriber — load –bind spends the database size more economically