diff options
| author | Christian Poessinger <christian@poessinger.com> | 2019-11-17 20:20:16 +0100 |
|---|---|---|
| committer | Christian Poessinger <christian@poessinger.com> | 2019-11-17 20:20:16 +0100 |
| commit | 73edff0a21f8486a2c416537b72dda60c1885462 (patch) | |
| tree | f94a3e0a545abfe2628cc82255790ddd7c4e5b77 /docs/services | |
| parent | 4e3fd8b583b17eb1a83681e35bea72b414d30b2e (diff) | |
| download | vyos-documentation-73edff0a21f8486a2c416537b72dda60c1885462.tar.gz vyos-documentation-73edff0a21f8486a2c416537b72dda60c1885462.zip | |
Replace all RFC links with proper :rfc: syntax
Diffstat (limited to 'docs/services')
| -rw-r--r-- | docs/services/dynamic-dns.rst | 5 | ||||
| -rw-r--r-- | docs/services/lldp.rst | 2 | ||||
| -rw-r--r-- | docs/services/references.rst | 1 |
3 files changed, 3 insertions, 5 deletions
diff --git a/docs/services/dynamic-dns.rst b/docs/services/dynamic-dns.rst index 67de6471..0a9900ed 100644 --- a/docs/services/dynamic-dns.rst +++ b/docs/services/dynamic-dns.rst @@ -6,7 +6,7 @@ address. In order to do so, VyOS includes ddclient_, a perl script written for this exact purpose. ddclient_ uses two methods to update a DNS record. The first one will send -updates directly to the DNS daemon, in compliance with RFC2136_. The second +updates directly to the DNS daemon, in compliance with :rfc:`2136`. The second one involves a third party service, like DynDNS.com or any other similar website. This method uses HTTP requests to transmit the new IP address. You can configure both in VyOS. @@ -14,7 +14,7 @@ can configure both in VyOS. VyOS CLI and RFC2136 ^^^^^^^^^^^^^^^^^^^^ -First, create an RFC2136_ config node : +First, create an :rfc:`2136` config node : .. code-block:: sh @@ -148,5 +148,4 @@ ddclient_ will load the webpage at `[url]` and will try to extract an IP address for the response. ddclient_ will skip any address located before the string set in `[skip]`. - .. include:: references.rst diff --git a/docs/services/lldp.rst b/docs/services/lldp.rst index 37214506..3f22af08 100644 --- a/docs/services/lldp.rst +++ b/docs/services/lldp.rst @@ -17,7 +17,7 @@ Information gathered Information gathered with LLDP is stored in the device as a management information database (MIB_) and can be queried with the Simple Network -Management Protocol (SNMP_) as specified in RFC 2922. The topology of an +Management Protocol (SNMP_) as specified in :rfc:`2922`. The topology of an LLDP-enabled network can be discovered by crawling the hosts and querying this database. Information that may be retrieved include: diff --git a/docs/services/references.rst b/docs/services/references.rst index 257ffe11..408d5288 100644 --- a/docs/services/references.rst +++ b/docs/services/references.rst @@ -2,7 +2,6 @@ .. _ddclient: http://sourceforge.net/p/ddclient/wiki/Home/ .. _`Foundry Discovery Protocol`: https://en.wikipedia.org/wiki/Foundry_Discovery_Protocol .. _MIB: https://en.wikipedia.org/wiki/Management_information_base -.. _RFC2136: https://www.ietf.org/rfc/rfc2136.txt .. _SNMP: https://en.wikipedia.org/wiki/Simple_Network_Management_Protocol .. _SNMPv2: https://en.wikipedia.org/wiki/Simple_Network_Management_Protocol#Version_2 .. _SNMPv3: https://en.wikipedia.org/wiki/Simple_Network_Management_Protocol#Version_3 |