diff options
author | Daniil Baturin <daniil@baturin.org> | 2019-09-19 03:02:46 +0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-09-19 03:02:46 +0700 |
commit | bf0a3006078255676abd109cb4b12f40fe35635a (patch) | |
tree | 2e6d663d5a47782d1825a3ed61ce0cd4f99f9985 /docs/routing/static.rst | |
parent | 3d08a03c5d1b0903e6bc40abe297e686ba6423d4 (diff) | |
parent | bf3eeb0ab548c88f79103e5b2cb88639648368df (diff) | |
download | vyos-documentation-bf0a3006078255676abd109cb4b12f40fe35635a.tar.gz vyos-documentation-bf0a3006078255676abd109cb4b12f40fe35635a.zip |
Merge pull request #113 from kroy-the-rabbit/master
Spelling, a few minor rewrites.
Diffstat (limited to 'docs/routing/static.rst')
-rw-r--r-- | docs/routing/static.rst | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/routing/static.rst b/docs/routing/static.rst index e1f96c31..4faa2451 100644 --- a/docs/routing/static.rst +++ b/docs/routing/static.rst @@ -13,11 +13,10 @@ 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, RFC 1918 private IP networks are set as blackhole routes. This -does not prevent networks within these segments from being used, since the -most specific route is always used. It does, however, prevent traffic to -unknown private networks from leaving the router. Commonly refereed to as -leaking. +example below, RFC1918_ 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. .. code-block:: sh @@ -27,3 +26,5 @@ leaking. .. note:: Routes with a distance of 255 are effectively disabled and not installed into the kernel. + +.. _RFC1918: https://tools.ietf.org/html/rfc1918 |