From: Shyam Shrivastav <shrivastav.shyam@gmail.com>
To: users@dpdk.org
Cc: Shyam Shrivastav <shrivastav.shyam@gmail.com>
Subject: [dpdk-users] ip_pipeline firewall customization
Date: Tue, 7 Mar 2017 13:36:52 +0530 [thread overview]
Message-ID: <CAGSp03kgjiCyFF4BZL3ZcvM9gxWAfh=EoyJjjnOW298L_VxQeQ@mail.gmail.com> (raw)
Hello friends
I am using ip_pipeline firewall as base for our project, need
comments/suggestions/corrections regarding following
1) We can not configure firewall rule to drop packets, as portid is
mandatory in command. I am planning to allow this for our requirement with
following code changes
a) Allow "port" as optional parameter (pipeline_firewall.c), pass -1
as port id if "port" is not specified to app_pipeline_firewall_add_rule and
change that parameter to int32_t.
b) Make required changes in pipeline_firewall_msg_req_add_handler if
portid is -1, that is table entry action to be .action =
RTE_PIPELINE_ACTION_DROP.
2) I am registering a f_action_hit function for firewall table to perform
certain translations if action is pass (RTE_PIPELINE_ACTION_PORT).
Configured a rule like following
pipeline>p 1 firewall add priority 1 ipv4 0.0.0.0 0 0.0.0.0 0 0 65535 0
65535 0 0 port 0
which should be hit only by ipv4 packets. However even ARP packets are hit
by this ACL and my routine is called. If I configure a specific src or dst
ip then everything works fine and arp packets are not hit , for example
following rule hits only ipv4 icmp packets
pipeline> p 1 firewall add priority 1 ipv4 0.0.0.0 0 45.35.70.12 32 0
65535 0 65535 1 0xf port 0
Is this a bug or am I missing something ?
Best regards
Shyam
reply other threads:[~2017-03-07 8:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAGSp03kgjiCyFF4BZL3ZcvM9gxWAfh=EoyJjjnOW298L_VxQeQ@mail.gmail.com' \
--to=shrivastav.shyam@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).