From: Ben Pfaff Date: Wed, 9 Oct 2013 22:22:15 +0000 (-0700) Subject: FAQ: Elaborate further on how one drops packets with OpenFlow. X-Git-Tag: sliver-openvswitch-2.0.90-1~6^2~20 X-Git-Url: http://git.onelab.eu/?a=commitdiff_plain;h=e5f1da19948e761e44bb1bce283dd134c56e7b43;p=sliver-openvswitch.git FAQ: Elaborate further on how one drops packets with OpenFlow. Signed-off-by: Ben Pfaff --- diff --git a/FAQ b/FAQ index 0a081ff7d..8b1ccb415 100644 --- a/FAQ +++ b/FAQ @@ -1255,9 +1255,11 @@ A: To debug network behavior problems, trace the path of a packet, Q: How do I make a flow drop packets? -A: An empty set of actions causes a packet to be dropped. You can - specify an empty set of actions with "actions=" on the ovs-ofctl - command line. For example: +A: To drop a packet is to receive it without forwarding it. OpenFlow + explicitly specifies forwarding actions. Thus, a flow with an + empty set of actions does not forward packets anywhere, causing + them to be dropped. You can specify an empty set of actions with + "actions=" on the ovs-ofctl command line. For example: ovs-ofctl add-flow br0 priority=65535,actions= @@ -1269,6 +1271,9 @@ A: An empty set of actions causes a packet to be dropped. You can ovs-ofctl add-flow br0 priority=65535,actions=drop + "drop" is not an action, either in OpenFlow or Open vSwitch. + Rather, it is only a way to say that there are no actions. + Q: I added a flow to send packets out the ingress port, like this: ovs-ofctl add-flow br0 in_port=2,actions=2