Re: [ovs-discuss] What is a l2 pkt microflow

2017-11-20 Thread Sara Gittlin
Thank you Ben Is this L2 flow is an entry in one of the kernel megaflow tables ? otherwise if it an entry in the kernel microflow table - then there should be multiple microflow tables, because L2 flow keys consist only of L2 header, while for other flow the keys are l2+l3 headers. i thought

Re: [ovs-discuss] OpenFlow “select” group

2017-11-20 Thread Ben Pfaff
No. On Mon, Nov 20, 2017 at 11:41:26AM -0600, Prabhu wrote: > Just curios to know, does Group selection method support weighted round > robin selection method ? > > > On 11/20/2017 11:37 AM, Ben Pfaff wrote: > >On Thu, Nov 16, 2017 at 04:41:07PM -0500, Ronaldo Resende wrote: > >>I know that

Re: [ovs-discuss] OpenFlow “select” group

2017-11-20 Thread Prabhu
Just curios to know, does Group selection method support weighted round robin selection method ? On 11/20/2017 11:37 AM, Ben Pfaff wrote: On Thu, Nov 16, 2017 at 04:41:07PM -0500, Ronaldo Resende wrote: I know that Open vSwitch 2.4 and later + OpenFlow 1.4, by default, hashes some headers

Re: [ovs-discuss] What is a l2 pkt microflow

2017-11-20 Thread Ben Pfaff
On Thu, Nov 16, 2017 at 07:46:05PM +0200, Sara Gittlin wrote: > I understand that microflow kernel cache entries consist of full set of > header keys. > What about a l2 pkt e.g cfm pkt. What are the hash keys for cfm pkt in the > single microflow table? Just the Ethernet header.

Re: [ovs-discuss] OpenFlow “select” group

2017-11-20 Thread Ben Pfaff
On Thu, Nov 16, 2017 at 04:41:07PM -0500, Ronaldo Resende wrote: > I know that Open vSwitch 2.4 and later + OpenFlow 1.4, by default, hashes > some headers fields to choose a bucket in a select group. > > What if I want to change the way this is being done? What would be the > right approach to

Re: [ovs-discuss] in_port=local never matches for flows

2017-11-20 Thread Ben Pfaff
On Fri, Nov 17, 2017 at 02:16:55PM +, Jan De Landtsheer wrote: > Hello again, > > I'm trying to define a conntrack flow that allows connections from linux > namespace1 to a test namespace, and block everything from the test > namespace to the host > > for that I create a bridge, add a port,