From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: Royce Niu <royceniu@gmail.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Request an example config for DPDK IP PIPELINE
Date: Mon, 25 Jan 2016 17:00:44 +0000 [thread overview]
Message-ID: <54CBAA185211B4429112C315DA58FF6DDB10F5@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAOwUCNvdiOyK4pV_h2UtmmUw+yQEWp5wdpduyRnY7bq5R542Gw@mail.gmail.com>
Hi Royce,
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Royce Niu
> Sent: Monday, January 25, 2016 4:03 PM
> To: Thomas Monjalon
> Cc: users@dpdk.org
> Subject: Re: [dpdk-users] Request an example config for DPDK IP PIPELINE
>
> Thanks!
>
> Sorry to bother you again.
> If there any example config on firewall?
> I find http://dpdk.org/dev/patchwork/patch/5778/ from Google.
> However, the patch is not in both 2.2.0 and master.
> So, is the firewall usable?
>
> By the way, I will try my best to add the solution my problem in the doc.
Firewall component exists in IP_Pipeline sample application.
Please check
http://dpdk.org/browse/dpdk/tree/examples/ip_pipeline/config/edge_router_upstream.cfg
In the above configuration file, firewall has been set up as first pipeline in the chain. You can learn the configuration parameters of the firewall from this file.
For firewall rules, please check
http://dpdk.org/browse/dpdk/tree/examples/ip_pipeline/config/edge_router_upstream.sh
In the above script file, the rules have been defined for firewall pipeline.
Thanks,
Jasvinder
next prev parent reply other threads:[~2016-01-25 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 15:40 Royce Niu
2016-01-25 15:42 ` Thomas Monjalon
2016-01-25 15:46 ` Royce Niu
2016-01-25 15:58 ` Thomas Monjalon
2016-01-25 16:03 ` Royce Niu
2016-01-25 17:00 ` Singh, Jasvinder [this message]
2016-01-25 17:09 ` Royce Niu
2016-01-25 17:18 ` Singh, Jasvinder
2016-01-25 17:21 ` Royce Niu
[not found] ` <56AA0736.3080908@intel.com>
2016-01-28 14:14 ` Singh, Jasvinder
2016-01-28 14:26 ` Royce Niu
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=54CBAA185211B4429112C315DA58FF6DDB10F5@IRSMSX103.ger.corp.intel.com \
--to=jasvinder.singh@intel.com \
--cc=royceniu@gmail.com \
--cc=thomas.monjalon@6wind.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).