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

Replace all occurances of 'Note:' with 'NOTE:'

Browse Source
This commit is contained in:
Christian Poessinger 2018-10-03 15:02:24 +02:00
parent 1417911523
commit 2022dd397e
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ch01-install.rst
View File

@ -28,7 +28,7 @@ version if something breaks after upgrade. Every version is contained in its
own squashfs image that is mounted in a union filesystem together with a own squashfs image that is mounted in a union filesystem together with a
directory for mutable data (configs etc.). directory for mutable data (configs etc.).
**Note:** older versions used to support non-image installation (`install **NOTE:** older versions used to support non-image installation (`install
system` command). It's been deprecated since the time image installation was system` command). It's been deprecated since the time image installation was
introduced (long before the fork), and does not provide any version management introduced (long before the fork), and does not provide any version management
capabilities. You **should not** use it for new installations even if it's still capabilities. You **should not** use it for new installations even if it's still

4
docs/ch08-nat.rst
View File

@ -57,7 +57,7 @@ rule [n] translation address` statement.
set nat source rule 100 translation address '203.0.113.32-203.0.113.63' set nat source rule 100 translation address '203.0.113.32-203.0.113.63'
**Note:** Avoiding "leaky" NAT **NOTE:** Avoiding "leaky" NAT
Linux netfilter will not NAT traffic marked as INVALID. This often confuses Linux netfilter will not NAT traffic marked as INVALID. This often confuses
people into thinking that Linux (or specifically VyOS) has a broken NAT people into thinking that Linux (or specifically VyOS) has a broken NAT
@ -82,7 +82,7 @@ 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, instead allowing the operator to make the determination on how the
traffic is handled. traffic is handled.
**Note:** Avoiding NAT breakage in the absence of split-DNS **NOTE:** Avoiding NAT breakage in the absence of split-DNS
A typical problem with using NAT and hosting public servers is the ability for A typical problem with using NAT and hosting public servers is the ability for
internal systems to reach an internal server using it's external IP address. internal systems to reach an internal server using it's external IP address.