Philipp Leusmann wrote:
-----Ursprüngliche Nachricht-----
Von: lartc-bounces@xxxxxxxxxxxxxxx [mailto:lartc-bounces@xxxxxxxxxxxxxxx]
Im Auftrag von Andy Furniss
Gesendet: Sonntag, 12. November 2006 21:51
An: Philipp Leusmann
Cc: lartc@xxxxxxxxxxxxxxx
Betreff: Re: Why did I need strange ceiling settings? (full
version)
Philipp Leusmann wrote:
You will need to back off from the rates more and use kbit of course.
tc qdisc add dev $IFACE root handle 1:0 htb default 103
default is bad if $IFACE is eth your arp will go here, also if eth
Quantum should be set to ip mtu + 14.
$IFACE is ppp0. Does this make difference?
Yes - using htb default is safe on ppp and quantum doesn't need 14
adding. One caveat, if you get ppp MTU by script what if mtu on ppp is
really big - my old ISP used to ask (during ppp negotiation) for mru of
about 32k (aal5 mtu), which meant that mtu on the ppp was set to 32k.
And you would recommend to use no backup at all?
Had it been eth then you could have made a catch all ip filter with
lower prio to get anything else. You could also have made a filter for
arp/other non ip - but if non ip trafic levels are low I would just let
them through unshaped, which is what htb does if you don't specify a
default class / use default 0. (hfsc is the opposite - unclassified gets
dropped by default).
Try setting uprate ceil to 600kbit and make sure the sum of rates
doesn't exceed it.
Upload for a few minutes and while still uploading do -
tc -s -d class ls dev ppp0
and post the output.
Andy.
post the output
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
