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/vpn | |
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/vpn')
-rw-r--r-- | docs/vpn/dmvpn.rst | 11 | ||||
-rw-r--r-- | docs/vpn/references.rst | 3 | ||||
-rw-r--r-- | docs/vpn/site2site_ipsec.rst | 7 |
3 files changed, 6 insertions, 15 deletions
diff --git a/docs/vpn/dmvpn.rst b/docs/vpn/dmvpn.rst index e53a013a..03bc48ed 100644 --- a/docs/vpn/dmvpn.rst +++ b/docs/vpn/dmvpn.rst @@ -9,9 +9,9 @@ DMVPN is a dynamic VPN technology originally developed by Cisco. While their implementation was somewhat proprietary, the underlying technologies are actually standards based. The three technologies are: -* **NHRP** - NBMA Next Hop Resolution Protocol RFC2332_ -* **mGRE** - Multipoint Generic Routing Encapsulation / mGRE RFC1702_ -* **IPSec** - IP Security (too many RFCs to list, but start with RFC4301_) +* **NHRP** - NBMA Next Hop Resolution Protocol :rfc:`2332` +* **mGRE** - Multipoint Generic Routing Encapsulation / mGRE :rfc:`1702` +* **IPSec** - IP Security (too many RFCs to list, but start with :rfc:`4301`) NHRP provides the dynamic tunnel endpoint discovery mechanism (endpoint registration, and endpoint discovery/lookup), mGRE provides the tunnel @@ -413,8 +413,3 @@ SPOKE2 Example Configuration set protocols static route 192.168.1.0/24 next-hop 10.0.0.1 set protocols static route 192.168.2.0/24 next-hop 10.0.0.2 - - -.. _RFC2332: https://tools.ietf.org/html/rfc2332 -.. _RFC1702: https://tools.ietf.org/html/rfc1702 -.. _RFC4301: https://tools.ietf.org/html/rfc4301 diff --git a/docs/vpn/references.rst b/docs/vpn/references.rst index 49b65cb0..be3d5921 100644 --- a/docs/vpn/references.rst +++ b/docs/vpn/references.rst @@ -4,7 +4,4 @@ .. _RADIUS: https://en.wikipedia.org/wiki/RADIUS .. _FreeRADIUS: https://freeradius.org .. _`Network Policy Server`: https://en.wikipedia.org/wiki/Network_Policy_Server -.. _RFC2332: https://tools.ietf.org/html/rfc2332 -.. _RFC1702: https://tools.ietf.org/html/rfc1702 -.. _RFC4301: https://tools.ietf.org/html/rfc4301 .. _PPTP: https://en.wikipedia.org/wiki/Point-to-Point_Tunneling_Protocol diff --git a/docs/vpn/site2site_ipsec.rst b/docs/vpn/site2site_ipsec.rst index ac410d52..8e0f257b 100644 --- a/docs/vpn/site2site_ipsec.rst +++ b/docs/vpn/site2site_ipsec.rst @@ -225,8 +225,9 @@ Imagine the following topology IPSec IKEv2 site2site VPN (source ./draw.io/vpn_s2s_ikev2.drawio) -.. note:: Don't get confused about the used /31 tunnel subnet. RFC3031_ gives - you additional information for using /31 subnets on point-to-point links. +.. note:: Don't get confused about the used /31 tunnel subnet. :rfc:`3031` + gives you additional information for using /31 subnets on point-to-point + links. **left** @@ -295,5 +296,3 @@ Imagine the following topology set vpn ipsec site-to-site peer 172.18.201.10 local-address '172.18.202.10' set vpn ipsec site-to-site peer 172.18.201.10 vti bind 'vti10' set vpn ipsec site-to-site peer 172.18.201.10 vti esp-group 'ESP_DEFAULT' - -.. _RFC3031: https://tools.ietf.org/html/rfc3021 |