diff options
Diffstat (limited to 'docs/configuration/service')
| -rw-r--r-- | docs/configuration/service/conntrack-sync.rst | 14 | ||||
| -rw-r--r-- | docs/configuration/service/dhcp-relay.rst | 4 | ||||
| -rw-r--r-- | docs/configuration/service/snmp.rst | 2 |
3 files changed, 13 insertions, 7 deletions
diff --git a/docs/configuration/service/conntrack-sync.rst b/docs/configuration/service/conntrack-sync.rst index 27bc977d..2527407e 100644 --- a/docs/configuration/service/conntrack-sync.rst +++ b/docs/configuration/service/conntrack-sync.rst @@ -56,6 +56,8 @@ Configuration Protocol for which expect entries need to be synchronized. +.. stop_vyoslinter + .. cfgcmd:: set service conntrack-sync failover-mechanism vrrp sync-group <group> Failover mechanism to use for conntrack-sync. @@ -64,7 +66,10 @@ Configuration .. cfgcmd:: set service conntrack-sync ignore-address <x.x.x.x> - IP addresses or networks for which local conntrack entries will not be synced + IP addresses or networks for which local conntrack entries will not + be synced + +.. start_vyoslinter .. cfgcmd:: set service conntrack-sync interface <name> @@ -147,8 +152,9 @@ Operation .. note:: If the table is empty and you have a warning message, it means - conntrack is not enabled. To enable conntrack, just create a NAT or a firewall - rule. :cfgcmd:`set firewall state-policy established action accept` + conntrack is not enabled. To enable conntrack, just create a NAT + or a firewall rule. + :cfgcmd:`set firewall state-policy established action accept` .. opcmd:: show conntrack-sync cache external @@ -210,7 +216,7 @@ Example The next example is a simple configuration of conntrack-sync. -.. figure:: /_static/images/service_conntrack_sync-schema.png +.. figure:: /_static/images/service_conntrack_sync-schema.* :scale: 60 % :alt: Conntrack Sync Example diff --git a/docs/configuration/service/dhcp-relay.rst b/docs/configuration/service/dhcp-relay.rst index 632b2800..6a1b02f2 100644 --- a/docs/configuration/service/dhcp-relay.rst +++ b/docs/configuration/service/dhcp-relay.rst @@ -89,7 +89,7 @@ Example * Router receives DHCP client requests on ``eth1`` and relays them to the server at 10.0.1.4 on ``eth2``. -.. figure:: /_static/images/service_dhcp-relay01.png +.. figure:: /_static/images/service_dhcp-relay01.* :scale: 80 % :alt: DHCP relay example @@ -177,7 +177,7 @@ Example * Requests are forwarded through ``eth2`` as the `upstream interface` * External DHCPv6 server is at 2001:db8::4 -.. figure:: /_static/images/service_dhcpv6-relay01.png +.. figure:: /_static/images/service_dhcpv6-relay01.* :scale: 80 % :alt: DHCPv6 relay example diff --git a/docs/configuration/service/snmp.rst b/docs/configuration/service/snmp.rst index b444ab85..6dc13240 100644 --- a/docs/configuration/service/snmp.rst +++ b/docs/configuration/service/snmp.rst @@ -56,7 +56,7 @@ managed devices. NMSs provide the bulk of the processing and memory resources required for network management. One or more NMSs may exist on any managed network. -.. figure:: /_static/images/service_snmp_communication_principles_diagram.png +.. figure:: /_static/images/service_snmp_communication_principles_diagram.* :scale: 20 % :alt: Principle of SNMP Communication |