Re: [LARTC] About ingress

[Stef Coene <stef.coene@docum.org>]

On Tuesday 11 February 2003 17:57, Nelson Guedes Paulo Junior wrote:
> Hi all,
>
> I couldn't figure, in the following command, whats the meaning of the
> flowid.
>
> tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match ip /
>  src 0.0.0.0/0 police rate 38kbit burst 38kbit drop flowid :1
>
> :1 means what??
It means that's going to redirect all traffic to class ffff:1 (flowid = 
classid).  But ingress is classless.  So the there is no real class ffff:1.  
But you have to redirect the traffic to something.  Actually, the ingress 
qdisc is a dummy qdisc.  The only thing you can do with it is add filters.

> There's some way to create other classes like the egress has?
No.

> For example, I coulde use this:
>
> tc qdisc add dev eth0 root handle 1: prio
> tc qdisc add dev eth0 parent 1:1 handle 10: sfq perturb 10
> tc qdisc add dev eth0 parent 1:2 handle 20: sfq perturb 10
> tc qdisc add dev eth0 parent 1:3 handle 30: sfq perturb 10
>
> And create a prio qdisc with 3 qdiscs inside.
>
> There's some way to do that with a ingress filter???
No.
Long answer : yes.  You can use the imq device.  If you patch the kernel and 
iptables, you can make a virutal imq device and redirect all incoming traffic 
to it.  You can add egress qdisc to the imq device.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/