When I test OvS openflow, I confuse the 'in_port' with
'output:in_port'. I doc the openflow.rst and it may
help others to avoid it.
Signed-off-by: nickcooper-zhangtonghao <n...@opencloud.tech>
---
Documentation/faq/openflow.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/faq/openflow.rst b/Documentation/faq/openflow.rst
index 7cd6161..1563893 100644
--- a/Documentation/faq/openflow.rst
+++ b/Documentation/faq/openflow.rst
@@ -362,6 +362,10 @@ but OVS drops the packets instead.
$ ovs-ofctl add-flow br0 in_port=2,actions=in_port
+ But if you use the ``output:in_port``, the packet is not output.::
+
+ $ ovs-ofctl add-flow br0 in_port=2,actions=output:in_port
+
This also works in some circumstances where the flow doesn't match on the
input port. For example, if you know that your switch has five ports
numbered 2 through 6, then the following will send every received packet
--
1.8.3.1
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
