</listitem>
</varlistentry>
+ <varlistentry>
+ <term><literal>radius_bind_min</literal> (short)</term>
+ <term><literal>radius_bind_max</literal> (short)</term>
+ <listitem>
+ <para>
+ Define a port range in which to bind sockets used to
+ send and receive RADIUS packets. Must be at least
+ RADIUS_FDS (64) wide. Simplifies firewalling of RADIUS
+ ports (default: dynamically assigned).
+ </para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term><literal>radius_dae_port</literal> (short)</term>
<listitem>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><literal>cluster_port</literal> (udp port)</term>
+ <listitem>
+ <para>
+ UDP cluster port (default: 32792).
+ See <xref linkend="clustering"/> for more information.
+ </para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term><literal>cluster_interface</literal> (string)</term>
<listitem>
<para>
An <command>l2tpns</command> cluster consists of one* or more
servers configured with the same configuration, notably the
- multicast <literal>cluster_address</literal>.
+ multicast <literal>cluster_address</literal> and the
+ <literal>cluster_port</literal>
</para>
<para>*A stand-alone server is simply a degraded cluster.</para>
Initially servers come up as cluster slaves, and periodically
(every <literal>cluster_hb_interval</literal>/10 seconds) send
out ping packets containing the start time of the process to the
- multicast <literal>cluster_address</literal>.
+ multicast <literal>cluster_address</literal> on
+ <literal>cluster_port</literal>.
</para>
<para>
</para>
<para>*Configurable with <literal>cluster_master_min_adv</literal></para>
+
+ <para>
+ Multiple clusters can be run on the same network by just using different
+ multicast <literal>cluster_address</literal>. However, for a given host to
+ be part of multiple clusters without mixing the clusters,
+ <literal>cluster_port</literal> must be different for each cluster.
+ </para>
</sect1>
<sect1 id="routing">