From: Tao Wang <tao.wang0221@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Request for a valid ip_pipeline example to configure firewall
Date: Fri, 15 Jul 2016 22:58:57 +0800 [thread overview]
Message-ID: <CAK0ntGgAp9izR8Ey_XesANQT=HJg5cz0wYAVrg21tL1C2bd2XA@mail.gmail.com> (raw)
Dear all,
I am using the dpdp-16.04 in a qemu-kvm based CentOS7 VM.
I am running the ip_pipeline example. However, I can not get firewall
configured rightly according to the config files posted at
http://dpdk.org/browse/dpdk/tree/examples/ip_pipeline/config.
But there are some problems,
1) CLI command "p 1 firewall add priority 1 ipv4 0.0.0.0 0 100.0.0.0 10 0
65535 0 65535 6 0xF port 0" returns "bad argument"
2) CLI command "p 1 firewall add default 4 #SINK0" returns "command failed"
So how to configure it rightly? What's the right semantics of the CLI
command for firewall?
Wish for your reply.
Best,
Tao
next reply other threads:[~2016-07-15 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 14:58 Tao Wang [this message]
2016-07-15 16:01 ` Singh, Jasvinder
2016-07-16 5:58 ` Tao Wang
2016-07-17 7:53 ` Singh, Jasvinder
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='CAK0ntGgAp9izR8Ey_XesANQT=HJg5cz0wYAVrg21tL1C2bd2XA@mail.gmail.com' \
--to=tao.wang0221@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).