- ``drop-packet``: drop the packet.
- ``reject``: same as ``drop-flow``, but reject the current packet as well (see
``reject`` action in Rule's :ref:`actions`).
-- ``reject-both``: same as ``reject``, except that it sends reject packets to both the
+- ``rejectboth``: same as ``reject``, except that it sends reject packets to both the
source and destination addresses.
- ``bypass``: bypass the flow. No further decoding or parsing is done. :ref:`Bypass
<bypass>` may be offloaded.
* - Drop-packet
- Not valid.*
- Not valid.*
- * - Reject / Reject-both
+ * - Reject / Rejectboth
- Not valid.*
- Session not tracked, flow REJECTED.
* - Pass-flow
* - Drop-packet
- Not valid.*
- Not valid.*
- * - Reject / Reject-both
+ * - Reject / Rejectboth
- Not valid.*
- Session not tracked, flow DROPPED and REJECTED.
* - Pass-flow
policy = EXCEPTION_POLICY_PASS_PACKET;
} else if (strcmp(value_str, "reject") == 0) {
policy = EXCEPTION_POLICY_REJECT;
- } else if (strcmp(value_str, "reject-both") == 0) {
+ } else if (strcmp(value_str, "rejectboth") == 0) {
policy = EXCEPTION_POLICY_REJECT_BOTH;
} else if (strcmp(value_str, "ignore") == 0) { // TODO name?
policy = EXCEPTION_POLICY_NOT_SET;