The set_tunnel action
Syntax:
set_tunnel:id
set_tunnel64:id
Many kinds of tunnels support a tunnel ID, e.g. VXLAN and Geneve
have a 24-bit VNI, and GRE has an optional 32-bit key. This
action sets the value used for tunnel ID in such tunneled
packets, although whether it is used for a particular tunnel
depends on the tunnel's configuration. See the tunnel ID
documentation in ovs-fields(7) for more information.
Conformance:
These actions are OpenFlow extensions. set_tunnel was introduced
in Open vSwitch 1.0. set_tunnel64, which is needed if id is wider
than 32 bits, was added in Open vSwitch 1.1. Both actions always
set the entire tunnel ID field.
Open vSwitch supports these actions in all versions of OpenFlow,
but in OpenFlow 1.2 and later it translates them to an
appropriate standardized OFPAT_SET_FIELD action.
The set_queue and pop_queue actions
Syntax:
set_queue:queue
pop_queue
The set_queue action sets the queue ID to be used for subsequent
output actions to queue, which must be a 32-bit integer. The
range of meaningful values of queue, and their meanings, varies
greatly from one OpenFlow implementation to another. Even within
a single implementation, there is no guarantee that all OpenFlow
ports have the same queues configured or that all OpenFlow ports
in an implementation can be configured the same way queue-wise.
For more information, see the documentation for the output queue
field in ovs-fields(7).
The pop_queue restores the output queue to the default that was
set when the packet entered the switch (generally 0).
Four billion queues ought to be enough for anyone: ⟨https://
mailman.stanford.edu/pipermail/openflow-spec/2009-August/
000394.html⟩
Conformance:
OpenFlow 1.1 introduced the set_queue action. Open vSwitch also
supports it as an extension in OpenFlow 1.0.
The pop_queue action is an Open vSwitch extension.
