It depends on what rate you are really synced at and what extra
overheads/encapsulation your sdsl line has.
It may be a bit different for sdsl - I only know adsl, but as an
example, for me, an empty ack which htb will see as 40 bytes (ignoring
timestamps/sacks) will actually use 2 atm
Actually doing some more tests with all traffic classified can reach 1700
kbits as rate/ceil, at this rate I must put the prio to have some good
results.
Doing more tests, I didn't know HTB was so sensitive to the max rate/ceil...
I'll post later on.
Ok I tested the shaping on the SDSL line with netperf and
an host outside.
Same script than before, I classify the packets into qdisc based on the
source address in netfilter and here are the result, that's with sfq.
I'm positive on the right traffic going to the right class.
TCP STREAM TEST to
:)
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
De la part de Gael Mauleon
Envoyé : mercredi 13 juillet 2005 12:26
À : lartc@mailman.ds9a.nl
Objet : RE: [LARTC] HTB Rate and Prio (continued)
Ok I tested the shaping on the SDSL line with netperf and
an host outside
Gael Mauleon wrote:
Ok I tested the shaping on the SDSL line with netperf and
an host outside.
Same script than before, I classify the packets into qdisc based on the
source address in netfilter and here are the result, that's with sfq.
I'm positive on the right traffic going to the right
Andy Furniss wrote:
add 70k bfifos to the classes - you shouldn't drop any packets then.
Maybe 100k just to be safe 70k may be a bit close once you take into
account the headers.
Andy.
___
LARTC mailing list
LARTC@mailman.ds9a.nl
I had a go with what you posted there over lan and with 2 tcp streams it
behaves as expected (see below for exact test).
Can you reproduce the failiure shaping over a lan rather than your
internet connection?
If your upstream bandwidth is sold as 2meg then ceil 2000kbit is likely
to be
Gael Mauleon wrote:
Hi again,
I keep posting about my problem with HTB -
http://mailman.ds9a.nl/pipermail/lartc/2005q3/016611.html
I had a go with what you posted there over lan and with 2 tcp streams it
behaves as expected (see below for exact test).
Can you reproduce the failiure
