Skip to content

Commit 09ca4d5

Browse files
authored
Minor changes.
1 parent b36a05a commit 09ca4d5

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

Documentation/services/pcn-firewall/firewall.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
Firewall
22
========
33

4-
This service is a transparent firewall, it can be attached to a port or a netdev, and it may drop or forward each packet that matches one of the defined rules, based on the source and destination IPv4 addresses, level 4 protocol and ports, and TCP flags.
5-
Policy rules can include one or more of the above fields; if a given field is missing, its content is influent for the matching.
6-
*Packets that are not ip are forwarded without any check*.
4+
This service implements a transparent firewall. It can be attached to a port or a netdev, and it may drop or forward each packet that matches one of the defined rules, based on the source and destination IPv4 addresses, level 4 protocol and ports, and TCP flags.
5+
Policy rules can include one or more of the above fields; if a given field is missing, its content does not influence the matching.
6+
*Non-IP packets are forwarded without any check*.
77

88
Features
99
--------
@@ -20,7 +20,7 @@ Supported features:
2020
- ``Forward`` packet from the interface from which it was received to the other
2121
- ``Drop`` packet
2222

23-
- Not IP packets are forwarded by default.
23+
- Non-IP packets are forwarded by default.
2424
- Up to 5k rules for each chain (INGRESS/EGRESS).
2525

2626
How to use
@@ -29,8 +29,8 @@ How to use
2929
Ingress ad egress chains
3030
^^^^^^^^^^^^^^^^^^^^^^^^
3131

32-
The service is based on the ingress and egress chains.
33-
Ingress and egress chains are independent and have two different policy sets.
32+
The service supports independent ingress and egress policy chains, with two different policy sets.
33+
3434

3535
Rule insertion
3636
^^^^^^^^^^^^^^

0 commit comments

Comments
 (0)