> >Ok... > >Using your script gave the following (from 17:30 onwards): > > > >http://www.overclockers.com.au/~mwp/temp/tc-1hour-yours.png > > This is strange I just tested again and it works for me. > > http://www.jessingale.dsl.pipex.com/tc-speed-1.png > > Blue is lowest with rate 20kbit green next low with 40kbit Red highest. The result your getting is exactly what im after. So whats different with what im doing... hrm. > It may be worth trying with ceils even lower - just incase you get radsl > adaption and don't really have the bandwidth. Nah, i have firm 256kbit up. > I suppose you should also use tc from new iproute2 that matches your kernel. Ok, where is the correct place to get it from? I havnt been able to find the official "release site" for iproute2. > rrdtool seems complicated - I suppose it could be averaging strangely, I > used - > > #set -x > /usr/local/rrdtool-1.0.49/bin/rrdtool create tcstats1.rrd --step 10 \ > DS:cls21:COUNTER:30:U:U \ > DS:cls22:COUNTER:30:U:U \ > DS:cls23:COUNTER:30:U:U \ > RRA:AVERAGE:0.5:1:100 > > while [ 1 ] > do > C21=`tc -s qdisc ls dev ppp0 | grep "21:" -A 1 | grep Sent | > awk '{print $2}'` > C22=`tc -s qdisc ls dev ppp0 | grep "22:" -A 1 | grep Sent | > awk '{print $2}'` > C23=`tc -s qdisc ls dev ppp0 | grep "23:" -A 1 | grep Sent | > awk '{print $2}'` > /usr/local/rrdtool-1.0.49/bin/rrdtool update tcstats1.rrd > N:$C21:$C22:$C23 > sleep 10 > done Thats very similar to what im doing, nothing too complex about it. I also know the graph is correct as the estimated rates from TC are the same as shown on the graph. So this is becoming an unknown problem? Thanks. Mark Williams. _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
