From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: netdev@vger.kernel.org
Subject: route classifiers and mirred actions
Date: Sat, 24 Dec 2011 12:47:20 -0500 [thread overview]
Message-ID: <1324748840.3200.20.camel@denise.theartistscloset.com> (raw)
Hello, all. I may have a workaround for the problem we have using netem
with ingress filters but I have hit a roadblock in implementing it. It
appears I cannot use an action with a route classifier. Specifically:
root@testswitch01:~# tc filter add dev eth0 parent ffff: protocol ip prio 50 route fromif eth1 action mirred egress redirect dev ifb1
What is "action"?
Usage: ... route [ from REALM | fromif TAG ] [ to REALM ]
[ flowid CLASSID ] [ police POLICE_SPEC ]
POLICE_SPEC := ... look at TBF
CLASSID := X:Y
NOTE: CLASSID is parsed as hexadecimal input.
root@testswitch01:~# tc action add action mirred help
Usage: mirred <DIRECTION> <ACTION> [index INDEX] <dev DEVICENAME>
where:
DIRECTION := <ingress | egress>
ACTION := <mirror | redirect>
INDEX is the specific policy instance id
DEVICENAME is the devicename
Yet, this works:
root@testswitch01:~# tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match u32 0 0 action mirred egress redirect dev ifb1
and this works:
root@testswitch01:~# tc filter add dev eth0 parent ffff: protocol ip prio 1 route fromif eth1 classid 1:10
So why does the u32 classifier work with actions, the route classifier
work with classids, but the route classifier does not work with actions?
Thanks - John
reply other threads:[~2011-12-24 17:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1324748840.3200.20.camel@denise.theartistscloset.com \
--to=jsullivan@opensourcedevel.com \
--cc=netdev@vger.kernel.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