From: "Liu, Yong" <yong.liu@intel.com>
To: "hkm73560@gmail.com" <hkm73560@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Where is rule_ipv4.db and rule_ipv6.db for l3pwd-acl example?
Date: Wed, 15 Apr 2015 14:16:37 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10DBEA76@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CACuKTmN9j-saN=n-WrEuoZM0xZun+C3kOyPmq=wXpLBsgwNhmg@mail.gmail.com>
Hi,
These rules parse failure for missing blank space between the start and end of port. Looks like user guide shown us the wrong format:)
L3fwd-acl sample will request at least one route rule. You can just add one simple rule as below which forward all packets to port0.
-bash-4.3# cat rule_ipv4.db
R0.0.0.0/0 0.0.0.0/0 0 : 65535 0 : 65535 0x00/0x00 0
-bash-4.3# cat rule_ipv6.db
R0:0:0:0:0:0:0:0/0 0:0:0:0:0:0:0:0/0 0 : 65535 0 : 65535 0x00/0x00 0
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ???
> Sent: Wednesday, April 15, 2015 10:40 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Where is rule_ipv4.db and rule_ipv6.db for l3pwd-acl
> example?
>
> Hi,
> I can`t find the rule format files (rule_ipv4.db and rule_ipv6.db) so I
> can`t run the access control example.
>
> I wrote my own rule file based on rule file example in the sample app
> document, but the example stopped saying that "Cause: ./ipv4.txt Line 1:
> parse rules error".
> My rule file likes below:
> @1.2.3.0/24 192.168.0.36/32 0:65535 0:65535 6/0xfe 0
> R0.0.0.0/0 192.168.0.36/32 0:65535 0:65535 6/0xfe 1
> R0.0.0.0/0 0.0.0.0/0 0:65535 0:65535 6/0xfe 0
>
> what`s wrong with my rule file? and where is the example rule files?
prev parent reply other threads:[~2015-04-15 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 2:40 황규민
2015-04-15 9:35 ` Ananyev, Konstantin
2015-04-15 14:16 ` Liu, Yong [this message]
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=86228AFD5BCD8E4EBFD2B90117B5E81E10DBEA76@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dev@dpdk.org \
--cc=hkm73560@gmail.com \
/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).