It seems Andreas Klauer's fairnat has experimental support for using HTB's MPU
and overhead options.
fairnat.config:
# Use MPU for HTB. From the LARTC Howto on MPU:
# A zero-sized packet does not use zero bandwidth. For ethernet, no packet
# uses less than 64 bytes. The Minimum Packet Unit
I imagine that 106 value is a reference to this post:
http://mailman.ds9a.nl/pipermail/lartc/2004q2/012369.html
...
It's my suspicion that the MPU and overhead options for HTB would assist in
resolving this and enable me to resume using 190kbit instead of 160kbit for
the outer most parent
Two easy questions after having read the LARTC HOWTO document (which by
the way is a *fantastic* document. Congratulations to all who contributed!)
First is: Can I prioritise my drops on incoming traffic when the link
is overloaded. ie instead of just tail dropping, can I prefer to drop
On Monday 17 May 2004 17:23, Ed Wildgoose wrote:
snip
Read the follows to that post as well. Basically it's only an
approximation. The MPU is basically pointing out that your ADSL
stream is encapsulated in an ATM stream. ATM uses fixed size 64 byte
packets. You need at least 2 of these,
Andy Furniss wrote:
You can make HTB more accurate by setting HTB_HYSTERESIS to 0 in
net/sched/sch_htb.c.
To save time - if you built HTB as a module, you can probably (well it
worked for me) get away with editing htb.c and do
make SUBDIRS=net/sched modules
and replacing
Hi Ed,
First is: Can I prioritise my drops on incoming traffic when the link
is overloaded. ie instead of just tail dropping, can I prefer to drop
certain classes of traffic? If so, do I do this by setting up, say, a
HTB tree like on the incoming, but the only action at the leaf is to drop?
