On Tue, Jul 01, 2014 at 11:40:31AM -0700, Ben Pfaff wrote:
> On Tue, Jul 01, 2014 at 03:28:54PM -0300, Flavio Leitner wrote:
> > On Tue, Jul 01, 2014 at 11:22:10AM -0700, Ben Pfaff wrote:
> > > On Tue, Jul 01, 2014 at 03:13:20PM -0300, Flavio Leitner wrote:
> > > > On Tue, Jul 01, 2014 at 11:05:15AM -0700, Ben Pfaff wrote:
> > > > > On Tue, Jul 01, 2014 at 01:57:17PM -0400, Jason Thorpe wrote:
> > > > > 
> > > > > > if I have a rule, nw_src=192.168.0.0/16 and a specific rule,
> > > > > > nw_src=192.168.0.1/32 and a packet comes from 192.168.0.1, which
> > > > > > rule will it match? the /16 or /32? I want to match the 192.168.0.1
> > > > > > packet even if I have both rules
> > > > > 
> > > > > If a packet can match two rules, use priority to disambiguate.
> > > > > Otherwise the behavior is undefined.
> > > > 
> > > > Isn't the more specific one first?
> > > 
> > > No.
> > 
> > For some reason I though exact matches gets prioritized over wildcarded
> > ones.
> 
> This was true in OpenFlow 1.0: a flow that has no wildcards at all has
> higher priority than wildcarded flows.  OVS implements this by just
> changing those flows' priorities to 65535.
> 
> This rule doesn't generalize to a "longest-prefix match" or anything
> like that, and it was deleted from OpenFlow 1.1 anyway.

Thanks for the detailed explanation.

> >   Anyway, priority needs to be used in any case as Ben says.
> > 
> > Additional info can be found in ovs-vsctl(8) man-page:
> 
> I think that's from the ovs-ofctl manpage.

Oops, you're right.

fbl
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to