Damion de Soto wrote:
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
Jason Boxman wrote:
On Monday 17 May 2004 17:23, Ed Wildgoose wrote:
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 leas
Am Monday 17 May 2004 23:31 schrieb Ed Wildgoose:
> First is: 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?
Probably with IMQ. Another way would by modifying your ingress filters, so
that they don't match packets you don't w
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
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 /lib/modules/[kversion]/ker
Ed Wildgoose wrote:
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
Jason Boxman wrote:
On Friday 14 May 2004 05:55, Andy Furniss wrote:
If you can get a cell count from your modem you can work it out with
ping. I don't know what your pppoe is.
I can probably get my USB Stringray out of the closet and hook it up. I think
the Windows diagnostic utility for it ac
On Monday 17 May 2004 17:23, Ed Wildgoose wrote:
> 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, h
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
c
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 cl
Hello,
On Mon, 17 May 2004, Charles-Etienne.Dube wrote:
> I did some tests with 2 cable modems, but now it is installed in a production
> environment with 4 cable modems. At first, everything seemed to work fine..
> But now I had a couple of users tell me that some web pages were
> not
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 det
12 matches
Mail list logo
