summaryrefslogtreecommitdiff
path: root/docs/configuration/firewall/flowtables.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/configuration/firewall/flowtables.rst')
-rw-r--r--docs/configuration/firewall/flowtables.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/configuration/firewall/flowtables.rst b/docs/configuration/firewall/flowtables.rst
index bc7b9212..ffd791f9 100644
--- a/docs/configuration/firewall/flowtables.rst
+++ b/docs/configuration/firewall/flowtables.rst
@@ -99,20 +99,20 @@ Creating rules for using flow tables:
Configuration Example
*********************
-Things to be considred in this setup:
+Things to be considered in this setup:
* Two interfaces are going to be used in the flowtables: eth0 and eth1
- * Minumum firewall ruleset is provided, which includes some filtering rules,
- and appropiate rules for using flowtable offload capabilities.
+ * Minimum firewall ruleset is provided, which includes some filtering rules,
+ and appropriate rules for using flowtable offload capabilities.
As described, first packet will be evaluated by all the firewall path, so
-desired connection should be explicitely accepted. Same thing should be taken
+desired connection should be explicitly accepted. Same thing should be taken
into account for traffic in reverse order. In most cases state policies are
used in order to accept connection in reverse patch.
-We will only accept traffic comming from interface eth0, protocol tcp and
-destination port 1122. All other traffic traspassing the router should be
+We will only accept traffic coming from interface eth0, protocol tcp and
+destination port 1122. All other traffic trespassing the router should be
blocked.
Commands