diff options
Diffstat (limited to 'docs/configuration')
| -rw-r--r-- | docs/configuration/nat/nat44.md | 4 | ||||
| -rw-r--r-- | docs/configuration/policy/route.md | 4 | ||||
| -rw-r--r-- | docs/configuration/protocols/bgp.md | 6 | ||||
| -rw-r--r-- | docs/configuration/protocols/ospf.md | 11 | ||||
| -rw-r--r-- | docs/configuration/protocols/traffic-engineering.md | 5 | ||||
| -rw-r--r-- | docs/configuration/service/console-server.md | 2 | ||||
| -rw-r--r-- | docs/configuration/service/router-advert.md | 2 | ||||
| -rw-r--r-- | docs/configuration/service/webproxy.md | 4 | ||||
| -rw-r--r-- | docs/configuration/system/conntrack.md | 2 |
9 files changed, 21 insertions, 19 deletions
diff --git a/docs/configuration/nat/nat44.md b/docs/configuration/nat/nat44.md index 8b02477e..2e877106 100644 --- a/docs/configuration/nat/nat44.md +++ b/docs/configuration/nat/nat44.md @@ -298,8 +298,8 @@ randomly. When defining the translated address, called `backends`, a `weight` must be configured. This lets the user define load balance distribution according -to their needs. Them sum of all the weights defined for the backends should -be equal to 100. In oder words, the weight defined for the backend is the +to their needs. The sum of all the weights defined for the backends should +be equal to 100. In other words, the weight defined for the backend is the percentage of the connections that will receive such backend. ```{cfgcmd} set nat [source | destination] rule \<rule\> load-balance hash [source-address | destination-address | source-port | destination-port | random] diff --git a/docs/configuration/policy/route.md b/docs/configuration/policy/route.md index b3ef6540..d2a6e8fa 100644 --- a/docs/configuration/policy/route.md +++ b/docs/configuration/policy/route.md @@ -201,7 +201,7 @@ about what type-name criteria are supported. ```{cfgcmd} set policy route6 \<name\> rule \<n\> ipsec \<match-ipsec|match-none\> -Set IPSec inbound match criterias, where: +Set IPSec inbound match criteria, where: * match-ipsec: match inbound IPsec packets. * match-none: match inbound non-IPsec packets. ``` @@ -270,7 +270,7 @@ Match based on packet type criteria. ```{cfgcmd} set policy route6 \<name\> rule \<n\> recent time \<1-4294967295\> Set parameters for matching recently seen sources. This match could be used -by seeting count (source address seen more than <1-255> times) and/or time +by setting count (source address seen more than <1-255> times) and/or time (source address seen in the last <0-4294967295> seconds). ``` diff --git a/docs/configuration/protocols/bgp.md b/docs/configuration/protocols/bgp.md index 702a2b1f..cfa79ce4 100644 --- a/docs/configuration/protocols/bgp.md +++ b/docs/configuration/protocols/bgp.md @@ -285,7 +285,7 @@ and happen automatically if local-role is set. ```{cfgcmd} set protocols bgp neighbor \<address|interface\> shutdown -This command disable the peer or peer group. To reenable the peer use +This command disables the peer or peer group. To re-enable the peer, use the delete form of this command. ``` @@ -805,7 +805,7 @@ availability is also advertised. A route that continually fails and returns requires a great deal of network traffic to update the network about the route's status. -Route dampening wich described in {rfc}`2439` enables you to identify routes +Route dampening, described in {rfc}`2439`, enables you to identify routes that repeatedly fail and return. If route dampening is enabled, an unstable route accumulates penalties each time the route fails and returns. If the accumulated penalties exceed a threshold, the route is no longer advertised. @@ -1016,7 +1016,7 @@ peer. The {cfgcmd}`receive` keyword configures a router to advertise ORF receive capabilities. The {cfgcmd}`send` keyword configures a router to advertise ORF send capabilities. To advertise a filter from a sender, you must create an IP prefix list for the specified BGP peer applied in inbound -derection. +direction. ``` diff --git a/docs/configuration/protocols/ospf.md b/docs/configuration/protocols/ospf.md index 72fefb84..b3297b3d 100644 --- a/docs/configuration/protocols/ospf.md +++ b/docs/configuration/protocols/ospf.md @@ -807,7 +807,7 @@ interface. ```{opcmd} show ip ospf interface [\<interface\>] -This command displays state and configuration of OSPF the specified +This command displays state and configuration of OSPF for the specified interface, or all interfaces if no interface is given. ``` @@ -1402,8 +1402,8 @@ This command displays the neighbor DR choice information. ``` ```{opcmd} show ipv6 ospfv3 interface [prefix]|[\<interface\> [prefix]] -This command displays state and configuration of OSPF the specified -interface, or all interfaces if no interface is given. Whith the argument +This command displays state and configuration of OSPF for the specified +interface, or all interfaces if no interface is given. With the argument {cfgcmd}`prefix` this command shows connected prefixes to advertise. ``` ```{opcmd} show ipv6 ospfv3 route @@ -1460,8 +1460,9 @@ set protocols ospfv3 redistribute connected show ipv6 ospfv3 redistribute ``` -Cost calculation wireguard interfaces is unreliable as ospfv3 uses the link speed to calculate the link cost. -You might therefore want to set the link cost to a fixed value on WireGuard tunnels. +Cost calculation for WireGuard interfaces is unreliable as ospfv3 uses the +link speed to calculate the link cost. You might therefore want to set the +link cost to a fixed value on WireGuard tunnels. Example configuration for WireGuard interfaces: diff --git a/docs/configuration/protocols/traffic-engineering.md b/docs/configuration/protocols/traffic-engineering.md index 832023a7..fc0841c7 100644 --- a/docs/configuration/protocols/traffic-engineering.md +++ b/docs/configuration/protocols/traffic-engineering.md @@ -7,11 +7,12 @@ alternative path. ## Common link parameters -Traffic Engineering parameters are used for both IS-IS and OSPF (not supported yet). +Traffic Engineering parameters are used for both IS-IS and OSPF (not supported +yet). ```{cfgcmd} set protocols traffic-engineering admin-group \<admin-group-name\> bit-position \<bit-position-value\> -Create Administrative group and assosiate bit position with it. These groups can be +Create Administrative group and associate bit position with it. These groups can be used in the following commands. \<bit-position-value\> can have value 0-31. There cannot be two groups with same bit position. diff --git a/docs/configuration/service/console-server.md b/docs/configuration/service/console-server.md index f0556652..4e0ec575 100644 --- a/docs/configuration/service/console-server.md +++ b/docs/configuration/service/console-server.md @@ -60,7 +60,7 @@ left unconfigured. :::{note} USB to serial converters will handle most of their work in software -so you should be carefull with the selected baudrate as some times they +so you should be careful with the selected baudrate as sometimes they can't cope with the expected speed. ::: ``` diff --git a/docs/configuration/service/router-advert.md b/docs/configuration/service/router-advert.md index 10753105..b81dddc7 100644 --- a/docs/configuration/service/router-advert.md +++ b/docs/configuration/service/router-advert.md @@ -108,7 +108,7 @@ Router Advertisements unless this option is set. ## Example Your LAN connected on eth0 uses prefix `2001:db8:beef:2::/64` with the router -beeing `2001:db8:beef:2::1` +being `2001:db8:beef:2::1` ```none set interfaces ethernet eth0 address 2001:db8:beef:2::1/64 diff --git a/docs/configuration/service/webproxy.md b/docs/configuration/service/webproxy.md index 28156b2b..0a21bed1 100644 --- a/docs/configuration/service/webproxy.md +++ b/docs/configuration/service/webproxy.md @@ -317,7 +317,7 @@ Defaults to 'uid' :::{note} This can only be done if all your users are located directly under the same position in the LDAP tree and the login name is used for naming -each user object. If your LDAP tree does not match these criterias or if you +each user object. If your LDAP tree does not match these criteria or if you want to filter who are valid users then you need to use a search filter to search for your users DN (filter-expression). ::: @@ -369,7 +369,7 @@ Download/Update complete blacklist vyos@vyos:~$ update webproxy blacklists Warning: No url-filtering blacklist installed Would you like to download a default blacklist? [confirm][y] -Connecting to ftp.univ-tlse1.fr (193.49.48.249:21) +Connecting to ftp.example.com (192.0.2.249:21) blacklists.gz 100% |*************************************************************************************************************| 17.0M 0:00:00 ETA Uncompressing blacklist... Checking permissions... diff --git a/docs/configuration/system/conntrack.md b/docs/configuration/system/conntrack.md index 2b7279f6..e27e2187 100644 --- a/docs/configuration/system/conntrack.md +++ b/docs/configuration/system/conntrack.md @@ -175,7 +175,7 @@ the future the conntrack ignore rules will be removed. .. cfgcmd:: set system conntrack ignore [ipv4 | ipv6] rule <1-999999> tcp flags [not] <text> - Allowed values fpr TCP flags: ``ack``, ``cwr``, ``ecn``, ``fin``, ``psh``, + Allowed values for TCP flags: ``ack``, ``cwr``, ``ecn``, ``fin``, ``psh``, ``rst``, ``syn`` and ``urg``. Multiple values are supported, and for inverted selection use ``not``, as shown in the example. ``` |
