summaryrefslogtreecommitdiff
path: root/docs/routing/static.rst
diff options
context:
space:
mode:
authorChristian Poessinger <christian@poessinger.com>2019-06-20 12:12:23 +0200
committerChristian Poessinger <christian@poessinger.com>2019-06-20 12:47:56 +0200
commit41d2d62e6948f0978f09b7350b1897168efec9f2 (patch)
tree3fb5f4760f083d7db86eb50dc18457d18b032bc5 /docs/routing/static.rst
parent57e4b8d6641a4cba327e5da55b3df06ef9060f2c (diff)
downloadvyos-documentation-41d2d62e6948f0978f09b7350b1897168efec9f2.tar.gz
vyos-documentation-41d2d62e6948f0978f09b7350b1897168efec9f2.zip
routing: split routing protocols into individual files
Diffstat (limited to 'docs/routing/static.rst')
-rw-r--r--docs/routing/static.rst29
1 files changed, 29 insertions, 0 deletions
diff --git a/docs/routing/static.rst b/docs/routing/static.rst
new file mode 100644
index 00000000..e1f96c31
--- /dev/null
+++ b/docs/routing/static.rst
@@ -0,0 +1,29 @@
+.. _routing-static:
+
+Static
+------
+
+Static routes are manually configured network routes.
+
+A typical use for a static route is a static default route for systems that do
+not make use of DHCP or dynamic routing protocols:
+
+.. code-block:: sh
+
+ 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.
+
+.. code-block:: sh
+
+ set protocols static route 10.0.0.0/8 blackhole distance '254'
+ set protocols static route 172.16.0.0/12 blackhole distance '254'
+ set protocols static route 192.168.0.0/16 blackhole distance '254'
+
+.. note:: Routes with a distance of 255 are effectively disabled and not
+ installed into the kernel.