From: Shyam Shrivastav <shrivastav.shyam@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] ip_pipeline firewall port filtering
Date: Fri, 17 Mar 2017 11:34:03 +0530 [thread overview]
Message-ID: <CAGSp03=ctU1vOd=HBYN8iQxMMaMXxLgAri7B+t5z3cmLHuCAKA@mail.gmail.com> (raw)
Hi
I am trying to just allow tcp dest port 80 packets using ip_pipeline
firewall, configured as under
------------------------------------------------------------------------------------------------------------------------------------
pipeline> p 1 firewall add priority 1 ipv4 0.0.0.0 0 0.0.0.0 0 0 65535 80
80 6 0xF port 0
pipeline> p 1 firewall ls
Prio = 1 (SA = 0.0.0.0/0, DA = 0.0.0.0/0, SP = 0-65535, DP = 80-80, Proto =
6 / 0xf) => Port = 0 (entry ptr = 0x7fddf9f0ff08)
Default rule: DROP
-----------------------------------------------------------------------------------------------------------------------------------
but it is not working and all tcp packets are getting dropped. If I
configure dest port range to be wildcard(0-65535) then tcp packets are
allowed
-----------------------------------------------------------------------------------------------------------------------------------
pipeline> p 1 firewall add priority 1 ipv4 0.0.0.0 0 0.0.0.0 0 0 65535 0
65535 6 0xF port 0
Prio = 1 (SA = 0.0.0.0/0, DA = 0.0.0.0/0, SP = 0-65535, DP = 0-65535, Proto
= 6 / 0xf) => Port = 0 (entry ptr = 0x7fddf9f0ff08)
pipeline> p 1 firewall ls
Prio = 1 (SA = 0.0.0.0/0, DA = 0.0.0.0/0, SP = 0-65535, DP = 0-65535, Proto
= 6 / 0xf) => Port = 0 (entry ptr = 0x7fddf9f0ff08)
Default rule: DROP
--------------------------------------------------------------------------------------------------------------------------------------
Has anyone got specific port filtering work with ip_pipeline firewall?
I am debugging this, meanwhile any help/guidance would be greatly
appreciated.
Thanks and rgds
Shyam
next reply other threads:[~2017-03-17 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 6:04 Shyam Shrivastav [this message]
2017-03-18 7:18 Shyam Shrivastav
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='CAGSp03=ctU1vOd=HBYN8iQxMMaMXxLgAri7B+t5z3cmLHuCAKA@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).