On Tue, Jun 21, 2011 at 7:37 PM, el05682 <[email protected]> wrote: > On Tue, 21 Jun 2011 18:56:06 -0700, Jesse Gross wrote: >> >> On Tue, Jun 21, 2011 at 6:46 PM, el05682 <[email protected]> wrote: >>> >>> Thanx for the quick reply. Got that, but I still haven't solved my >>> problem >>> though. >>> >>> Is there any way to group the packet flow without sacrificing the L2 >>> lookup? >>> I think that the flows to multiple ports (i.e. ovs-ofctl add-flow br0 >>> in_port=3,actions=output:1,2) >>> skip this lookup. >> >> If you're outputting to particular ports then what would L2 learning >> do? It determines the output ports but you've already specified them. >> > If I set a flow from port 1 to 2 and 3 then the packet will go to both > destinations, something > like a hub, but I want something smarter than that.
Well, it's not really acting like a hub. It's simply doing exactly what you tell it to do. > >> You can match on some fields and then do learning for only a set of >> flows by outputting to the NORMAL action. I'm not sure that achieves >> what you are looking for though. > > This could be achieved by multiple actions on an flow rule or by > resubmitting the packet? NORMAL is a virtual OpenFlow port, so you just have to write an output action to direct packets to it. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
