summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkroy <kroy@kroy.io>2019-09-17 11:34:26 -0500
committerkroy <kroy@kroy.io>2019-09-17 11:34:26 -0500
commitbc8a28ccbdff599eb1f7de12b5cf7f824eef49d3 (patch)
treecccf6d5e9f601da49af1c8aaf0353694619d5d11
parent6ae968116ca045551133b1623788f917ce20b1b2 (diff)
downloadvyos-documentation-bc8a28ccbdff599eb1f7de12b5cf7f824eef49d3.tar.gz
vyos-documentation-bc8a28ccbdff599eb1f7de12b5cf7f824eef49d3.zip
Text/spelling fixes, adding additional navigation headers
-rw-r--r--docs/appendix/examples/index.rst1
-rw-r--r--docs/nat.rst11
-rw-r--r--docs/vpn/wireguard.rst8
3 files changed, 13 insertions, 7 deletions
diff --git a/docs/appendix/examples/index.rst b/docs/appendix/examples/index.rst
index f9689851..0f4ba595 100644
--- a/docs/appendix/examples/index.rst
+++ b/docs/appendix/examples/index.rst
@@ -15,3 +15,4 @@ This chapter contains various configuration Examples
ospf-unnumbered
azure-vpn-bgp
azure-vpn-dual-bgp
+ tunnelbroker-ipv6
diff --git a/docs/nat.rst b/docs/nat.rst
index 5c3dadc4..d20995d4 100644
--- a/docs/nat.rst
+++ b/docs/nat.rst
@@ -87,6 +87,9 @@ protocol behavior. For this reason, VyOS does not globally drop invalid state
traffic, instead allowing the operator to make the determination on how the
traffic is handled.
+NAT Reflection/Hairpin NAT
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
.. note:: Avoiding NAT breakage in the absence of split-DNS
A typical problem with using NAT and hosting public servers is the ability for
@@ -96,7 +99,7 @@ systems to the internal address when requests are made internally. Because
many smaller networks lack DNS infrastructure, a work-around is commonly
deployed to facilitate the traffic by NATing the request from internal hosts
to the source address of the internal interface on the firewall. This technique
-is commonly reffered to as **NAT Reflection**, or **Hairpin NAT**.
+is commonly referred to as **NAT Reflection**, or **Hairpin NAT**.
In this example, we will be using the example Quick Start configuration above
as a starting point.
@@ -272,8 +275,10 @@ described in RFC6296_. NPTv6 is supported in linux kernel since version 3.13.
Usage
^^^^^
-NPTv6 is very useful for IPv6 multihoming. Let's assume the following network
-configuration:
+NPTv6 is very useful for IPv6 multihoming. It is also commonly used when the external IPv6 prefix is dynamic,
+as it prevents the need for renumbering of internal hosts when the extern prefix changes.
+
+Let's assume the following network configuration:
* eth0 : LAN
* eth1 : WAN1, with 2001:db8:e1::/48 routed towards it
diff --git a/docs/vpn/wireguard.rst b/docs/vpn/wireguard.rst
index 955c2d40..a2f45913 100644
--- a/docs/vpn/wireguard.rst
+++ b/docs/vpn/wireguard.rst
@@ -131,9 +131,9 @@ asymmetric crypto, which is optional.
wg01# run generate wireguard preshared-key
rvVDOoc2IYEnV+k5p7TNAmHBMEGTHbPU8Qqg8c/sUqc=
-Copy the key, it is not stored on the local file system. Make sure you
-distribute that key in a safe manner, it's a symmatric key, so only you and
-your peer should have knowledge if its content.
+Copy the key, as it is not stored on the local file system. Make sure you
+distribute that key in a safe manner, it's a symmetric key, so only you and
+your peer should have knowledge of its content.
.. code-block:: sh
@@ -141,7 +141,7 @@ your peer should have knowledge if its content.
wg02# set interfaces wireguard wg01 peer to-wg01 preshared-key 'rvVDOoc2IYEnV+k5p7TNAmHBMEGTHbPU8Qqg8c/sUqc='
Operational commands
-~~~~~~~~~~~~~~~~~~~~
+^^^^^^^^^^^^^^^^^^^^
**Show interface status**