Hopefully I got the right thread here ("FAQ: Elaborate further on how
one drops packets with OpenFlow.").Acked-by: Joe Stringer <[email protected]> On Wed, Oct 9, 2013 at 3:22 PM, Ben Pfaff <[email protected]> wrote: > > Signed-off-by: Ben Pfaff <[email protected]> > --- > FAQ | 11 ++++++++--- > 1 file changed, 8 insertions(+), 3 deletions(-) > > diff --git a/FAQ b/FAQ > index d36495c..14fb1c0 100644 > --- a/FAQ > +++ b/FAQ > @@ -1235,9 +1235,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= > > @@ -1249,6 +1251,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 > -- > 1.7.10.4 > > _______________________________________________ > dev mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
