diff options
| author | Christian Poessinger <christian@poessinger.com> | 2020-01-04 16:20:22 +0100 |
|---|---|---|
| committer | Christian Poessinger <christian@poessinger.com> | 2020-01-04 16:25:54 +0100 |
| commit | 811129e2e37dbc9632f1341bfafe7e78b2f68088 (patch) | |
| tree | d237bc2b8e048ea9efe4c29ffd7874345f6ab0c9 | |
| parent | 389f5fb8e5e4824e6f6be144d08f537540d8b1dc (diff) | |
| download | vyos-documentation-811129e2e37dbc9632f1341bfafe7e78b2f68088.tar.gz vyos-documentation-811129e2e37dbc9632f1341bfafe7e78b2f68088.zip | |
dhcp: use proper indent on description inside failover section
| -rw-r--r-- | docs/services/dhcp.rst | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/services/dhcp.rst b/docs/services/dhcp.rst index 166f24a8..2b139b10 100644 --- a/docs/services/dhcp.rst +++ b/docs/services/dhcp.rst @@ -83,24 +83,24 @@ explicitly by the following statements. A generic `<name>` referencing this sync service. -.. note:: `<name>` must be identical on both sides! + .. note:: `<name>` must be identical on both sides! .. cfgcmd:: set service dhcp-server shared-network-name <name> subnet <subnet> failover status <primary | secondary> The primary and secondary statements determines whether the server is primary or secondary. -.. note:: In order for the primary and the secondary DHCP server to keep - their lease tables in sync, they must be able to reach each other on TCP - port 647. If you have firewall rules in effect, adjust them accordingly. - -.. hint:: The dialogue between failover partners is neither encrypted nor - authenticated. Since most DHCP servers exist within an organisation's own - secure Intranet, this would be an unnecessary overhead. However, if you have - DHCP failover peers whose communications traverse insecure networks, then we - recommend that you consider the use of VPN tunneling between them to ensure - that the failover partnership is immune to disruption (accidental or - otherwise) via third parties. + .. note:: In order for the primary and the secondary DHCP server to keep + their lease tables in sync, they must be able to reach each other on TCP + port 647. If you have firewall rules in effect, adjust them accordingly. + + .. hint:: The dialogue between failover partners is neither encrypted nor + authenticated. Since most DHCP servers exist within an organisation's own + secure Intranet, this would be an unnecessary overhead. However, if you have + DHCP failover peers whose communications traverse insecure networks, then we + recommend that you consider the use of VPN tunneling between them to ensure + that the failover partnership is immune to disruption (accidental or + otherwise) via third parties. Example ^^^^^^^ |