Thanks Ben for your prompt answer. Your answer eliminates the confusion.
On Sun, Aug 21, 2011 at 1:57 AM, Ben Pfaff wrote:
> On Sat, Aug 20, 2011 at 11:12:10PM +0500, Tahir Rauf wrote:
> > I got a little question regarding wildcards of nw_src address. I have
> > written a controller application
On Sat, Aug 20, 2011 at 11:12:10PM +0500, Tahir Rauf wrote:
> I got a little question regarding wildcards of nw_src address. I have
> written a controller application which sets the wildcards as following
>
> 1. ofm->match.wildcards = htonlOFPFW_ALL & ~ OFPFW_DL_SRC) & ~
> OFPFW_DL_DST) & ~ O
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 wrote:
> On Sat, Aug 20, 2011 at 11:36:26PM +0500, Usman Ajmal
On Sun, Aug 21, 2011 at 12:45:23AM +0500, Tahir Rauf wrote:
> Another aspect of the problem is that although implementation of Range-match
> in OVS is not difficult, [...]
It's not? Sincerely, I'd gratefully accept patches.
___
discuss mailing list
disc
Hi,
I think that up till now, there is lack of support to add specific ranges.
However, you can add some general ranges like 192.168.2.1 to
192.168.2.*256*by adding rule like
192.168.2.0/8. You can only tell that how many consecutive LSBs you want to
ignore.
Another aspect of the problem is that a
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.1
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 r
Hi,
I got a little question regarding wildcards of nw_src address. I have
written a controller application which sets the wildcards as following
1. ofm->match.wildcards = htonlOFPFW_ALL & ~ OFPFW_DL_SRC) & ~
OFPFW_DL_DST) & ~ OFPFW_DL_TYPE) & ~ OFPFW_NW_SRC_ALL);
The above statement yields wi
