Differences
This shows you the differences between two versions of the page.
| en:dpi:dpi_components:radius:radius_inst_spec [2018/03/19 12:16] – created lexx26 | en:dpi:dpi_components:radius:radius_inst_spec [2024/09/26 15:29] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== Operation peculiarities in different connection modes ====== |
| + | {{indexmenu_n> | ||
| + | Radius events monitor supports 3 modes of its connection into the operator' | ||
| + | |||
| + | ===== The traffic passes through the Radius server ===== | ||
| + | Radius events monitor is connected into the line between the access equipment and Radius server. | ||
| + | |||
| + | An additional DNA network interface is required to transmit Radius server interaction traffic. The configuration parameter to define this interface must be set in the configuration file / | ||
| + | < | ||
| + | out_dev=dna1 | ||
| + | </ | ||
| + | |||
| + | ===== Listening to the mirrored traffic ===== | ||
| + | Radius events monitor receives the mirrored traffic of interaction with Radius server. | ||
| + | |||
| + | in_dev interface is sufficient in this case: | ||
| + | < | ||
| + | in_dev=dna0 | ||
| + | </ | ||
| + | |||
| + | ===== Redundant Radius server emulation ===== | ||
| + | Radius events monitor emulates the redundant Radius server. | ||
| + | |||
| + | To support operation in this mode, it has to reply queries of the main Radius server by valid Radius replies. Also, it has to emulate the network interface on which the " | ||
| + | |||
| + | The following configuration parameters must be specified to support this mode: | ||
| + | < | ||
| + | #Enable emulation mode | ||
| + | rad_server_emulation=1 | ||
| + | #Set IP and MAC of the emulated network interface | ||
| + | rad_virtual_eth=172.17.69.10/ | ||
| + | #Indicate secret to form Radius replies | ||
| + | rad_secret=mysecretkey | ||
| + | </ | ||