Thanks Ben. We don't have a patch. The purpose of the mail was just to find if we are missing some information related to multidimensional ranges and if it's implemented already.
-- Usman On Sun, Aug 21, 2011 at 12:04 AM, Ben Pfaff <b...@nicira.com> wrote: > On Sat, Aug 20, 2011 at 11:36:26PM +0500, Usman Ajmal wrote: > > That's what I am interested in too. For example, I can write a wildcarded > > rule for a particular subnet say 192.168.2.* where * denotes a wildcarded > > field but I couldn't find a functionality to specify a particular range, > say > > 192.168.2.1 to 192.168.2.100, as Masoud mentioned. > > > > An example of such a rule will be something like, "If a packet received > has > > an src_ip in the range mentioned above, forward it to port 2 of the > > switch (action.out_port = 2)". > > > > As far as I know Openflow specification 1.0, also don't talk about this. > > > > Am I missing here something? > > It's difficult to implement multidimensional range matching cleanly and > efficiently in the general case. That's why it isn't implemented. > > If you have a clean patch that implements it, we'll look at it. > > Thanks, > > Ben. > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
