+=======================+=========================+=======================+
| Equal | 'foo' == 'bar' | Compare the two |
| | | values and return |
- | | | `true` or `false` |
+ | | | ``true`` or ``false`` |
+-----------------------+-------------------------+-----------------------+
| Not | not ('foo' == 'bar') | Logical negation |
+-----------------------+-------------------------+-----------------------+
Split
---------
-The Split operator ``split(value, delimiters, field-number)`` accepts a list
+The split operator ``split(value, delimiters, field-number)`` accepts a list
of characters to use as delimiters and a positive field number of the
desired field when the value is split into fields separated by the delimiters.
Adjacent delimiters are not compressed out, rather they result in an empty
To achieve this, the regular class must also contain the fixed part of the
spawned class name:
- SPAWN_<template-class-name-used-to-activate-this-regular-class>_<evaluated-value-filtering-this-regular-class>
+ ``SPAWN_<template-class-name-used-to-activate-this-regular-class>_<evaluated-value-filtering-this-regular-class>``
::
.. note ::
The ``template-test`` expression can also be used to filter generated spawned
- classes, so that they are created only when needed by using the `ifelse`
+ classes, so that they are created only when needed by using the ``ifelse``
instruction.
::
For example, using the configuration below, ingress DHCPv6 packets that have
client ID values (in the format expressed by the Kea evaluator) ``foobar``
and ``foofoo`` both amount to the same limit of 60 packets per day, while
- other packets that have the first three hextets different than `foo` are put
+ other packets that have the first three hextets different than ``foo`` are put
in separate rate limiting buckets.
::