While this is not too helpful, it might give some hints for bql-42, as from the roadmap I take it you will tackle the dsl issue there. I am just about to move and switch from DSL to cable internet, so unfortunately this might be my last test…

(BTW, I have been playing with the -s option of ping to change the payload size and for my measly 3008kbps down, 512kbps up connection I can actually see the 48 byte ATM package boundaries in avg RTTs (-c 100), for each new ATM package I roughly get 1ms added to the RTT (as expected when doing the math the my line rate). So I think it should be possible to figure out whether a link uses ATM as carrier or not (IIRC newer ADSL systems like AT&T's verse HSI use ADSL2 over PTM-TC instead of ATM so touch connections still have per package overhead to account for but lack the weird ATM repack issues). 
	I also have a hunch that using this method it should be possible to deduct a link's overhead (as taken understood by tc's step option) from a properly prepared ping sweep. In other words my hypothesis is that it should be possible to run a script on a non-shaped idle link and figure out the optimal parameters for stab. But I digress… (And alas, in two days my DSL connection will be gone and I can not even test my hypothesis in any meaningful way until then...))


best
	Sebastian





On Feb 14, 2012, at 11:53 AM, Dave Taht wrote:

> http://huchra.bufferbloat.net/~cero1/bql-smoketests/bql-40/
> 
> changes in this release:
> 
> kernel 3.3-rc3
> bind 9.9rc2
> ntpd + dnssec removed (too buggy)
> snmpd installed by default
> fprobe installed by default
> avahi installed by default
> 
> sort of better working 'aqm' shaper installed
> ** when configured uses hfsc + sfqred
> ** still has trouble with ipv6, diffserv, and tcp elephants
> ** no adsl overhead support
> 
> I will be travelling later this week. What I'm mostly
> working on right now is better ipv6 support.
> 
> -- 
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> FR Tel: 0638645374
> http://www.bufferbloat.net
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel