1 # Replicate packet(s) to a home server.
3 # This module will open a new socket for each packet, and "clone"
4 # the incoming packet to the destination realm (i.e. home server).
6 # Use it by setting "Replicate-To-Realm = name" in the control list,
7 # just like Proxy-To-Realm. The configurations for the two attributes
8 # are identical. The realm must exist, the home_server_pool must exist,
9 # and the home_server must exist.
11 # The only difference is that the "replicate" module sends requests
12 # and does not expect a reply. Any reply is ignored.
14 # Both Replicate-To-Realm and Proxy-To-Realm can be used at the same time.
16 # To use this module, list "replicate" in the "authorize" or
17 # "accounting" section. Then, ensure that Replicate-To-Realm is set.
18 # The contents of the "packet" attribute list will be sent to the
19 # home server. The usual load-balancing, etc. features of the home
20 # server will be used.
22 # "radmin" can be used to mark home servers alive/dead, in order to
23 # enable/disable replication to specific servers.
25 # Packets can be replicated to multiple destinations. Just set
26 # Replicate-To-Realm multiple times. One packet will be sent for
27 # each of the Replicate-To-Realm attribute in the "control" list.
29 # If no packets are sent, the module returns "noop". If at least one
30 # packet is sent, the module returns "ok". If an error occurs, the
31 # module returns "fail"
33 # Note that replication does NOT change any of the packet statistics.
34 # If you use "radmin" to look at the statistics for a home server,
35 # the replicated packets will cause NO counters to increment. This
36 # is not a bug, this is how replication works.