====== Operation peculiarities in different connection modes ======
{{indexmenu_n>5}}
Radius events monitor supports 3 modes of its connection into the operator's network:

===== 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 /etc/dpi/fdpi_radius.conf:
<code>
out_dev=dna1
</code>

===== 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:
<code>
in_dev=dna0
</code>

===== 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 "redundant" Radius server listens.

The following configuration parameters must be specified to support this mode:
<code>
#Enable emulation mode
rad_server_emulation=1
#Set IP and MAC of the emulated network interface
rad_virtual_eth=172.17.69.10/D4:AE:52:C1:A7:29
#Indicate secret to form Radius replies
rad_secret=mysecretkey
</code>