vyos/vyos-documentation
1
0
Fork 0
mirror of https://github.com/vyos/vyos-documentation.git synced 2025-10-26 08:41:46 +01:00
Code Issues Packages Projects Releases Wiki Activity

Text/spelling fixes, adding additional navigation headers

Browse Source
This commit is contained in:
kroy 2019-09-17 11:34:26 -05:00
parent 6ae968116c
commit bc8a28ccbd
3 changed files with 13 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/appendix/examples/index.rst
View File

@ -15,3 +15,4 @@ This chapter contains various configuration Examples
ospf-unnumbered
azure-vpn-bgp
azure-vpn-dual-bgp
tunnelbroker-ipv6

11
docs/nat.rst
View File

@ -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

8
docs/vpn/wireguard.rst
View File

@ -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**