From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 221] How to classifier ipv6 packets with flow classification library
Date: Wed, 06 Mar 2019 01:03:09 +0000 [thread overview]
Message-ID: <bug-221-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=221
Bug ID: 221
Summary: How to classifier ipv6 packets with flow
classification library
Product: DPDK
Version: 17.11
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: coalacoco@gmail.com
Target Milestone: ---
Hello. Thank you for your support!
I want to know if dpdk support "Flow classification for ipv6 packet".
We want to classifier ipv6 packets with specific rules using dpdk libraries!
Example, dpdk offers 'Flow classification Library' for ipv4 packets.
We are using rte_flow_classifier_query() function for classificating ipv4
packets.
Have you any classification libraries for ipv6 packets? like
https://doc.dpdk.org/guides/prog_guide/flow_classify_lib.html ( for ipv4)
We want some sample codes or guide for classification for ipv6 packets.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-03-06 1:03 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=bug-221-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).