Configuration [Документация 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:radius:radius_config [2024/09/26 15:29] – external edit 127.0.0.1en:dpi:dpi_components:radius:radius_config [2025/04/11 13:25] (current) – [Radius Monitor Setup] elena.krasnobryzh
    Line 55: Line 55:
     ===== Radius Monitor Setup ===== ===== Radius Monitor Setup =====
     <note important>Radius events monitor is configured by the file **/etc/dpi/fdpi_radius.conf.**</note> <note important>Radius events monitor is configured by the file **/etc/dpi/fdpi_radius.conf.**</note>
    -<code> 
    -# FastDPI RADIUS configuration parameters: 
    -# listening interface name 
    -in_dev=tap1 
    -# listening port number (or a list of ports separated by commas) with Radius Accounting packets 
    -rad_acct_port=1813,1814,1815 
    -# save bad PDUs in pcap format for analysis 
    -rad_save_pdu=0 
    -# analyze PDU with code 2 and 4 
    -rad_check_code_pdu=2:4 
    -# analyze PDU with status 1 and 3 
    -rad_check_acct_status_type=1:3 
    -# initialize memory at start  
    -mem_preset=1 
    -# List of DPI servers, to send data to 
    -fdpi_servers=127.0.0.1:29000,123.45.67.85:29000 
      
    -# stream processing setup (it is recommended to use the values from the example) +  * ''in_dev=tap1'' — listening interface name 
    -num_threads=1 +  * ''rad_acct_port=1813,1814,1815'' — listening port number (or a list of ports separated by commas) with Radius Accounting packets 
    -rx_bind_core=0 +  * ''rad_save_pdu=0'' — save bad PDUs in pcap format for analysis 
    -services_bind_cores=0 +  * ''rad_check_code_pdu=2:4'' — analyze PDU with code 2 and 4 
    -engine_bind_cores=0 +  * ''rad_check_acct_status_type=1:3'' — analyze PDU with status 1 and 3 
    -fifo_bind_cores=0 +  * ''mem_preset=1'' — initialize memory at start  
    -snaplen=2000 +  * ''fdpi_servers=127.0.0.1:29000,123.45.67.85:29000'' — List of DPI servers, to send data to 
    -timeout_alarm=5 +  * ''ipfix_extra_gsm=1'' — enable support for sending new attributes from Radius Accounting packets via IPFIX. Additional fields that are added when this option is enabled are listed in the [[en:dpi:dpi_components:radius:radmon_acct_ipfix|template]]. 
    -dbg_log_mask=0x31+ 
     +Stream processing setup (it is recommended to use the values from the example): 
     +  * ''num_threads=1'' 
     +  * ''rx_bind_core=0'' 
     +  * ''services_bind_cores=0'' 
     +  * ''engine_bind_cores=0'' 
     +  * ''fifo_bind_cores=0'' 
     +  * ''snaplen=2000'' 
     +  * ''timeout_alarm=5'' 
     +  * ''dbg_log_mask=0x31'' 
     + 
     +Configuration of Radius Event Export: 
     +  * ''ipfix_dev=eno8'' 
     +  * ''ipfix_tcp_collectors=172.32.0.239:1502'' 
     + 
     +After changing the configuration, restart the service: 
     +<code> 
     +systemctl restart fastradius
     </code> </code>