Configuration [Документация VAS Experts]

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:start [2020/06/10 13:19] – [Example 1] edrudichgmailcomen:dpi:dpi_components:radius:radius_config:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
Line 1: Line 1:
-====== 3 Configuration ====== 
-{{indexmenu_n>3}} 
-Radius events monitor is configured by the file /etc/dpi/fdpi_radius.conf. 
  
-===== Configuring network interfaces to use: ===== 
-The interfaces available for configuring have names in format dna<digit>. 
- 
-==== Example 1 ====  
-The complete configuration file: 
-<code> 
-# FastDPI RADIUS configuration parameters 
-# 
-in_dev=dna0 
-#out_dev=dna1 - the name of the output interface if Monitor runs in pass through mode 
-#rad_server_emulation=1 - enable emulation of back up Radius server 
-#rad_virtual_eth=172.17.69.10/D4:AE:52:C1:A7:29 - enable emulation of a network card 
-#rad_secret=mysecretkey - secret value to generate replies in Radius server emulation mode 
-#rad_prefix_info=1 - append regional prefixes to subscribers' names (LOGIN) 
- 
-rad_acct_port=1646 - port number (or several ports divided by a comma) to listen to Radius Accounting packets 
-#rad_auth_port=1645 - port number (or several ports divided by a comma) to listen to Radius Authentication packets 
-#rad_save_pdu=1 - store bad PDU in pcap format for analysis 
-rad_check_code_pdu=2:4 - check PDU with codes 2 and 3 
-rad_check_acct_status_type=1:3 - check PDU having status 1 and 3 
- 
-mem_preset=1 - initialize memory upon start 
- 
-# 
-# fdpi_servers The list of DPI servers in the cluster 
-# 
-fdpi_servers=123.45.67.83:29000,123.45.67.85:29000 
-</code> 
- 
-Please check [[en:dpi:dpi_components:radius:radius_admin:start|administration]] chapter as well.