Hi andy,
I reset the ceiling to 600kbit and get same same bad results as before. Also
I set all classes to use the same quantum which is mtu (it is 1488 here).
Here is the output you requested:
miles:~# tc -s -d class ls dev ppp0
class htb 1:101 parent 1:1 leaf 8019: prio 0 quantum 1488 rate 150000bit
ceil 600000bit burst 1674b/8 mpu 0b overhead 0b cburst 1899b/8 mpu 0b
overhead 0b level 0
Sent 130659 bytes 806 pkts (dropped 0, overlimits 0)
rate 224bit
lended: 632 borrowed: 174 giants: 0
tokens: 84164 ctokens: 24117
class htb 1:1 root rate 600000bit ceil 600000bit burst 1899b/8 mpu 0b
overhead 0b cburst 1899b/8 mpu 0b overhead 0b level 7
Sent 27239843 bytes 29309 pkts (dropped 0, overlimits 0)
rate 286640bit 34pps
lended: 16484 borrowed: 0 giants: 0
tokens: -66101 ctokens: -66101
class htb 1:103 parent 1:1 leaf 801b: prio 2 quantum 1488 rate 250000bit
ceil 600000bit burst 1724b/8 mpu 0b overhead 0b cburst 1899b/8 mpu 0b
overhead 0b level 0
Sent 27111784 bytes 28505 pkts (dropped 0, overlimits 0)
rate 286232bit 34pps backlog 2p
lended: 12193 borrowed: 16310 giants: 0
tokens: -83395 ctokens: -41934
class htb 1:102 parent 1:1 leaf 801a: prio 1 quantum 1488 rate 150000bit
ceil 600000bit burst 1674b/8 mpu 0b overhead 0b cburst 1899b/8 mpu 0b
overhead 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 91601 ctokens: 25976
class htb 1:104 parent 1:1 leaf 801c: prio 3 quantum 1488 rate 50000bit ceil
200000bit burst 1624b/8 mpu 0b overhead 0b cburst 1699b/8 mpu 0b overhead 0b
level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 266600 ctokens: 69726
I hope this helps to track down the problem.
Thanks,
Philipp
> -----Ursprüngliche Nachricht-----
> Von: lartc-bounces@mailman.ds9a.nl [mailto:lartc-bounces@mailman.ds9a.nl]
> Im Auftrag von Andy Furniss
> Gesendet: Dienstag, 14. November 2006 00:50
> An: Philipp Leusmann
> Cc: lartc@mailman.ds9a.nl
> Betreff: Re: AW: [LARTC] Why did I need strange ceiling settings? (full
> version)
>
> Philipp Leusmann wrote:
> >
> >>-----Ursprüngliche Nachricht-----
> >>Von: lartc-bounces@mailman.ds9a.nl [mailto:lartc-
> bounces@mailman.ds9a.nl]
> >>Im Auftrag von Andy Furniss
> >>Gesendet: Sonntag, 12. November 2006 21:51
> >>An: Philipp Leusmann
> >>Cc: lartc@mailman.ds9a.nl
> >>Betreff: Re: [LARTC] 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@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
|