diff options
| author | Daniil Baturin <daniil@baturin.org> | 2019-09-18 01:22:12 +0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-09-18 01:22:12 +0700 |
| commit | 7facf991a64e6e95281b5538e804eb0339be2a34 (patch) | |
| tree | cccf6d5e9f601da49af1c8aaf0353694619d5d11 /docs/nat.rst | |
| parent | 6ae968116ca045551133b1623788f917ce20b1b2 (diff) | |
| parent | bc8a28ccbdff599eb1f7de12b5cf7f824eef49d3 (diff) | |
| download | vyos-documentation-7facf991a64e6e95281b5538e804eb0339be2a34.tar.gz vyos-documentation-7facf991a64e6e95281b5538e804eb0339be2a34.zip | |
Merge pull request #108 from kroy-the-rabbit/master
Text/spelling fixes, adding additional navigation headers
Diffstat (limited to 'docs/nat.rst')
| -rw-r--r-- | docs/nat.rst | 11 |
1 files changed, 8 insertions, 3 deletions
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 |