* route classifiers and mirred actions
@ 2011-12-24 17:47 John A. Sullivan III
0 siblings, 0 replies; only message in thread
From: John A. Sullivan III @ 2011-12-24 17:47 UTC (permalink / raw)
To: netdev
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-12-24 17:47 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-24 17:47 route classifiers and mirred actions John A. Sullivan III
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox