summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Poessinger <christian@poessinger.com>2018-10-03 09:35:52 +0200
committerChristian Poessinger <christian@poessinger.com>2018-10-03 09:35:52 +0200
commit676003ffbdf1f26b667f2ab9490a2390076191e3 (patch)
tree638a785d10604b03b28f00748d28db8d7d1d0e4d
parent48550a8aa379ba66f454bc22c9122f6e0472d9de (diff)
downloadvyos-documentation-676003ffbdf1f26b667f2ab9490a2390076191e3.tar.gz
vyos-documentation-676003ffbdf1f26b667f2ab9490a2390076191e3.zip
NAT: use code-block formatting rather then bold for 'set nat foo'
-rw-r--r--docs/ch08-nat.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/ch08-nat.rst b/docs/ch08-nat.rst
index 4c7110a0..0266137b 100644
--- a/docs/ch08-nat.rst
+++ b/docs/ch08-nat.rst
@@ -50,8 +50,8 @@ reserving an average of 200-300 sessions per host system.
Example: For an ~8,000 host network a source NAT pool of 32 IP addresses is
recommended.
-A pool of addresses can be defined by using a **-** in the **set nat source
-rule [n] translation address** statement.
+A pool of addresses can be defined by using a **-** in the `set nat source
+rule [n] translation address` statement.
.. code-block:: sh
@@ -176,8 +176,8 @@ Which would generate the following NAT destination configuration:
}
Note that if forwarding traffic to a different port than it is arriving on,
-you may also configure the translation port using **set nat destination rule
-[n] translation port**.
+you may also configure the translation port using `set nat destination rule
+[n] translation port`.
This establishes our Port Forward rule, but if we created a firewall policy it
will likely block the traffic.