diff options
Diffstat (limited to 'docs/configexamples')
| -rw-r--r-- | docs/configexamples/ha.rst | 2 | ||||
| -rw-r--r-- | docs/configexamples/wan-load-balancing.rst | 8 |
2 files changed, 10 insertions, 0 deletions
diff --git a/docs/configexamples/ha.rst b/docs/configexamples/ha.rst index aa184d09..401d7b9f 100644 --- a/docs/configexamples/ha.rst +++ b/docs/configexamples/ha.rst @@ -332,6 +332,8 @@ hardware router. set service conntrack-sync mcast-group '224.0.0.50' set service conntrack-sync sync-queue-size '8' +.. _ha:contracktesting: + Testing ------- diff --git a/docs/configexamples/wan-load-balancing.rst b/docs/configexamples/wan-load-balancing.rst index f26f3ce6..cd150121 100644 --- a/docs/configexamples/wan-load-balancing.rst +++ b/docs/configexamples/wan-load-balancing.rst @@ -67,6 +67,9 @@ Example 2: Failover based on interface weights This examples uses the failover mode. + +.. _wan:example2_overwiew: + Overview ^^^^^^^^ In this example eth0 is the primary interface and eth1 is the secondary @@ -94,6 +97,8 @@ The previous example used the failover command to send traffic thorugh eth1 if eth0 fails. In this example failover functionality is provided by rule order. +.. _wan:example3_overwiew: + Overview ^^^^^^^^ Two rules will be created, the first rule directs traffic coming in @@ -122,6 +127,9 @@ secondary link has a lower speed and should only carry high priority traffic. It is assumed for this example that eth1 is connected to a slower connection than eth0 and should prioritise VoIP traffic. + +.. _wan:example4_overwiew: + Overview ^^^^^^^^ A rule order for prioritising traffic is useful in scenarios where the |