From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: Tao Wang <tao.wang0221@gmail.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Request for a valid ip_pipeline example to configure firewall
Date: Fri, 15 Jul 2016 16:01:37 +0000 [thread overview]
Message-ID: <54CBAA185211B4429112C315DA58FF6DE7C444@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAK0ntGgAp9izR8Ey_XesANQT=HJg5cz0wYAVrg21tL1C2bd2XA@mail.gmail.com>
Hi Tao,
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Tao Wang
> Sent: Friday, July 15, 2016 3:59 PM
> To: users@dpdk.org
> Subject: [dpdk-users] Request for a valid ip_pipeline example to configure
> firewall
>
> 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"
If you are working on 16.04, the command format for adding firewall rule is as below;
p <pipeline_id> firewall add ipv4 <priority> <src ip><src ip mask><dst ip><ds tip mask><src_port_from><src_port_to><dst_port_from><dst_port_to><protocol><protocol_mask><port id>
The reason why your command is failing is because in 16.07 we have changed the command format for adding rule to firewall pipeline.
> 2) CLI command "p 1 firewall add default 4 #SINK0" returns "command failed"
I guess you have configured 4 ports (port id 0 -3), so if this is the case, use right port id.
>
> So how to configure it rightly? What's the right semantics of the CLI command
> for firewall?
To learn the command format, please follow the code - ip_pipeline/pipeline/pipeline_firewall.c
> Wish for your reply.
>
> Best,
> Tao
Jasvinder
next prev parent reply other threads:[~2016-07-15 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 14:58 Tao Wang
2016-07-15 16:01 ` Singh, Jasvinder [this message]
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=54CBAA185211B4429112C315DA58FF6DE7C444@IRSMSX103.ger.corp.intel.com \
--to=jasvinder.singh@intel.com \
--cc=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).