On Monday 28 April 2003 10:45, Szymon Miotk wrote:
> Enric Ramos Mas wrote:
> > I have implemented a traffic control / advanced router server using
> > iproute2 and tc (using htb). For all my outgoing tc policies, all
> > it's ok (all the traffic goes out using eth0, and therefore I'm able
> > to catch it using the corresponfing tc filter).
> >
> > However, the incoming traffic has to be treated in eth1, which has
> > several virtual ifaces (eth1:0, eth1:1, eth1:2 and so on).
> > Even I have introduced all the tc rules correctly, the kernel is not
> > matching any filter rule and there is no way to match any destination
> > into any queue discipline.
> >
> > Anyone knows some way to implement that ?
>
> I'm also very interested about this question as I have similiar link
> configuration.
> One question about classes on eth0: do leaf rates (1:10 - 1:??) sum up
> to 3256kbit (parent rate)?
> I have to split 1040 kbit for 700 users and HTB manual advices
> a) that children rates should sum up to parent rate
> b) that the rate should not be less than 4kbit
This is the first time I hear about this rule. You can have a problem with
quantum if you have a low rate. But you can overrule quantum when you add a
htb class (rule : quantum > MTU).
> I expect that I should go by the b) rule, as used rates will never sum
> up over 1040kbit (there will never be 700 users using this link at the
> same time).
> Am I right?
Yes. The problem is that the parent rate is not respected. So if each class
is sending, it will exceed the parent rate. This can be "bad" because you
send more data then your router/modem can handle so it's possible that you
your shaping will not be that perfect.
Stef
--
stef.coene@xxxxxxxxx
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
