From: sml <sml.caerus@gmail.com>
To: users@dpdk.org
Subject: Re: [dpdk-users] RTE_ACL - Question about ANY PROTO
Date: Sun, 10 Apr 2016 15:09:40 -0400 [thread overview]
Message-ID: <CAHXxcueXa-BpKbhDKLCHak8rF0iKhUVqhF0p4rz+zquGTgP=bA@mail.gmail.com> (raw)
In-Reply-To: <CAHXxcudH8oARd-C9VWTEZRqs292bhmDj_8Dcr8wbS-K_7-DRNQ@mail.gmail.com>
On Sun, Apr 10, 2016 at 2:42 PM, sml <sml.caerus@gmail.com> wrote:
> So I have the ACL library working great. One issue I am running into
> though is how to wildcard the PROTO field (this is for IPv4).
>
> I have set the value to 0x0, range mask to 0x0, 0x0 and 0xff, 0xff and
> 0xff, nothing seems to work.
>
> I want to be able to establish a rule such as:
>
> PROTO: ANY
>
> - thats the rule, it could be expanded of course to:
>
> PROTO: ANY
> SOURCEIP: xxx, and range
>
> But I think first step is in establishing how I set the PROTO field to
> accept any PROTO value?
>
> Any guidance would be greatly appreciated...
>
>
>
Nevermind - Changing to 0x1 and 0xff seems to be working.....
prev parent reply other threads:[~2016-04-10 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 18:42 sml
2016-04-10 19:09 ` sml [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHXxcueXa-BpKbhDKLCHak8rF0iKhUVqhF0p4rz+zquGTgP=bA@mail.gmail.com' \
--to=sml.caerus@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).