Re: [LARTC] ingress and egress

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 21 May 2002 03:31, hanhbnetfilter wrote:
> ingress can be used to control the incoming packet,
> such as:
> tc qdisc add dev eth0 handle ffff: ingress
> tc filter add dev eth0 parent ffff: protocol ip prio 5
> u32 match ip src 172.16.1.11 police rate 10kbit burst
> 10k drop flowid :1
> tc filter add dev eth0 parent ffff: protocol ip prio 5
>
> u32 match ip src 172.16.1.22 police rate 10kbit burst
> 10k drop flowid :2
> first ,I do not sure these method can  use class(could
> it do? I tested it can not do). if it can do it
> ,please give me a example.
Ingress qdisc is classless.

> second, rate can not be shared, if i want to control
> the incoming packet rate not throug egress qdisc, and
> the rate can be shared, please tell me how can i do.
You can use use the imq device.  You can redirect packets (incoming and 
outgoing) to this device.  And you can attach CBQ or HTB to this device.  A 
link can be found on www.docum.org under faq.

Stef

-- 

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


[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux