DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] rte_acl test-acl app
@ 2014-10-25  3:15 Erik Ziegenbalg
  0 siblings, 0 replies; 3+ messages in thread
From: Erik Ziegenbalg @ 2014-10-25  3:15 UTC (permalink / raw)
  To: dev

Hi everyone,

I am having trouble to successfully perform a packet classification
using the rte_acl test app. I have my rules.acl and trace.acl files as
follows:

rules.acl:
@192.168.0.0/24 192.168.0.0/24 400 : 500 1000 : 2000 6/0xff

trace.acl:
192.168.0.5 192.168.0.9 450 1002 0x06

However, the result always comes up as 4294967295 (xFFFFFFFF). I have
dug through the code quite a bit to follow and see what is going on, but
not sure where I went wrong.

Any help on how the rte_acl_classify function works would be much
appreciated. In understand that the data for rte_acl_classify is a
uint32_t ** and I double checked to make sure I'm passing along proper
values. Is xFFFFFFFF the expected result? If so, I am getting the same
for packets that should not match.

Thank you,
Erik Ziegenbalg

^ permalink raw reply	[flat|nested] 3+ messages in thread
* [dpdk-dev] rte_acl test-acl app
@ 2014-10-25  3:19 Erik Ziegenbalg
  2014-10-28 11:51 ` Ananyev, Konstantin
  0 siblings, 1 reply; 3+ messages in thread
From: Erik Ziegenbalg @ 2014-10-25  3:19 UTC (permalink / raw)
  To: dev

Hi everyone,

I am having trouble to successfully perform a packet classification
using the rte_acl test app. I have my rules.acl and trace.acl files as
follows:

rules.acl:
@192.168.0.0/24 192.168.0.0/24 400 : 500 1000 : 2000 6/0xff

trace.acl:
192.168.0.5 192.168.0.9 450 1002 0x06

However, the result always comes up as 4294967295 (xFFFFFFFF). I have
dug through the code quite a bit to follow and see what is going on, but
not sure where I went wrong.

Any help on how the rte_acl_classify function works would be much
appreciated. In understand that the data for rte_acl_classify is a
uint32_t ** and I double checked to make sure I'm passing along proper
values. Is xFFFFFFFF the expected result? If so, I am getting the same
for packets that should not match.

Thank you,
Erik Ziegenbalg

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-10-28 11:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-10-25  3:15 [dpdk-dev] rte_acl test-acl app Erik Ziegenbalg
2014-10-25  3:19 Erik Ziegenbalg
2014-10-28 11:51 ` Ananyev, Konstantin

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git