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/routing/static.rst | |
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/routing/static.rst')
-rw-r--r-- | docs/routing/static.rst | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/routing/static.rst b/docs/routing/static.rst index 4faa2451..b2c7833a 100644 --- a/docs/routing/static.rst +++ b/docs/routing/static.rst @@ -13,7 +13,7 @@ not make use of DHCP or dynamic routing protocols: set protocols static route 0.0.0.0/0 next-hop 10.1.1.1 distance '1' Another common use of static routes is to blackhole (drop) traffic. In the -example below, RFC1918_ networks are set as blackhole routes. +example below, :rfc:`1918` networks are set as blackhole routes. This prevents these networks leaking out public interfaces, but it does not prevent them from being used as the most specific route has the highest priority. @@ -26,5 +26,3 @@ them from being used as the most specific route has the highest priority. .. note:: Routes with a distance of 255 are effectively disabled and not installed into the kernel. - -.. _RFC1918: https://tools.ietf.org/html/rfc1918 |