On Thu, Apr 18, 2013 at 02:42:10PM -0300, Luiz Ozaki wrote:
> On 4/17/13 8:03 PM, Ben Pfaff wrote:
> >+ovs-ofctl add-flows br0 - <<'EOF'
> >+ table=4 reg0=0 priority=99 dl_vlan=20 actions=1,strip_vlan,2
> >+ table=4 reg0=0 priority=99 dl_vlan=30 actions=1,strip_vlan,3,4
> >+ table=4 reg0=0 priority=50 actions=1
> >+EOF
>
> Wouldn't the last flow (table=4 reg0=0 priority=50 actions=1) cause
> the flooeded packet that came from the trunk to be flooded back to
> the trunk ?
Keep reading, please:
>>> Our rules rely on the standard OpenFlow behavior that an output
action will not forward a packet back out the port it came in on.
That is, if a packet comes in on p1, and we've learned that the
packet's destination MAC is also on p1, so that we end up with
"actions=1" as our actions, the switch will not forward the packet
back out its input port. The multicast/broadcast/unknown
destination cases above also rely on this behavior.
> It would be nice to have a link to this on the OVS page ;)
Sure, after it gets reviewed and committed, I'll add a link.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
