From: Shyam Shrivastav <shrivastav.shyam@gmail.com>
To: dev@dpdk.org, users@dpdk.org
Cc: Shyam Shrivastav <shrivastav.shyam@gmail.com>
Subject: [dpdk-dev] ip_pipeline firewall : fragmented ipv4 packets handling
Date: Fri, 17 Mar 2017 11:22:54 +0530 [thread overview]
Message-ID: <CAGSp03kNzs_oiaQ4faqEyMAh=iWZx+9U+Bfzg6jUyS9YRO_koA@mail.gmail.com> (raw)
Again sending this issue as no response on original post. As per my
understanding if we are supporting ACL on tcp/usp port ranges then ipv4
packets must be reassembled before checking against ACL, then fragmented
if required during forwarding. So there are three cases
1) My understanding is wrong then please correct me.
2) We correct this in examples wherever we are supporting access control on
udp/tcp ports.
3) We document this clearly.
-------------------------------------------------
Below is my original post
-------------------------------------------------
Hi All
Filtering based on TCP/UDP fields like src/dest port range works correctly
only on non-fragmented packets , that means reassembly must be done before
packets hit firewall rules table. Also packets must be fragmented before
transmission if larger than port mtu. This is unsupported currently, any
plans for this in near future?
Regards
reply other threads:[~2017-03-17 5:52 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='CAGSp03kNzs_oiaQ4faqEyMAh=iWZx+9U+Bfzg6jUyS9YRO_koA@mail.gmail.com' \
--to=shrivastav.shyam@gmail.com \
--cc=dev@dpdk.org \
--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).