[Cerowrt-devel] smoketest BQL-40 is out

[Cerowrt-devel] smoketest BQL-40 is out

[Dave Taht]

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

Re: [Cerowrt-devel] smoketest BQL-40 is out

[Sebastian Moeller]

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

Hi Dave,

I finally got around to update from rc6 to bql-40, to try the ATM shaping. The update was a breeze, great work!
	I am sad to report that for my ATM link AQM does not work for me as well as QoS does. My measurement consists out of using ping to get the RTT to the first ISP hop (as taken from trace route) while concurrently saturating the up link with a dropbox upload (which I usually give that a headstart of 10 seconds to go into bandwidth ceiling): AQM gives the same bad avg RTT of 1.2 seconds as no shaping at all does, while QoS gives me an avg RTT of around 24ms (best case RTT is around 13ms on my link, so the link stays pretty useable).
	I tried to apply the same changes to /usr/lib/aqm/generate.sh and /usr/lib/qos/generate.sh to make the them better understand the peculiarities of my ATM adsl1 connection, but it seems I did something wrong for the AQM script since my change does not have any effect there… (both modified files attached). I usually only  shape up- and down-stream to 97% of the line rate, which works ok with QoS. (And all my tests have been done, very unscientifically, using my mac laptop over the 5GHz wireless band of the router… )


[-- Attachment #2: generate.sh.aqm --]
[-- Type: application/octet-stream, Size: 14728 bytes --]

#!/bin/sh
[ -e /etc/functions.sh ] && . /etc/functions.sh || . ./functions.sh
[ -x /sbin/modprobe ] && {
	insmod="modprobe"
	rmmod="$insmod -r"
} || {
	insmod="insmod"
	rmmod="rmmod"
}

add_insmod() {
	eval "export isset=\${insmod_$1}"
	case "$isset" in
		1) ;;
		*) {
			[ "$2" ] && append INSMOD "$rmmod $1 >&- 2>&-" "$N"
			append INSMOD "$insmod $* >&- 2>&-" "$N"; export insmod_$1=1
		};;
	esac
}

[ -e /etc/config/network ] && {
	# only try to parse network config on openwrt

	find_ifname() {(
		reset_cb
		include /lib/network
		scan_interfaces
		config_get "$1" ifname
	)}
} || {
	find_ifname() {
		echo "Interface not found."
		exit 1
	}
}

parse_matching_rule() {
	local var="$1"
	local section="$2"
	local options="$3"
	local prefix="$4"
	local suffix="$5"
	local proto="$6"
	local mport=""
	local ports=""

	append "$var" "$prefix" "$N"
	for option in $options; do
		case "$option" in
			proto) config_get value "$section" proto; proto="${proto:-$value}";;
		esac
	done
	config_get type "$section" TYPE
	case "$type" in
		classify) unset pkt; append "$var" "-m mark --mark 0/0xff";;
		default) pkt=1; append "$var" "-m mark --mark 0/0xff";;
		reclassify) pkt=1;;
	esac
	append "$var" "${proto:+-p $proto}"
	for option in $options; do
		config_get value "$section" "$option"
		
		case "$pkt:$option" in
			*:srchost)
				append "$var" "-s $value"
			;;
			*:dsthost)
				append "$var" "-d $value"
			;;
			*:layer7)
				add_insmod ipt_layer7
				add_insmod xt_layer7
				append "$var" "-m layer7 --l7proto $value${pkt:+ --l7pkt}"
			;;
			*:ports|*:srcports|*:dstports)
				value="$(echo "$value" | sed -e 's,-,:,g')"
				lproto=${lproto:-tcp}
				case "$proto" in
					""|tcp|udp) append "$var" "-m ${proto:-tcp -p tcp} -m multiport";;
					*) unset "$var"; return 0;;
				esac
				case "$option" in
					ports)
						config_set "$section" srcports ""
						config_set "$section" dstports ""
						config_set "$section" portrange ""
						append "$var" "--ports $value"
					;;
					srcports)
						config_set "$section" ports ""
						config_set "$section" dstports ""
						config_set "$section" portrange ""
						append "$var" "--sports $value"
					;;
					dstports)
						config_set "$section" ports ""
						config_set "$section" srcports ""
						config_set "$section" portrange ""
						append "$var" "--dports $value"
					;;
				esac
				ports=1
			;;
			*:portrange)
				config_set "$section" ports ""
				config_set "$section" srcports ""
				config_set "$section" dstports ""
				value="$(echo "$value" | sed -e 's,-,:,g')"
				case "$proto" in
					""|tcp|udp) append "$var" "-m ${proto:-tcp -p tcp} --sport $value --dport $value";;
					*) unset "$var"; return 0;;
				esac
				ports=1
			;;
			*:connbytes)
				value="$(echo "$value" | sed -e 's,-,:,g')"
				add_insmod ipt_connbytes
				append "$var" "-m connbytes --connbytes $value --connbytes-dir both --connbytes-mode bytes"
			;;
			*:tos)
                                add_insmod ipt_tos
                                case "$value" in
                                        !*) append "$var" "-m tos ! --tos $value";;
                                        *) append "$var" "-m tos --tos $value"
                                esac
                        ;;
			*:dscp)
                                add_insmod ipt_dscp
				dscp_option="--dscp"
                                [ -z "${value%%[EBCA]*}" ] && dscp_option="--dscp-class"
				case "$value" in
                                       	!*) append "$var" "-m dscp ! $dscp_option $value";;
                                       	*) append "$var" "-m dscp $dscp_option $value"
                                esac
                        ;;
			*:direction)
				value="$(echo "$value" | sed -e 's,-,:,g')"
				if [ "$value" = "out" ]; then
					append "$var" "-o $device"
				elif [ "$value" = "in" ]; then
					append "$var" "-i $device"
				fi
			;;
			1:pktsize)
				value="$(echo "$value" | sed -e 's,-,:,g')"
				add_insmod ipt_length
				append "$var" "-m length --length $value"
			;;
			1:limit)
				add_insmod ipt_limit
				append "$var" "-m limit --limit $value"
			;;
			1:tcpflags)
				case "$proto" in
					tcp) append "$var" "-m tcp --tcp-flags ALL $value";;
					*) unset $var; return 0;;
				esac
			;;
			1:mark)
				config_get class "${value##!}" classnr
				[ -z "$class" ] && continue;
				case "$value" in
					!*) append "$var" "-m mark ! --mark $class/0xff";;
					*) append "$var" "-m mark --mark $class/0xff";;
				esac
			;;
			1:TOS)
				add_insmod ipt_TOS
				config_get TOS "$rule" 'TOS'
				suffix="-j TOS --set-tos "${TOS:-"Normal-Service"}
			;;
			1:DSCP)
				add_insmod ipt_DSCP
				config_get DSCP "$rule" 'DSCP'
				[ -z "${DSCP%%[EBCA]*}" ] && set_value="--set-dscp-class $DSCP" \
				|| set_value="--set-dscp $DSCP"
				suffix="-j DSCP $set_value"
			;;
		esac
	done
	append "$var" "$suffix"
	case "$ports:$proto" in
		1:)	parse_matching_rule "$var" "$section" "$options" "$prefix" "$suffix" "udp";;
	esac
}

config_cb() {
	option_cb() {
		return 0
	}

	# Section start
	case "$1" in
		interface)
			config_set "$2" "classgroup" "Default"
			config_set "$2" "upload" "128"
		;;
		classify|default|reclassify)
			option_cb() {
				append options "$1"
			}
		;;
	esac

    # Section end
	config_get TYPE "$CONFIG_SECTION" TYPE
	case "$TYPE" in
		interface)
			config_get_bool enabled "$CONFIG_SECTION" enabled 1
			[ 1 -eq "$enabled" ] || return 0
			config_get classgroup "$CONFIG_SECTION" classgroup
			config_set "$CONFIG_SECTION" ifbdev "$C"
			C=$(($C+1))
			append INTERFACES "$CONFIG_SECTION"
			config_set "$classgroup" enabled 1
			config_get device "$CONFIG_SECTION" device
			[ -z "$device" ] && {
				device="$(find_ifname ${CONFIG_SECTION})"
				config_set "$CONFIG_SECTION" device "${device:-eth0}"
			}
		;;
		classgroup) append CG "$CONFIG_SECTION";;
		classify|default|reclassify)
			case "$TYPE" in
				classify) var="ctrules";;
				*) var="rules";;
			esac
			config_get target "$CONFIG_SECTION" target
			config_set "$CONFIG_SECTION" options "$options"
			append "$var" "$CONFIG_SECTION"
			unset options
		;;
	esac
}


enum_classes() {
	local c="0"
	config_get classes "$1" classes
	config_get default "$1" default
	for class in $classes; do
		c="$(($c + 1))"
		config_set "${class}" classnr $c
		case "$class" in
			$default) class_default=$c;;
		esac
	done
	class_default="${class_default:-$c}"
}

cls_var() {
	local varname="$1"
	local class="$2"
	local name="$3"
	local type="$4"
	local default="$5"
	local tmp tmp1 tmp2
	config_get tmp1 "$class" "$name"
	config_get tmp2 "${class}_${type}" "$name"
	tmp="${tmp2:-$tmp1}"
	tmp="${tmp:-$tmp2}"
	export ${varname}="${tmp:-$default}"
}

tcrules() {
	dir=/usr/lib/aqm
	[ -e $dir/tcrules.awk ] || dir=.
	echo "$cstr" | awk \
		-v device="$dev" \
		-v linespeed="$rate" \
		-f $dir/tcrules.awk
}

start_interface() {
	local iface="$1"
	local num_ifb="$2"
	tc_stab_string="stab overhead 18 mtu 2048 mpu 53 linklayer atm"
	config_get device "$iface" device
	config_get_bool enabled "$iface" enabled 1
	[ -z "$device" -o 1 -ne "$enabled" ] && {
		return 1 
	}
	config_get upload "$iface" upload
	config_get_bool halfduplex "$iface" halfduplex
	config_get download "$iface" download
	config_get classgroup "$iface" classgroup
	config_get_bool overhead "$iface" overhead 0
	
	download="${download:-${halfduplex:+$upload}}"
	enum_classes "$classgroup"
	for dir in ${halfduplex:-up} ${download:+down}; do
		case "$dir" in
			up)
				[ "$overhead" = 1 ] && upload=$(($upload * 98 / 100 - (15 * 128 / $upload)))
				dev="$device"
				rate="$upload"
				dl_mode=""
				prefix="cls"
			;;
			down)
				[ "$(ls -d /proc/sys/net/ipv4/conf/ifb* 2>&- | wc -l)" -ne "$num_ifb" ] && add_insmod ifb numifbs="$num_ifb"
				config_get ifbdev "$iface" ifbdev
				[ "$overhead" = 1 ] && download=$(($download * 98 / 100 - (80 * 1024 / $download)))
				dev="ifb$ifbdev"
				rate="$download"
				dl_mode=1
				prefix="d_cls"
			;;
			*) continue;;
		esac
		cstr=
		for class in $classes; do
			cls_var pktsize "$class" packetsize $dir 1500
			cls_var pktdelay "$class" packetdelay $dir 0
			cls_var maxrate "$class" limitrate $dir 100
			cls_var prio "$class" priority $dir 1
			cls_var avgrate "$class" avgrate $dir 0
			cls_var qdisc "$class" qdisc $dir ""
			cls_var filter "$class" filter $dir ""
			config_get classnr "$class" classnr
			append cstr "$classnr:$prio:$avgrate:$pktsize:$pktdelay:$maxrate:$qdisc:$filter" "$N"
		done
		append ${prefix}q "$(tcrules)" "$N"
		export dev_${dir}="ifconfig $dev up txqueuelen 5 >&- 2>&-
tc qdisc del dev $dev root >&- 2>&-
tc qdisc add dev $dev root handle 1: ${tc_stab_string} hfsc default ${class_default}0
tc class add dev $dev parent 1: classid 1:1 hfsc sc rate ${rate}kbit ul rate ${rate}kbit"
	done
	[ -n "$download" ] && {
		add_insmod cls_u32
		add_insmod em_u32
		add_insmod act_connmark
		add_insmod act_mirred
		add_insmod sch_ingress
	}
	if [ -n "$halfduplex" ]; then
		export dev_up="tc qdisc del dev $device root >&- 2>&-
tc qdisc add dev $device root handle 1: ${tc_stab_string} hfsc
tc filter add dev $device parent 1: protocol ipv6 prio 9 u32 match u32 0 0 flowid 1:1 action mirred egress redirect dev ifb$ifbdev"
tc filter add dev $device parent 1: protocol ip prio 10 u32 match u32 0 0 flowid 1:1 action mirred egress redirect dev ifb$ifbdev"
	elif [ -n "$download" ]; then
		append dev_${dir} "tc qdisc del dev $device ingress >&- 2>&-
tc qdisc add dev $device ${tc_stab_string} ingress
tc filter add dev $device parent ffff: protocol ipv6 prio 1 u32 match u32 0 0 flowid 1:1 action connmark action mirred egress redirect dev ifb$ifbdev" "$N"
tc filter add dev $device parent ffff: protocol ip prio 2 u32 match u32 0 0 flowid 1:1 action connmark action mirred egress redirect dev ifb$ifbdev" "$N"
	fi
	add_insmod cls_fw
	add_insmod sch_hfsc
	add_insmod sch_sfq
	add_insmod sch_red

	cat <<EOF
${INSMOD:+$INSMOD$N}${dev_up:+$dev_up
$clsq
}${ifbdev:+$dev_down
$d_clsq
$d_clsl
$d_clsf
}
EOF
	unset INSMOD clsq clsf clsl d_clsq d_clsl d_clsf dev_up dev_down
}

start_interfaces() {
	local C="$1"
	for iface in $INTERFACES; do
		start_interface "$iface" "$C"
	done
}

add_rules() {
	local var="$1"
	local rules="$2"
	local prefix="$3"
	
	for rule in $rules; do
		unset iptrule
		config_get target "$rule" target
		config_get target "$target" classnr
		config_get options "$rule" options

		## If we want to override the TOS field, let's clear the DSCP field first.
		[ ! -z "$(echo $options | grep 'TOS')" ] && {
			s_options=${options%%TOS}
			add_insmod ipt_DSCP
			parse_matching_rule iptrule "$rule" "$s_options" "$prefix" "-j DSCP --set-dscp 0"
			append "$var" "$iptrule" "$N"
			unset iptrule
		}

		parse_matching_rule iptrule "$rule" "$options" "$prefix" "-j MARK --set-mark $target/0xff"
		append "$var" "$iptrule" "$N"
	done
}

start_cg() {
	local cg="$1"
	local iptrules
	local pktrules
	local sizerules
	enum_classes "$cg"
	add_rules iptrules "$ctrules" "iptables -t mangle -A qos_${cg}_ct"
	add_rules iptrules "$ctrules" "ip6tables -t mangle -A qos_${cg}_ct"
	config_get classes "$cg" classes
	for class in $classes; do
		config_get mark "$class" classnr
		config_get maxsize "$class" maxsize
		[ -z "$maxsize" -o -z "$mark" ] || {
			add_insmod ipt_length
			append pktrules "iptables -t mangle -A qos_${cg} -m mark --mark $mark/0xff -m length --length $maxsize: -j MARK --set-mark 0/0xff" "$N"
			append pktrules "ip6tables -t mangle -A qos_${cg} -m mark --mark $mark/0xff -m length --length $maxsize: -j MARK --set-mark 0/0xff" "$N"
		}
	done
	add_rules pktrules "$rules" "iptables -t mangle -A qos_${cg}"
	for iface in $INTERFACES; do
		config_get classgroup "$iface" classgroup
		config_get device "$iface" device
		config_get ifbdev "$iface" ifbdev
		config_get upload "$iface" upload
		config_get download "$iface" download
		config_get halfduplex "$iface" halfduplex
		download="${download:-${halfduplex:+$upload}}"
		append up "iptables -t mangle -A OUTPUT -o $device -j qos_${cg}" "$N"
		append up "iptables -t mangle -A FORWARD -o $device -j qos_${cg}" "$N"
		append up "ip6tables -t mangle -A OUTPUT -o $device -j qos_${cg}" "$N"
		append up "ip6tables -t mangle -A FORWARD -o $device -j qos_${cg}" "$N"
	done
	cat <<EOF
$INSMOD
iptables -t mangle -N qos_${cg} >&- 2>&-
iptables -t mangle -N qos_${cg}_ct >&- 2>&-
ip6tables -t mangle -N qos_${cg} >&- 2>&-
ip6tables -t mangle -N qos_${cg}_ct >&- 2>&-
${iptrules:+${iptrules}${N}iptables -t mangle -A qos_${cg}_ct -j CONNMARK --save-mark --mask 0xff}
${iptrules:+${iptrules}${N}ip6tables -t mangle -A qos_${cg}_ct -j CONNMARK --save-mark --mask 0xff}
iptables -t mangle -A qos_${cg} -j CONNMARK --restore-mark --mask 0xff
iptables -t mangle -A qos_${cg} -m mark --mark 0/0xff -j qos_${cg}_ct
ip6tables -t mangle -A qos_${cg} -j CONNMARK --restore-mark --mask 0xff
ip6tables -t mangle -A qos_${cg} -m mark --mark 0/0xff -j qos_${cg}_ct
$pktrules
$up$N${down:+${down}$N}
EOF
	unset INSMOD
}

start_firewall() {
	add_insmod ipt_multiport
	add_insmod ipt_CONNMARK
	stop_firewall
	for group in $CG; do
		start_cg $group
	done
}

stop_firewall() {
	# Builds up a list of iptables commands to flush the qos_* chains,
	# remove rules referring to them, then delete them

	# Print rules in the mangle table, like iptables-save
	iptables -t mangle -S |
		# Find rules for the qos_* chains
		grep '^-N qos_\|-j qos_' |
		# Exclude rules in qos_* chains (inter-qos_* refs)
		grep -v '^-A qos_' |
		# Replace -N with -X and hold, with -F and print
		# Replace -A with -D
		# Print held lines at the end (note leading newline)
		sed -e '/^-N/{s/^-N/-X/;H;s/^-X/-F/}' \
			-e 's/^-A/-D/' \
			-e '${p;g}' |
		# Make into proper iptables calls
		# Note:  awkward in previous call due to hold space usage
		sed -n -e 's/^./iptables -t mangle &/p'
	ip6tables -t mangle -S |
		# Find rules for the qos_* chains
		grep '^-N qos_\|-j qos_' |
		# Exclude rules in qos_* chains (inter-qos_* refs)
		grep -v '^-A qos_' |
		# Replace -N with -X and hold, with -F and print
		# Replace -A with -D
		# Print held lines at the end (note leading newline)
		sed -e '/^-N/{s/^-N/-X/;H;s/^-X/-F/}' \
			-e 's/^-A/-D/' \
			-e '${p;g}' |
		# Make into proper iptables calls
		# Note:  awkward in previous call due to hold space usage
		sed -n -e 's/^./ip6tables -t mangle &/p'
}

C="0"
INTERFACES=""
[ -e ./aqm.conf ] && {
	. ./aqm.conf
	config_cb
} || config_load aqm

C="0"
for iface in $INTERFACES; do
	export C="$(($C + 1))"
done

case "$1" in
	all)
		start_interfaces "$C"
		start_firewall
	;;
	interface)
		start_interface "$2" "$C"
	;;
	interfaces)
		start_interfaces
	;;
	firewall)
		case "$2" in
			stop)
				stop_firewall
			;;
			start|"")
				start_firewall
			;;
		esac
	;;
esac

[-- Attachment #3: generate.sh.qos --]
[-- Type: application/octet-stream, Size: 13240 bytes --]

#!/bin/sh
[ -e /etc/functions.sh ] && . /etc/functions.sh || . ./functions.sh
[ -x /sbin/modprobe ] && {
	insmod="modprobe"
	rmmod="$insmod -r"
} || {
	insmod="insmod"
	rmmod="rmmod"
}

add_insmod() {
	eval "export isset=\${insmod_$1}"
	case "$isset" in
		1) ;;
		*) {
			[ "$2" ] && append INSMOD "$rmmod $1 >&- 2>&-" "$N"
			append INSMOD "$insmod $* >&- 2>&-" "$N"; export insmod_$1=1
		};;
	esac
}

[ -e /etc/config/network ] && {
	# only try to parse network config on openwrt

	find_ifname() {(
		reset_cb
		include /lib/network
		scan_interfaces
		config_get "$1" ifname
	)}
} || {
	find_ifname() {
		echo "Interface not found."
		exit 1
	}
}

parse_matching_rule() {
	local var="$1"
	local section="$2"
	local options="$3"
	local prefix="$4"
	local suffix="$5"
	local proto="$6"
	local mport=""
	local ports=""

	append "$var" "$prefix" "$N"
	for option in $options; do
		case "$option" in
			proto) config_get value "$section" proto; proto="${proto:-$value}";;
		esac
	done
	config_get type "$section" TYPE
	case "$type" in
		classify) unset pkt; append "$var" "-m mark --mark 0/0xff";;
		default) pkt=1; append "$var" "-m mark --mark 0/0xff";;
		reclassify) pkt=1;;
	esac
	append "$var" "${proto:+-p $proto}"
	for option in $options; do
		config_get value "$section" "$option"
		
		case "$pkt:$option" in
			*:srchost)
				append "$var" "-s $value"
			;;
			*:dsthost)
				append "$var" "-d $value"
			;;
			*:layer7)
				add_insmod ipt_layer7
				add_insmod xt_layer7
				append "$var" "-m layer7 --l7proto $value${pkt:+ --l7pkt}"
			;;
			*:ports|*:srcports|*:dstports)
				value="$(echo "$value" | sed -e 's,-,:,g')"
				lproto=${lproto:-tcp}
				case "$proto" in
					""|tcp|udp) append "$var" "-m ${proto:-tcp -p tcp} -m multiport";;
					*) unset "$var"; return 0;;
				esac
				case "$option" in
					ports)
						config_set "$section" srcports ""
						config_set "$section" dstports ""
						config_set "$section" portrange ""
						append "$var" "--ports $value"
					;;
					srcports)
						config_set "$section" ports ""
						config_set "$section" dstports ""
						config_set "$section" portrange ""
						append "$var" "--sports $value"
					;;
					dstports)
						config_set "$section" ports ""
						config_set "$section" srcports ""
						config_set "$section" portrange ""
						append "$var" "--dports $value"
					;;
				esac
				ports=1
			;;
			*:portrange)
				config_set "$section" ports ""
				config_set "$section" srcports ""
				config_set "$section" dstports ""
				value="$(echo "$value" | sed -e 's,-,:,g')"
				case "$proto" in
					""|tcp|udp) append "$var" "-m ${proto:-tcp -p tcp} --sport $value --dport $value";;
					*) unset "$var"; return 0;;
				esac
				ports=1
			;;
			*:connbytes)
				value="$(echo "$value" | sed -e 's,-,:,g')"
				add_insmod ipt_connbytes
				append "$var" "-m connbytes --connbytes $value --connbytes-dir both --connbytes-mode bytes"
			;;
			*:tos)
                                add_insmod ipt_tos
                                case "$value" in
                                        !*) append "$var" "-m tos ! --tos $value";;
                                        *) append "$var" "-m tos --tos $value"
                                esac
                        ;;
			*:dscp)
                                add_insmod ipt_dscp
				dscp_option="--dscp"
                                [ -z "${value%%[EBCA]*}" ] && dscp_option="--dscp-class"
				case "$value" in
                                       	!*) append "$var" "-m dscp ! $dscp_option $value";;
                                       	*) append "$var" "-m dscp $dscp_option $value"
                                esac
                        ;;
			*:direction)
				value="$(echo "$value" | sed -e 's,-,:,g')"
				if [ "$value" = "out" ]; then
					append "$var" "-o $device"
				elif [ "$value" = "in" ]; then
					append "$var" "-i $device"
				fi
			;;
			1:pktsize)
				value="$(echo "$value" | sed -e 's,-,:,g')"
				add_insmod ipt_length
				append "$var" "-m length --length $value"
			;;
			1:limit)
				add_insmod ipt_limit
				append "$var" "-m limit --limit $value"
			;;
			1:tcpflags)
				case "$proto" in
					tcp) append "$var" "-m tcp --tcp-flags ALL $value";;
					*) unset $var; return 0;;
				esac
			;;
			1:mark)
				config_get class "${value##!}" classnr
				[ -z "$class" ] && continue;
				case "$value" in
					!*) append "$var" "-m mark ! --mark $class/0xff";;
					*) append "$var" "-m mark --mark $class/0xff";;
				esac
			;;
			1:TOS)
				add_insmod ipt_TOS
				config_get TOS "$rule" 'TOS'
				suffix="-j TOS --set-tos "${TOS:-"Normal-Service"}
			;;
			1:DSCP)
				add_insmod ipt_DSCP
				config_get DSCP "$rule" 'DSCP'
				[ -z "${DSCP%%[EBCA]*}" ] && set_value="--set-dscp-class $DSCP" \
				|| set_value="--set-dscp $DSCP"
				suffix="-j DSCP $set_value"
			;;
		esac
	done
	append "$var" "$suffix"
	case "$ports:$proto" in
		1:)	parse_matching_rule "$var" "$section" "$options" "$prefix" "$suffix" "udp";;
	esac
}

config_cb() {
	option_cb() {
		return 0
	}

	# Section start
	case "$1" in
		interface)
			config_set "$2" "classgroup" "Default"
			config_set "$2" "upload" "128"
		;;
		classify|default|reclassify)
			option_cb() {
				append options "$1"
			}
		;;
	esac

    # Section end
	config_get TYPE "$CONFIG_SECTION" TYPE
	case "$TYPE" in
		interface)
			config_get_bool enabled "$CONFIG_SECTION" enabled 1
			[ 1 -eq "$enabled" ] || return 0
			config_get classgroup "$CONFIG_SECTION" classgroup
			config_set "$CONFIG_SECTION" ifbdev "$C"
			C=$(($C+1))
			append INTERFACES "$CONFIG_SECTION"
			config_set "$classgroup" enabled 1
			config_get device "$CONFIG_SECTION" device
			[ -z "$device" ] && {
				device="$(find_ifname ${CONFIG_SECTION})"
				config_set "$CONFIG_SECTION" device "${device:-eth0}"
			}
		;;
		classgroup) append CG "$CONFIG_SECTION";;
		classify|default|reclassify)
			case "$TYPE" in
				classify) var="ctrules";;
				*) var="rules";;
			esac
			config_get target "$CONFIG_SECTION" target
			config_set "$CONFIG_SECTION" options "$options"
			append "$var" "$CONFIG_SECTION"
			unset options
		;;
	esac
}


enum_classes() {
	local c="0"
	config_get classes "$1" classes
	config_get default "$1" default
	for class in $classes; do
		c="$(($c + 1))"
		config_set "${class}" classnr $c
		case "$class" in
			$default) class_default=$c;;
		esac
	done
	class_default="${class_default:-$c}"
}

cls_var() {
	local varname="$1"
	local class="$2"
	local name="$3"
	local type="$4"
	local default="$5"
	local tmp tmp1 tmp2
	config_get tmp1 "$class" "$name"
	config_get tmp2 "${class}_${type}" "$name"
	tmp="${tmp2:-$tmp1}"
	tmp="${tmp:-$tmp2}"
	export ${varname}="${tmp:-$default}"
}

tcrules() {
	dir=/usr/lib/qos
	[ -e $dir/tcrules.awk ] || dir=.
	echo "$cstr" | awk \
		-v device="$dev" \
		-v linespeed="$rate" \
		-f $dir/tcrules.awk
}

start_interface() {
	tc_stab_string="stab overhead 18 mtu 2048 mpu 53 linklayer atm"
	local iface="$1"
	local num_ifb="$2"
	config_get device "$iface" device
	config_get_bool enabled "$iface" enabled 1
	[ -z "$device" -o 1 -ne "$enabled" ] && {
		return 1 
	}
	config_get upload "$iface" upload
	config_get_bool halfduplex "$iface" halfduplex
	config_get download "$iface" download
	config_get classgroup "$iface" classgroup
	config_get_bool overhead "$iface" overhead 0
	
	download="${download:-${halfduplex:+$upload}}"
	enum_classes "$classgroup"
	for dir in ${halfduplex:-up} ${download:+down}; do
		case "$dir" in
			up)
				[ "$overhead" = 1 ] && upload=$(($upload * 98 / 100 - (15 * 128 / $upload)))
				dev="$device"
				rate="$upload"
				dl_mode=""
				prefix="cls"
			;;
			down)
				[ "$(ls -d /proc/sys/net/ipv4/conf/ifb* 2>&- | wc -l)" -ne "$num_ifb" ] && add_insmod ifb numifbs="$num_ifb"
				config_get ifbdev "$iface" ifbdev
				[ "$overhead" = 1 ] && download=$(($download * 98 / 100 - (80 * 1024 / $download)))
				dev="ifb$ifbdev"
				rate="$download"
				dl_mode=1
				prefix="d_cls"
			;;
			*) continue;;
		esac
		cstr=
		for class in $classes; do
			cls_var pktsize "$class" packetsize $dir 1500
			cls_var pktdelay "$class" packetdelay $dir 0
			cls_var maxrate "$class" limitrate $dir 100
			cls_var prio "$class" priority $dir 1
			cls_var avgrate "$class" avgrate $dir 0
			cls_var qdisc "$class" qdisc $dir ""
			cls_var filter "$class" filter $dir ""
			config_get classnr "$class" classnr
			append cstr "$classnr:$prio:$avgrate:$pktsize:$pktdelay:$maxrate:$qdisc:$filter" "$N"
		done
		append ${prefix}q "$(tcrules)" "$N"
		export dev_${dir}="ifconfig $dev up txqueuelen 5 >&- 2>&-
tc qdisc del dev $dev root >&- 2>&-
tc qdisc add dev $dev root handle 1: ${tc_stab_string} hfsc default ${class_default}0
tc class add dev $dev parent 1: classid 1:1 hfsc sc rate ${rate}kbit ul rate ${rate}kbit"
	done
	[ -n "$download" ] && {
		add_insmod cls_u32
		add_insmod em_u32
		add_insmod act_connmark
		add_insmod act_mirred
		add_insmod sch_ingress
	}
	if [ -n "$halfduplex" ]; then
		export dev_up="tc qdisc del dev $device root >&- 2>&-
tc qdisc add dev $device root handle 1: ${tc_stab_string} hfsc
tc filter add dev $device parent 1: protocol ip prio 10 u32 match u32 0 0 flowid 1:1 action mirred egress redirect dev ifb$ifbdev"
	elif [ -n "$download" ]; then
		append dev_${dir} "tc qdisc del dev $device ingress >&- 2>&-
tc qdisc add dev $device ${tc_stab_string} ingress
tc filter add dev $device parent ffff: protocol ip prio 1 u32 match u32 0 0 flowid 1:1 action connmark action mirred egress redirect dev ifb$ifbdev" "$N"
	fi
	add_insmod cls_fw
	add_insmod sch_hfsc
	add_insmod sch_sfq
	add_insmod sch_red

	cat <<EOF
${INSMOD:+$INSMOD$N}${dev_up:+$dev_up
$clsq
}${ifbdev:+$dev_down
$d_clsq
$d_clsl
$d_clsf
}
EOF
	unset INSMOD clsq clsf clsl d_clsq d_clsl d_clsf dev_up dev_down
}

start_interfaces() {
	local C="$1"
	for iface in $INTERFACES; do
		start_interface "$iface" "$C"
	done
}

add_rules() {
	local var="$1"
	local rules="$2"
	local prefix="$3"
	
	for rule in $rules; do
		unset iptrule
		config_get target "$rule" target
		config_get target "$target" classnr
		config_get options "$rule" options

		## If we want to override the TOS field, let's clear the DSCP field first.
		[ ! -z "$(echo $options | grep 'TOS')" ] && {
			s_options=${options%%TOS}
			add_insmod ipt_DSCP
			parse_matching_rule iptrule "$rule" "$s_options" "$prefix" "-j DSCP --set-dscp 0"
			append "$var" "$iptrule" "$N"
			unset iptrule
		}

		parse_matching_rule iptrule "$rule" "$options" "$prefix" "-j MARK --set-mark $target/0xff"
		append "$var" "$iptrule" "$N"
	done
}

start_cg() {
	local cg="$1"
	local iptrules
	local pktrules
	local sizerules
	enum_classes "$cg"
	add_rules iptrules "$ctrules" "iptables -t mangle -A qos_${cg}_ct"
	config_get classes "$cg" classes
	for class in $classes; do
		config_get mark "$class" classnr
		config_get maxsize "$class" maxsize
		[ -z "$maxsize" -o -z "$mark" ] || {
			add_insmod ipt_length
			append pktrules "iptables -t mangle -A qos_${cg} -m mark --mark $mark/0xff -m length --length $maxsize: -j MARK --set-mark 0/0xff" "$N"
		}
	done
	add_rules pktrules "$rules" "iptables -t mangle -A qos_${cg}"
	for iface in $INTERFACES; do
		config_get classgroup "$iface" classgroup
		config_get device "$iface" device
		config_get ifbdev "$iface" ifbdev
		config_get upload "$iface" upload
		config_get download "$iface" download
		config_get halfduplex "$iface" halfduplex
		download="${download:-${halfduplex:+$upload}}"
		append up "iptables -t mangle -A OUTPUT -o $device -j qos_${cg}" "$N"
		append up "iptables -t mangle -A FORWARD -o $device -j qos_${cg}" "$N"
	done
	cat <<EOF
$INSMOD
iptables -t mangle -N qos_${cg} >&- 2>&-
iptables -t mangle -N qos_${cg}_ct >&- 2>&-
${iptrules:+${iptrules}${N}iptables -t mangle -A qos_${cg}_ct -j CONNMARK --save-mark --mask 0xff}
iptables -t mangle -A qos_${cg} -j CONNMARK --restore-mark --mask 0xff
iptables -t mangle -A qos_${cg} -m mark --mark 0/0xff -j qos_${cg}_ct
$pktrules
$up$N${down:+${down}$N}
EOF
	unset INSMOD
}

start_firewall() {
	add_insmod ipt_multiport
	add_insmod ipt_CONNMARK
	stop_firewall
	for group in $CG; do
		start_cg $group
	done
}

stop_firewall() {
	# Builds up a list of iptables commands to flush the qos_* chains,
	# remove rules referring to them, then delete them

	# Print rules in the mangle table, like iptables-save
	iptables -t mangle -S |
		# Find rules for the qos_* chains
		grep '^-N qos_\|-j qos_' |
		# Exclude rules in qos_* chains (inter-qos_* refs)
		grep -v '^-A qos_' |
		# Replace -N with -X and hold, with -F and print
		# Replace -A with -D
		# Print held lines at the end (note leading newline)
		sed -e '/^-N/{s/^-N/-X/;H;s/^-X/-F/}' \
			-e 's/^-A/-D/' \
			-e '${p;g}' |
		# Make into proper iptables calls
		# Note:  awkward in previous call due to hold space usage
		sed -n -e 's/^./iptables -t mangle &/p'
}

C="0"
INTERFACES=""
[ -e ./qos.conf ] && {
	. ./qos.conf
	config_cb
} || config_load qos

C="0"
for iface in $INTERFACES; do
	export C="$(($C + 1))"
done

case "$1" in
	all)
		start_interfaces "$C"
		start_firewall
	;;
	interface)
		start_interface "$2" "$C"
	;;
	interfaces)
		start_interfaces
	;;
	firewall)
		case "$2" in
			stop)
				stop_firewall
			;;
			start|"")
				start_firewall
			;;
		esac
	;;
esac

[-- Attachment #4: Type: text/plain, Size: 2262 bytes --]



	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

Re: [Cerowrt-devel] smoketest BQL-40 is out

[Dave Taht]

I'm aware there are several messages in
the backlog I need to respond to, but I am travelling
at the moment and eyeball deep in meetings. (presently in NJ,
next week philly, and then I get back to the bloatlab in isc
in california friday-ish.

As best as I recall there was no real difference between
the AQM script and the QoS script in bql-40, and I may
not get around to doing a 'bql-42' per se' but go right
into the 3.3 development process.

This will not be the final url for the 3.3 development
series, but

http://huchra.bufferbloat.net/~cero1/3.3/

has that.

I made a small dent in the qos/aqm problem there,
(my intent was to basically treat the above as 'bql-41' -
 I wanted to treat 3.3 issues and bql issues separately,
 but lack time to do both, and 3.3 is going swimmingly, so...)

but I'm puzzled as to what you are seeing below.

0) Did you enable the aqm script? If you merely run it
without enabling it, nothing happens. Similarly, the qos script
needs to be disabled.

1) Neither the AQM nor qos script does ADSL overhead right,
and I'd got puzzled on what was 'right' after fiddling with it.

2) both qos and aqm calculated the sfq 'limit' variable wrong, and
neither did ipv6 work right at all.

I believe, but don't remember, that at least those fixes got made in
the 3.3rc4-1 code. Actually there's a better fix for the ipv6 issue
than what's there...

3) I am not intending to stick with the aqm script as structured now,
but to finish modifying the 'debloat' script to have all the features required.

that one has a bunch of semi-working queue models in it.

If yer gonna hack scripts, please take a look at that one.
There are plenty of things it needs and the qos and aqm scripts
are more feature complete, tho...

4) re updates: I have to warn against doing sysupgrade "and keep files
in place", as the based filesystem does change, and I'm not making
huge attempts at dealing with that. so doing a backup
then a sysupdate -n (-n meaning don't preserve files over the backup)
is generally a good idea.

anyway:

commit be09b8c15b6dc6bf4cb7da3112c598138a9c77ef
Author: Dave Taht <dave.taht@bufferbloat.net>
Date:   Tue Feb 14 14:38:40 2012 +0000

    SFQ is limited in packets. RED is in bytes. tcrules.awk conflated these

    The original openwrt shaper took the RED byte calculation...
    and reused it to specify a limit for sfq. However, sfq uses
    packets rather than bytes, so it was specifying, say 16000 bytes
    and translating that to 16000 packets.

    This was not an error I prior to 3.3, because SFQ had a
    hard coded limit of 127 packets. It is now.

    So this commit puts a lower and upper bound on the maximum packets
    that is sane, but is not pre 3.2 compatible.

commit 44f8febbd34686564516c3261a911bd7cffcf714


On Thu, Feb 23, 2012 at 6:21 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Dave,
>
> I finally got around to update from rc6 to bql-40, to try the ATM shaping. The update was a breeze, great work!
>        I am sad to report that for my ATM link AQM does not work for me as well as QoS does. My measurement consists out of using ping to get the RTT to the first ISP hop (as taken from trace route) while concurrently saturating the up link with a dropbox upload (which I usually give that a headstart of 10 seconds to go into bandwidth ceiling): AQM gives the same bad avg RTT of 1.2 seconds as no shaping at all does, while QoS gives me an avg RTT of around 24ms (best case RTT is around 13ms on my link, so the link stays pretty useable).
>        I tried to apply the same changes to /usr/lib/aqm/generate.sh and /usr/lib/qos/generate.sh to make the them better understand the peculiarities of my ATM adsl1 connection, but it seems I did something wrong for the AQM script since my change does not have any effect there… (both modified files attached). I usually only  shape up- and down-stream to 97% of the line rate, which works ok with QoS. (And all my tests have been done, very unscientifically, using my mac laptop over the 5GHz wireless band of the router… )
>
>
>
>
>        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
>
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

Re: [Cerowrt-devel] smoketest BQL-40 is out

[Dave Taht]

A couple quick notes:

1) I had hoped that the kernel development phase was over, and all I'd
have to do is track the 3.3 rcs from linus and keep up with openwrt's
churn...

It is looking like a few more mods to iptables and tc are going to be
required over the next month or two to get things right.

2) That said, most of what remains is scripting and 'glue', and it
will generally be possible to install a package under test on an
existing box without having to reflash the whole thing and
reconfigure. For example, you can pull the new aqm-script package from
either the git repository or the current 3.3 build - an example of the
latter would be:

cd /tmp
opkg remove aqm-scripts
wget http://huchra.bufferbloat.net/~cero1/3.3/3.3-rc4-1/packages/aqm-scripts_1.2.1-6_all.ipk
opkg install ./aqm-scrip*

right now anyway! (see item 1)

It would improve our cycle time to schedule and focus on each
scripting problem, perhaps in irc, for things like the ADSL problem.

Regrettably I'm not in a position to do any real work on that this week.

On Thu, Feb 23, 2012 at 10:49 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I'm aware there are several messages in
> the backlog I need to respond to, but I am travelling
> at the moment and eyeball deep in meetings. (presently in NJ,
> next week philly, and then I get back to the bloatlab in isc
> in california friday-ish.
>
> As best as I recall there was no real difference between
> the AQM script and the QoS script in bql-40, and I may
> not get around to doing a 'bql-42' per se' but go right
> into the 3.3 development process.
>
> This will not be the final url for the 3.3 development
> series, but
>
> http://huchra.bufferbloat.net/~cero1/3.3/
>
> has that.
>
> I made a small dent in the qos/aqm problem there,
> (my intent was to basically treat the above as 'bql-41' -
>  I wanted to treat 3.3 issues and bql issues separately,
>  but lack time to do both, and 3.3 is going swimmingly, so...)
>
> but I'm puzzled as to what you are seeing below.
>
> 0) Did you enable the aqm script? If you merely run it
> without enabling it, nothing happens. Similarly, the qos script
> needs to be disabled.
>
> 1) Neither the AQM nor qos script does ADSL overhead right,
> and I'd got puzzled on what was 'right' after fiddling with it.
>
> 2) both qos and aqm calculated the sfq 'limit' variable wrong, and
> neither did ipv6 work right at all.
>
> I believe, but don't remember, that at least those fixes got made in
> the 3.3rc4-1 code. Actually there's a better fix for the ipv6 issue
> than what's there...
>
> 3) I am not intending to stick with the aqm script as structured now,
> but to finish modifying the 'debloat' script to have all the features required.
>
> that one has a bunch of semi-working queue models in it.
>
> If yer gonna hack scripts, please take a look at that one.
> There are plenty of things it needs and the qos and aqm scripts
> are more feature complete, tho...
>
> 4) re updates: I have to warn against doing sysupgrade "and keep files
> in place", as the based filesystem does change, and I'm not making
> huge attempts at dealing with that. so doing a backup
> then a sysupdate -n (-n meaning don't preserve files over the backup)
> is generally a good idea.
>
> anyway:
>
> commit be09b8c15b6dc6bf4cb7da3112c598138a9c77ef
> Author: Dave Taht <dave.taht@bufferbloat.net>
> Date:   Tue Feb 14 14:38:40 2012 +0000
>
>    SFQ is limited in packets. RED is in bytes. tcrules.awk conflated these
>
>    The original openwrt shaper took the RED byte calculation...
>    and reused it to specify a limit for sfq. However, sfq uses
>    packets rather than bytes, so it was specifying, say 16000 bytes
>    and translating that to 16000 packets.
>
>    This was not an error I prior to 3.3, because SFQ had a
>    hard coded limit of 127 packets. It is now.
>
>    So this commit puts a lower and upper bound on the maximum packets
>    that is sane, but is not pre 3.2 compatible.
>
> commit 44f8febbd34686564516c3261a911bd7cffcf714
>
>
> On Thu, Feb 23, 2012 at 6:21 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>> Hi Dave,
>>
>> I finally got around to update from rc6 to bql-40, to try the ATM shaping. The update was a breeze, great work!
>>        I am sad to report that for my ATM link AQM does not work for me as well as QoS does. My measurement consists out of using ping to get the RTT to the first ISP hop (as taken from trace route) while concurrently saturating the up link with a dropbox upload (which I usually give that a headstart of 10 seconds to go into bandwidth ceiling): AQM gives the same bad avg RTT of 1.2 seconds as no shaping at all does, while QoS gives me an avg RTT of around 24ms (best case RTT is around 13ms on my link, so the link stays pretty useable).
>>        I tried to apply the same changes to /usr/lib/aqm/generate.sh and /usr/lib/qos/generate.sh to make the them better understand the peculiarities of my ATM adsl1 connection, but it seems I did something wrong for the AQM script since my change does not have any effect there… (both modified files attached). I usually only  shape up- and down-stream to 97% of the line rate, which works ok with QoS. (And all my tests have been done, very unscientifically, using my mac laptop over the 5GHz wireless band of the router… )
>>
>>
>>
>>
>>        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
>>
>>
>
>
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://www.bufferbloat.net



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

Re: [Cerowrt-devel] smoketest BQL-40 is out

[Sebastian Moeller]

Hi Dave,

thanks for your reply.


On Feb 23, 2012, at 2:49 AM, Dave Taht wrote:

> I'm aware there are several messages in
> the backlog I need to respond to, but I am travelling
> at the moment and eyeball deep in meetings. (presently in NJ,
> next week philly, and then I get back to the bloatlab in isc
> in california friday-ish.
> 
> As best as I recall there was no real difference between
> the AQM script and the QoS script in bql-40, and I may
> not get around to doing a 'bql-42' per se' but go right
> into the 3.3 development process.

	Well in my case AQM does not work at all (if I shape to 1/5 of my uplink line rate I still see transfers running at 1/1 uplink rate, so clearly somehow on my system AQM does not work) I will have a try at figuring out why AQM does not seem to activate...

> 
> This will not be the final url for the 3.3 development
> series, but
> 
> http://huchra.bufferbloat.net/~cero1/3.3/
> 
> has that.
> 
> I made a small dent in the qos/aqm problem there,
> (my intent was to basically treat the above as 'bql-41' -
> I wanted to treat 3.3 issues and bql issues separately,
> but lack time to do both, and 3.3 is going swimmingly, so...)
> 
> but I'm puzzled as to what you are seeing below.
> 
> 0) Did you enable the aqm script? If you merely run it
> without enabling it, nothing happens. Similarly, the qos script
> needs to be disabled.

	Sorry for not being clear, I always had only the module under test enabled, the other one was always disabled. One thing I noticed, when enabling QoS I get the "Applying changes" info widget and it will state "/etc/config/qos" while enabling AQM will not show any "/etc/config" info, but that might be purely cosmetic. Will investigate, as it looks somehow AQM is never really enabled.
	Question do I need to install any package under the system->software tab for AQM to fully work? I assume not.

> 
> 1) Neither the AQM nor qos script does ADSL overhead right,
> and I'd got puzzled on what was 'right' after fiddling with it.

	Well, I agree that the overhead calculation as implemented in generate.sh is quite dubious (it looks like a stochastic approach). So I used the fact that cewrowrt comes with quite recent tc and used tc's "stab" option as that seems theoretically solve both the ATM carrier packet quantization as well as the per packet overhead issues quite well.

> 
> 2) both qos and aqm calculated the sfq 'limit' variable wrong, and
> neither did ipv6 work right at all.

	I still have no IPv6 available so I did not test that. And even with the limit error QoS still works okay. (And I quite sure so will AQM once I manage to actually activate it :) )

> 
> I believe, but don't remember, that at least those fixes got made in
> the 3.3rc4-1 code. Actually there's a better fix for the ipv6 issue
> than what's there…

	Ah, so I will keep changing my firmware :)

> 
> 3) I am not intending to stick with the aqm script as structured now,
> but to finish modifying the 'debloat' script to have all the features required.
> 
> that one has a bunch of semi-working queue models in it.
> 
> If yer gonna hack scripts, please take a look at that one.
> There are plenty of things it needs and the qos and aqm scripts
> are more feature complete, tho…

	OH, thanks for the pointer, I have not looked at debloat recently, but I am somewhat confused by the generate.sh and trulls.awk combination, so I hope that debloat is more accessible for non-programmers...


> 
> 4) re updates: I have to warn against doing sysupgrade "and keep files
> in place", as the based filesystem does change, and I'm not making
> huge attempts at dealing with that. so doing a backup
> then a sysupdate -n (-n meaning don't preserve files over the backup)
> is generally a good idea.

	Thanks for the advise, I actually reflashed the factory firmware for bql-40 and called it update, sorry for being unclear. Actually the installation flashing instructions (http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_flashing_instructions) were quite specific about which method one should use.


> 
> anyway:
> 
> commit be09b8c15b6dc6bf4cb7da3112c598138a9c77ef
> Author: Dave Taht <dave.taht@bufferbloat.net>
> Date:   Tue Feb 14 14:38:40 2012 +0000
> 
>    SFQ is limited in packets. RED is in bytes. tcrules.awk conflated these
> 
>    The original openwrt shaper took the RED byte calculation...
>    and reused it to specify a limit for sfq. However, sfq uses
>    packets rather than bytes, so it was specifying, say 16000 bytes
>    and translating that to 16000 packets.
> 
>    This was not an error I prior to 3.3, because SFQ had a
>    hard coded limit of 127 packets. It is now.
> 
>    So this commit puts a lower and upper bound on the maximum packets
>    that is sane, but is not pre 3.2 compatible.
> 
> commit 44f8febbd34686564516c3261a911bd7cffcf714

	Thanks a lot for the great project.

Best
	Sebastian


> 
> 
> On Thu, Feb 23, 2012 at 6:21 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>> Hi Dave,
>> 
>> I finally got around to update from rc6 to bql-40, to try the ATM shaping. The update was a breeze, great work!
>>        I am sad to report that for my ATM link AQM does not work for me as well as QoS does. My measurement consists out of using ping to get the RTT to the first ISP hop (as taken from trace route) while concurrently saturating the up link with a dropbox upload (which I usually give that a headstart of 10 seconds to go into bandwidth ceiling): AQM gives the same bad avg RTT of 1.2 seconds as no shaping at all does, while QoS gives me an avg RTT of around 24ms (best case RTT is around 13ms on my link, so the link stays pretty useable).
>>        I tried to apply the same changes to /usr/lib/aqm/generate.sh and /usr/lib/qos/generate.sh to make the them better understand the peculiarities of my ATM adsl1 connection, but it seems I did something wrong for the AQM script since my change does not have any effect there… (both modified files attached). I usually only  shape up- and down-stream to 97% of the line rate, which works ok with QoS. (And all my tests have been done, very unscientifically, using my mac laptop over the 5GHz wireless band of the router… )
>> 
>> 
>> 
>> 
>>        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
>> 
>> 
> 
> 
> 
> -- 
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://www.bufferbloat.net

Re: [Cerowrt-devel] smoketest BQL-40 is out

[Dave Taht]

On Thu, Feb 23, 2012 at 6:38 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Dave,
>
> thanks for your reply.
>
>
> On Feb 23, 2012, at 2:49 AM, Dave Taht wrote:
>
>> I'm aware there are several messages in
>> the backlog I need to respond to, but I am travelling
>> at the moment and eyeball deep in meetings. (presently in NJ,
>> next week philly, and then I get back to the bloatlab in isc
>> in california friday-ish.
>>
>> As best as I recall there was no real difference between
>> the AQM script and the QoS script in bql-40, and I may
>> not get around to doing a 'bql-42' per se' but go right
>> into the 3.3 development process.
>
>        Well in my case AQM does not work at all (if I shape to 1/5 of my uplink line rate I still see transfers running at 1/1 uplink rate, so clearly somehow on my system AQM does not work) I will have a try at figuring out why AQM does not seem to activate...

I was not running it via the web interface. Splitting off 'AQM' from
'QOS' is a start at
to be able to a/b the two different systems easily and then fold back
the good bits upstream on the qos side, and continue to revise the aqm
side. It wouldn't surprise me if the web side was entirely borked, and
I won't be in a position to work on this until late next week, unless
I get some spare time this weekend.

/etc/init.d/aqm enable - to run at boot
edit /etc/config/aqm - and make the enable line have '1'
/etc/init.d/aqm start

>>
>> This will not be the final url for the 3.3 development
>> series, but
>>
>> http://huchra.bufferbloat.net/~cero1/3.3/
>>
>> has that.
>>
>> I made a small dent in the qos/aqm problem there,
>> (my intent was to basically treat the above as 'bql-41' -
>> I wanted to treat 3.3 issues and bql issues separately,
>> but lack time to do both, and 3.3 is going swimmingly, so...)
>>
>> but I'm puzzled as to what you are seeing below.
>>
>> 0) Did you enable the aqm script? If you merely run it
>> without enabling it, nothing happens. Similarly, the qos script
>> needs to be disabled.
>
>        Sorry for not being clear, I always had only the module under test enabled, the other one was always disabled. One thing I noticed, when enabling QoS I get the "Applying changes" info widget and it will state "/etc/config/qos" while enabling AQM will not show any "/etc/config" info, but that might be purely cosmetic. Will investigate, as it looks somehow AQM is never really enabled.
>        Question do I need to install any package under the system->software tab for AQM to fully work? I assume not.

No, aside from the web interface being as yet untested...

>
>>
>> 1) Neither the AQM nor qos script does ADSL overhead right,
>> and I'd got puzzled on what was 'right' after fiddling with it.
>
>        Well, I agree that the overhead calculation as implemented in generate.sh is quite dubious (it looks like a stochastic approach).

Completely dubious and probably dates back to before the stab work.

>So I used the fact that cewrowrt comes with quite recent tc and used tc's "stab" option as that seems theoretically solve both the ATM carrier packet quantization as well as the per packet overhead issues quite well.

Yes.
>
>>
>> 2) both qos and aqm calculated the sfq 'limit' variable wrong, and
>> neither did ipv6 work right at all.
>
>        I still have no IPv6 available so I did not test that. And even with the limit error QoS still works okay. (And I quite sure so will AQM once I manage to actually activate it :) )

Well, my concern is mostly that bittorrent will misbehave worse under
this system than otherwise.

Qos-scripts uses hfsc + sfq for two bins, and hfsc + red for two other
bins. Both sfq and red have improvements that qos-scripts should now
be automatically picking up - red was entirely broken before kernel
3.2, actually.

AQM-scripts - at least this cut at it - will use hfsc + sfqred for all
bins, and saner limits for both sfq and the red component of sfqred
which will hopefully

I have to admit that the simplest possible implementation of the new
stuff in debloat is performing pretty well - which is merely htb + 1
bin of sfqred.

So if you pull down the latest debloat from the deBloat repo, and just
run a command line of

IFACE=ge00 QMODEL=htb_sfq_red UPLINK=whatever_in_kbits /usr/sbin/debloat

the results should be pretty good.

I'm thinking a two tier model (Best effort and background) will be
pretty good, 3 tiers and
I can emulate most of pfifo_fast's behavior, but I don't see a need
for the 4 tier model in qos-scripts, but that's why we test...

>
>>
>> I believe, but don't remember, that at least those fixes got made in
>> the 3.3rc4-1 code. Actually there's a better fix for the ipv6 issue
>> than what's there…
>
>        Ah, so I will keep changing my firmware :)

Like I said, it's mostly just scripts now.... no huge need for that.

>>
>> 3) I am not intending to stick with the aqm script as structured now,
>> but to finish modifying the 'debloat' script to have all the features required.
>>
>> that one has a bunch of semi-working queue models in it.
>>
>> If yer gonna hack scripts, please take a look at that one.
>> There are plenty of things it needs and the qos and aqm scripts
>> are more feature complete, tho…
>
>        OH, thanks for the pointer, I have not looked at debloat recently, but I am somewhat confused by the generate.sh and trulls.awk combination, so I hope that debloat is more accessible for non-programmers...

There is some really good stuff in the current combo, but I too found
the amalagation of shell and awk kind of difficult. Wanted one
language, with floating point, which was why I ended up
going for lua, which has it's own problems too, but...
>
>
>>
>> 4) re updates: I have to warn against doing sysupgrade "and keep files
>> in place", as the based filesystem does change, and I'm not making
>> huge attempts at dealing with that. so doing a backup
>> then a sysupdate -n (-n meaning don't preserve files over the backup)
>> is generally a good idea.
>
>        Thanks for the advise, I actually reflashed the factory firmware for bql-40 and called it update, sorry for being unclear. Actually the installation flashing instructions (http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_flashing_instructions) were quite specific about which method one should use.

Yep. Large red letters and everything.
>
>
>>
>> anyway:
>>
>> commit be09b8c15b6dc6bf4cb7da3112c598138a9c77ef
>> Author: Dave Taht <dave.taht@bufferbloat.net>
>> Date:   Tue Feb 14 14:38:40 2012 +0000
>>
>>    SFQ is limited in packets. RED is in bytes. tcrules.awk conflated these
>>
>>    The original openwrt shaper took the RED byte calculation...
>>    and reused it to specify a limit for sfq. However, sfq uses
>>    packets rather than bytes, so it was specifying, say 16000 bytes
>>    and translating that to 16000 packets.
>>
>>    This was not an error I prior to 3.3, because SFQ had a
>>    hard coded limit of 127 packets. It is now.
>>
>>    So this commit puts a lower and upper bound on the maximum packets
>>    that is sane, but is not pre 3.2 compatible.
>>
>> commit 44f8febbd34686564516c3261a911bd7cffcf714
>
>        Thanks a lot for the great project.

Getting there!

> Best
>        Sebastian
>
>
>>
>>
>> On Thu, Feb 23, 2012 at 6:21 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>>> Hi Dave,
>>>
>>> I finally got around to update from rc6 to bql-40, to try the ATM shaping. The update was a breeze, great work!
>>>        I am sad to report that for my ATM link AQM does not work for me as well as QoS does. My measurement consists out of using ping to get the RTT to the first ISP hop (as taken from trace route) while concurrently saturating the up link with a dropbox upload (which I usually give that a headstart of 10 seconds to go into bandwidth ceiling): AQM gives the same bad avg RTT of 1.2 seconds as no shaping at all does, while QoS gives me an avg RTT of around 24ms (best case RTT is around 13ms on my link, so the link stays pretty useable).
>>>        I tried to apply the same changes to /usr/lib/aqm/generate.sh and /usr/lib/qos/generate.sh to make the them better understand the peculiarities of my ATM adsl1 connection, but it seems I did something wrong for the AQM script since my change does not have any effect there… (both modified files attached). I usually only  shape up- and down-stream to 97% of the line rate, which works ok with QoS. (And all my tests have been done, very unscientifically, using my mac laptop over the 5GHz wireless band of the router… )
>>>
>>>
>>>
>>>
>>>        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
>>>
>>>
>>
>>
>>
>> --
>> Dave Täht
>> SKYPE: davetaht
>> US Tel: 1-239-829-5608
>> http://www.bufferbloat.net
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

Re: [Cerowrt-devel] smoketest BQL-40 is out

[Sebastian Moeller]

Hi Dave,

thanks again,

On Feb 23, 2012, at 11:10 AM, Dave Taht wrote:

> On Thu, Feb 23, 2012 at 6:38 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
>> Hi Dave,
>> 
>> thanks for your reply.
>> 
>> 
>> On Feb 23, 2012, at 2:49 AM, Dave Taht wrote:
>> 
>>> I'm aware there are several messages in
>>> the backlog I need to respond to, but I am travelling
>>> at the moment and eyeball deep in meetings. (presently in NJ,
>>> next week philly, and then I get back to the bloatlab in isc
>>> in california friday-ish.
>>> 
>>> As best as I recall there was no real difference between
>>> the AQM script and the QoS script in bql-40, and I may
>>> not get around to doing a 'bql-42' per se' but go right
>>> into the 3.3 development process.
>> 
>>        Well in my case AQM does not work at all (if I shape to 1/5 of my uplink line rate I still see transfers running at 1/1 uplink rate, so clearly somehow on my system AQM does not work) I will have a try at figuring out why AQM does not seem to activate...
> 
> I was not running it via the web interface. Splitting off 'AQM' from
> 'QOS' is a start at
> to be able to a/b the two different systems easily and then fold back
> the good bits upstream on the qos side, and continue to revise the aqm
> side. It wouldn't surprise me if the web side was entirely borked, and
> I won't be in a position to work on this until late next week, unless
> I get some spare time this weekend.
> 
> /etc/init.d/aqm enable - to run at boot
> edit /etc/config/aqm - and make the enable line have '1'
> /etc/init.d/aqm start

	Yes, that did the trick! Now AQM actually is even better than QoS for my worst case scenario, saturating uplink, starting one downlink elephant and open 93 media heavy tabs in the browser.
I now get:
100 packets transmitted, 73 packets received, 27.0% packet loss
round-trip min/avg/max/stddev = 33.941/108.083/177.825/22.795 ms

while using QoS I got:
100 packets transmitted, 75 packets received, 25.0% packet loss
round-trip min/avg/max/stddev = 18.111/181.506/325.416/45.006 ms

AQM is even better behaved than QoS now. That is pretty cool.

BTW the web AQM interface manged to set the enabled line in /etc/config/aqm just fine it just did not seem to manage to do the equivalent of /etc/init.d/aqm start.

Cool stuff.

Best
	Sebastian



> 
>>> 
>>> This will not be the final url for the 3.3 development
>>> series, but
>>> 
>>> http://huchra.bufferbloat.net/~cero1/3.3/
>>> 
>>> has that.
>>> 
>>> I made a small dent in the qos/aqm problem there,
>>> (my intent was to basically treat the above as 'bql-41' -
>>> I wanted to treat 3.3 issues and bql issues separately,
>>> but lack time to do both, and 3.3 is going swimmingly, so...)
>>> 
>>> but I'm puzzled as to what you are seeing below.
>>> 
>>> 0) Did you enable the aqm script? If you merely run it
>>> without enabling it, nothing happens. Similarly, the qos script
>>> needs to be disabled.
>> 
>>        Sorry for not being clear, I always had only the module under test enabled, the other one was always disabled. One thing I noticed, when enabling QoS I get the "Applying changes" info widget and it will state "/etc/config/qos" while enabling AQM will not show any "/etc/config" info, but that might be purely cosmetic. Will investigate, as it looks somehow AQM is never really enabled.
>>        Question do I need to install any package under the system->software tab for AQM to fully work? I assume not.
> 
> No, aside from the web interface being as yet untested...
> 
>> 
>>> 
>>> 1) Neither the AQM nor qos script does ADSL overhead right,
>>> and I'd got puzzled on what was 'right' after fiddling with it.
>> 
>>        Well, I agree that the overhead calculation as implemented in generate.sh is quite dubious (it looks like a stochastic approach).
> 
> Completely dubious and probably dates back to before the stab work.
> 
>> So I used the fact that cewrowrt comes with quite recent tc and used tc's "stab" option as that seems theoretically solve both the ATM carrier packet quantization as well as the per packet overhead issues quite well.
> 
> Yes.
>> 
>>> 
>>> 2) both qos and aqm calculated the sfq 'limit' variable wrong, and
>>> neither did ipv6 work right at all.
>> 
>>        I still have no IPv6 available so I did not test that. And even with the limit error QoS still works okay. (And I quite sure so will AQM once I manage to actually activate it :) )
> 
> Well, my concern is mostly that bittorrent will misbehave worse under
> this system than otherwise.
> 
> Qos-scripts uses hfsc + sfq for two bins, and hfsc + red for two other
> bins. Both sfq and red have improvements that qos-scripts should now
> be automatically picking up - red was entirely broken before kernel
> 3.2, actually.
> 
> AQM-scripts - at least this cut at it - will use hfsc + sfqred for all
> bins, and saner limits for both sfq and the red component of sfqred
> which will hopefully
> 
> I have to admit that the simplest possible implementation of the new
> stuff in debloat is performing pretty well - which is merely htb + 1
> bin of sfqred.
> 
> So if you pull down the latest debloat from the deBloat repo, and just
> run a command line of
> 
> IFACE=ge00 QMODEL=htb_sfq_red UPLINK=whatever_in_kbits /usr/sbin/debloat
> 
> the results should be pretty good.
> 
> I'm thinking a two tier model (Best effort and background) will be
> pretty good, 3 tiers and
> I can emulate most of pfifo_fast's behavior, but I don't see a need
> for the 4 tier model in qos-scripts, but that's why we test...
> 
>> 
>>> 
>>> I believe, but don't remember, that at least those fixes got made in
>>> the 3.3rc4-1 code. Actually there's a better fix for the ipv6 issue
>>> than what's there…
>> 
>>        Ah, so I will keep changing my firmware :)
> 
> Like I said, it's mostly just scripts now.... no huge need for that.
> 
>>> 
>>> 3) I am not intending to stick with the aqm script as structured now,
>>> but to finish modifying the 'debloat' script to have all the features required.
>>> 
>>> that one has a bunch of semi-working queue models in it.
>>> 
>>> If yer gonna hack scripts, please take a look at that one.
>>> There are plenty of things it needs and the qos and aqm scripts
>>> are more feature complete, tho…
>> 
>>        OH, thanks for the pointer, I have not looked at debloat recently, but I am somewhat confused by the generate.sh and trulls.awk combination, so I hope that debloat is more accessible for non-programmers...
> 
> There is some really good stuff in the current combo, but I too found
> the amalagation of shell and awk kind of difficult. Wanted one
> language, with floating point, which was why I ended up
> going for lua, which has it's own problems too, but...
>> 
>> 
>>> 
>>> 4) re updates: I have to warn against doing sysupgrade "and keep files
>>> in place", as the based filesystem does change, and I'm not making
>>> huge attempts at dealing with that. so doing a backup
>>> then a sysupdate -n (-n meaning don't preserve files over the backup)
>>> is generally a good idea.
>> 
>>        Thanks for the advise, I actually reflashed the factory firmware for bql-40 and called it update, sorry for being unclear. Actually the installation flashing instructions (http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_flashing_instructions) were quite specific about which method one should use.
> 
> Yep. Large red letters and everything.
>> 
>> 
>>> 
>>> anyway:
>>> 
>>> commit be09b8c15b6dc6bf4cb7da3112c598138a9c77ef
>>> Author: Dave Taht <dave.taht@bufferbloat.net>
>>> Date:   Tue Feb 14 14:38:40 2012 +0000
>>> 
>>>    SFQ is limited in packets. RED is in bytes. tcrules.awk conflated these
>>> 
>>>    The original openwrt shaper took the RED byte calculation...
>>>    and reused it to specify a limit for sfq. However, sfq uses
>>>    packets rather than bytes, so it was specifying, say 16000 bytes
>>>    and translating that to 16000 packets.
>>> 
>>>    This was not an error I prior to 3.3, because SFQ had a
>>>    hard coded limit of 127 packets. It is now.
>>> 
>>>    So this commit puts a lower and upper bound on the maximum packets
>>>    that is sane, but is not pre 3.2 compatible.
>>> 
>>> commit 44f8febbd34686564516c3261a911bd7cffcf714
>> 
>>        Thanks a lot for the great project.
> 
> Getting there!
> 
>> Best
>>        Sebastian
>> 
>> 
>>> 
>>> 
>>> On Thu, Feb 23, 2012 at 6:21 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>>>> Hi Dave,
>>>> 
>>>> I finally got around to update from rc6 to bql-40, to try the ATM shaping. The update was a breeze, great work!
>>>>        I am sad to report that for my ATM link AQM does not work for me as well as QoS does. My measurement consists out of using ping to get the RTT to the first ISP hop (as taken from trace route) while concurrently saturating the up link with a dropbox upload (which I usually give that a headstart of 10 seconds to go into bandwidth ceiling): AQM gives the same bad avg RTT of 1.2 seconds as no shaping at all does, while QoS gives me an avg RTT of around 24ms (best case RTT is around 13ms on my link, so the link stays pretty useable).
>>>>        I tried to apply the same changes to /usr/lib/aqm/generate.sh and /usr/lib/qos/generate.sh to make the them better understand the peculiarities of my ATM adsl1 connection, but it seems I did something wrong for the AQM script since my change does not have any effect there… (both modified files attached). I usually only  shape up- and down-stream to 97% of the line rate, which works ok with QoS. (And all my tests have been done, very unscientifically, using my mac laptop over the 5GHz wireless band of the router… )
>>>> 
>>>> 
>>>> 
>>>> 
>>>>        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
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Dave Täht
>>> SKYPE: davetaht
>>> US Tel: 1-239-829-5608
>>> http://www.bufferbloat.net
>> 
> 
> 
> 
> -- 
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://www.bufferbloat.net

Re: [Cerowrt-devel] smoketest BQL-40 is out

[Dave Taht]

your min time is higher than I'd expected, but certainly the mean and
max and stddev have improved.

Could you send the output of

tc -s qdisc show dev ge00

after a test run?

>        Yes, that did the trick! Now AQM actually is even better than QoS for my worst case scenario, saturating uplink, starting one downlink elephant and open 93 media heavy tabs in the browser.
> I now get:
> 100 packets transmitted, 73 packets received, 27.0% packet loss
> round-trip min/avg/max/stddev = 33.941/108.083/177.825/22.795 ms
>
> while using QoS I got:
> 100 packets transmitted, 75 packets received, 25.0% packet loss
> round-trip min/avg/max/stddev = 18.111/181.506/325.416/45.006 ms
>
> AQM is even better behaved than QoS now. That is pretty cool.
>
> BTW the web AQM interface manged to set the enabled line in /etc/config/aqm just fine it just did not seem to manage to do the equivalent of /etc/init.d/aqm start.
>
> Cool stuff.
>
> Best
>        Sebastian
>
>
>
>>
>>>>
>>>> This will not be the final url for the 3.3 development
>>>> series, but
>>>>
>>>> http://huchra.bufferbloat.net/~cero1/3.3/
>>>>
>>>> has that.
>>>>
>>>> I made a small dent in the qos/aqm problem there,
>>>> (my intent was to basically treat the above as 'bql-41' -
>>>> I wanted to treat 3.3 issues and bql issues separately,
>>>> but lack time to do both, and 3.3 is going swimmingly, so...)
>>>>
>>>> but I'm puzzled as to what you are seeing below.
>>>>
>>>> 0) Did you enable the aqm script? If you merely run it
>>>> without enabling it, nothing happens. Similarly, the qos script
>>>> needs to be disabled.
>>>
>>>        Sorry for not being clear, I always had only the module under test enabled, the other one was always disabled. One thing I noticed, when enabling QoS I get the "Applying changes" info widget and it will state "/etc/config/qos" while enabling AQM will not show any "/etc/config" info, but that might be purely cosmetic. Will investigate, as it looks somehow AQM is never really enabled.
>>>        Question do I need to install any package under the system->software tab for AQM to fully work? I assume not.
>>
>> No, aside from the web interface being as yet untested...
>>
>>>
>>>>
>>>> 1) Neither the AQM nor qos script does ADSL overhead right,
>>>> and I'd got puzzled on what was 'right' after fiddling with it.
>>>
>>>        Well, I agree that the overhead calculation as implemented in generate.sh is quite dubious (it looks like a stochastic approach).
>>
>> Completely dubious and probably dates back to before the stab work.
>>
>>> So I used the fact that cewrowrt comes with quite recent tc and used tc's "stab" option as that seems theoretically solve both the ATM carrier packet quantization as well as the per packet overhead issues quite well.
>>
>> Yes.
>>>
>>>>
>>>> 2) both qos and aqm calculated the sfq 'limit' variable wrong, and
>>>> neither did ipv6 work right at all.
>>>
>>>        I still have no IPv6 available so I did not test that. And even with the limit error QoS still works okay. (And I quite sure so will AQM once I manage to actually activate it :) )
>>
>> Well, my concern is mostly that bittorrent will misbehave worse under
>> this system than otherwise.
>>
>> Qos-scripts uses hfsc + sfq for two bins, and hfsc + red for two other
>> bins. Both sfq and red have improvements that qos-scripts should now
>> be automatically picking up - red was entirely broken before kernel
>> 3.2, actually.
>>
>> AQM-scripts - at least this cut at it - will use hfsc + sfqred for all
>> bins, and saner limits for both sfq and the red component of sfqred
>> which will hopefully
>>
>> I have to admit that the simplest possible implementation of the new
>> stuff in debloat is performing pretty well - which is merely htb + 1
>> bin of sfqred.
>>
>> So if you pull down the latest debloat from the deBloat repo, and just
>> run a command line of
>>
>> IFACE=ge00 QMODEL=htb_sfq_red UPLINK=whatever_in_kbits /usr/sbin/debloat
>>
>> the results should be pretty good.
>>
>> I'm thinking a two tier model (Best effort and background) will be
>> pretty good, 3 tiers and
>> I can emulate most of pfifo_fast's behavior, but I don't see a need
>> for the 4 tier model in qos-scripts, but that's why we test...
>>
>>>
>>>>
>>>> I believe, but don't remember, that at least those fixes got made in
>>>> the 3.3rc4-1 code. Actually there's a better fix for the ipv6 issue
>>>> than what's there…
>>>
>>>        Ah, so I will keep changing my firmware :)
>>
>> Like I said, it's mostly just scripts now.... no huge need for that.
>>
>>>>
>>>> 3) I am not intending to stick with the aqm script as structured now,
>>>> but to finish modifying the 'debloat' script to have all the features required.
>>>>
>>>> that one has a bunch of semi-working queue models in it.
>>>>
>>>> If yer gonna hack scripts, please take a look at that one.
>>>> There are plenty of things it needs and the qos and aqm scripts
>>>> are more feature complete, tho…
>>>
>>>        OH, thanks for the pointer, I have not looked at debloat recently, but I am somewhat confused by the generate.sh and trulls.awk combination, so I hope that debloat is more accessible for non-programmers...
>>
>> There is some really good stuff in the current combo, but I too found
>> the amalagation of shell and awk kind of difficult. Wanted one
>> language, with floating point, which was why I ended up
>> going for lua, which has it's own problems too, but...
>>>
>>>
>>>>
>>>> 4) re updates: I have to warn against doing sysupgrade "and keep files
>>>> in place", as the based filesystem does change, and I'm not making
>>>> huge attempts at dealing with that. so doing a backup
>>>> then a sysupdate -n (-n meaning don't preserve files over the backup)
>>>> is generally a good idea.
>>>
>>>        Thanks for the advise, I actually reflashed the factory firmware for bql-40 and called it update, sorry for being unclear. Actually the installation flashing instructions (http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_flashing_instructions) were quite specific about which method one should use.
>>
>> Yep. Large red letters and everything.
>>>
>>>
>>>>
>>>> anyway:
>>>>
>>>> commit be09b8c15b6dc6bf4cb7da3112c598138a9c77ef
>>>> Author: Dave Taht <dave.taht@bufferbloat.net>
>>>> Date:   Tue Feb 14 14:38:40 2012 +0000
>>>>
>>>>    SFQ is limited in packets. RED is in bytes. tcrules.awk conflated these
>>>>
>>>>    The original openwrt shaper took the RED byte calculation...
>>>>    and reused it to specify a limit for sfq. However, sfq uses
>>>>    packets rather than bytes, so it was specifying, say 16000 bytes
>>>>    and translating that to 16000 packets.
>>>>
>>>>    This was not an error I prior to 3.3, because SFQ had a
>>>>    hard coded limit of 127 packets. It is now.
>>>>
>>>>    So this commit puts a lower and upper bound on the maximum packets
>>>>    that is sane, but is not pre 3.2 compatible.
>>>>
>>>> commit 44f8febbd34686564516c3261a911bd7cffcf714
>>>
>>>        Thanks a lot for the great project.
>>
>> Getting there!
>>
>>> Best
>>>        Sebastian
>>>
>>>
>>>>
>>>>
>>>> On Thu, Feb 23, 2012 at 6:21 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>>>>> Hi Dave,
>>>>>
>>>>> I finally got around to update from rc6 to bql-40, to try the ATM shaping. The update was a breeze, great work!
>>>>>        I am sad to report that for my ATM link AQM does not work for me as well as QoS does. My measurement consists out of using ping to get the RTT to the first ISP hop (as taken from trace route) while concurrently saturating the up link with a dropbox upload (which I usually give that a headstart of 10 seconds to go into bandwidth ceiling): AQM gives the same bad avg RTT of 1.2 seconds as no shaping at all does, while QoS gives me an avg RTT of around 24ms (best case RTT is around 13ms on my link, so the link stays pretty useable).
>>>>>        I tried to apply the same changes to /usr/lib/aqm/generate.sh and /usr/lib/qos/generate.sh to make the them better understand the peculiarities of my ATM adsl1 connection, but it seems I did something wrong for the AQM script since my change does not have any effect there… (both modified files attached). I usually only  shape up- and down-stream to 97% of the line rate, which works ok with QoS. (And all my tests have been done, very unscientifically, using my mac laptop over the 5GHz wireless band of the router… )
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>        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
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Dave Täht
>>>> SKYPE: davetaht
>>>> US Tel: 1-239-829-5608
>>>> http://www.bufferbloat.net
>>>
>>
>>
>>
>> --
>> Dave Täht
>> SKYPE: davetaht
>> US Tel: 1-239-829-5608
>> http://www.bufferbloat.net
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

Re: [Cerowrt-devel] smoketest BQL-40 is out

[Sebastian Moeller]

Hi Dave, 

I managed to squeeze that test in, hope it helps.



On Feb 23, 2012, at 2:19 PM, Dave Taht wrote:

> your min time is higher than I'd expected, but certainly the mean and
> max and stddev have improved.
> 
> Could you send the output of
> 
> tc -s qdisc show dev ge00


Here the BEFORE test run output:
root@nacktmulle:~# tc -s qdisc show dev ge00
qdisc hfsc 1: root refcnt 2 default 30 
 Sent 42751655 bytes 128031 pkt (dropped 1635, overlimits 244784 requeues 2) 
 backlog 0b 0p requeues 2 
qdisc sfq 100: parent 1:10 limit 60p quantum 1514b depth 24 headdrop divisor 1024 
 ewma 2 min 3174b max 9522b probability 0.12 ecn 
 prob_mark 0 prob_mark_head 0 prob_drop 0
 forced_mark 0 forced_mark_head 0 forced_drop 0
 Sent 10785394 bytes 96191 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
qdisc sfq 200: parent 1:20 limit 60p quantum 1514b depth 24 headdrop divisor 1024 
 ewma 2 min 3174b max 9522b probability 0.12 ecn 
 prob_mark 0 prob_mark_head 0 prob_drop 0
 forced_mark 0 forced_mark_head 0 forced_drop 0
 Sent 72822 bytes 370 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
qdisc sfq 300: parent 1:30 limit 60p quantum 1514b depth 24 headdrop divisor 1024 
 ewma 2 min 3174b max 9522b probability 0.12 ecn 
 prob_mark 0 prob_mark_head 0 prob_drop 972
 forced_mark 0 forced_mark_head 0 forced_drop 3
 Sent 31856604 bytes 31239 pkt (dropped 2438, overlimits 975 requeues 0) 
 backlog 0b 0p requeues 0 
qdisc sfq 400: parent 1:40 limit 60p quantum 1514b depth 24 headdrop divisor 1024 
 ewma 2 min 3174b max 9522b probability 0.12 ecn 
 prob_mark 0 prob_mark_head 0 prob_drop 0
 forced_mark 0 forced_mark_head 0 forced_drop 0
 Sent 36835 bytes 231 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 

And here AFTER the test run:
root@nacktmulle:~# tc -s qdisc show dev ge00
qdisc hfsc 1: root refcnt 2 default 30 
 Sent 51812429 bytes 170042 pkt (dropped 4040, overlimits 325311 requeues 2) 
 backlog 0b 0p requeues 2 
qdisc sfq 100: parent 1:10 limit 60p quantum 1514b depth 24 headdrop divisor 1024 
 ewma 2 min 3174b max 9522b probability 0.12 ecn 
 prob_mark 0 prob_mark_head 0 prob_drop 0
 forced_mark 0 forced_mark_head 0 forced_drop 0
 Sent 14805550 bytes 130775 pkt (dropped 24, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
qdisc sfq 200: parent 1:20 limit 60p quantum 1514b depth 24 headdrop divisor 1024 
 ewma 2 min 3174b max 9522b probability 0.12 ecn 
 prob_mark 0 prob_mark_head 0 prob_drop 0
 forced_mark 0 forced_mark_head 0 forced_drop 0
 Sent 74783 bytes 387 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
qdisc sfq 300: parent 1:30 limit 60p quantum 1514b depth 24 headdrop divisor 1024 
 ewma 2 min 3174b max 9522b probability 0.12 ecn 
 prob_mark 0 prob_mark_head 0 prob_drop 1067
 forced_mark 0 forced_mark_head 0 forced_drop 40
 Sent 36890173 bytes 38621 pkt (dropped 5546, overlimits 1107 requeues 0) 
 backlog 0b 0p requeues 0 
qdisc sfq 400: parent 1:40 limit 60p quantum 1514b depth 24 headdrop divisor 1024 
 ewma 2 min 3174b max 9522b probability 0.12 ecn 
 prob_mark 0 prob_mark_head 0 prob_drop 0
 forced_mark 0 forced_mark_head 0 forced_drop 0
 Sent 41923 bytes 259 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 


> 
> after a test run?

Here is the ping probe with AQM at 97% of line rates (line up 512 k)
--- netblock-75-79-143-1.dslextreme.com ping statistics ---
100 packets transmitted, 70 packets received, 30.0% packet loss
round-trip min/avg/max/stddev = 10.246/92.621/203.575/39.855 ms

So it looks the minimum and STD are quite variable between test runs...


Best Regards
	Sebastian

> 
>>        Yes, that did the trick! Now AQM actually is even better than QoS for my worst case scenario, saturating uplink, starting one downlink elephant and open 93 media heavy tabs in the browser.
>> I now get:
>> 100 packets transmitted, 73 packets received, 27.0% packet loss
>> round-trip min/avg/max/stddev = 33.941/108.083/177.825/22.795 ms
>> 
>> while using QoS I got:
>> 100 packets transmitted, 75 packets received, 25.0% packet loss
>> round-trip min/avg/max/stddev = 18.111/181.506/325.416/45.006 ms
>> 
>> AQM is even better behaved than QoS now. That is pretty cool.
>> 
>> BTW the web AQM interface manged to set the enabled line in /etc/config/aqm just fine it just did not seem to manage to do the equivalent of /etc/init.d/aqm start.
>> 
>> Cool stuff.
>> 
>> Best
>>        Sebastian
>> 
>> 
>> 
>>> 
>>>>> 
>>>>> This will not be the final url for the 3.3 development
>>>>> series, but
>>>>> 
>>>>> http://huchra.bufferbloat.net/~cero1/3.3/
>>>>> 
>>>>> has that.
>>>>> 
>>>>> I made a small dent in the qos/aqm problem there,
>>>>> (my intent was to basically treat the above as 'bql-41' -
>>>>> I wanted to treat 3.3 issues and bql issues separately,
>>>>> but lack time to do both, and 3.3 is going swimmingly, so...)
>>>>> 
>>>>> but I'm puzzled as to what you are seeing below.
>>>>> 
>>>>> 0) Did you enable the aqm script? If you merely run it
>>>>> without enabling it, nothing happens. Similarly, the qos script
>>>>> needs to be disabled.
>>>> 
>>>>        Sorry for not being clear, I always had only the module under test enabled, the other one was always disabled. One thing I noticed, when enabling QoS I get the "Applying changes" info widget and it will state "/etc/config/qos" while enabling AQM will not show any "/etc/config" info, but that might be purely cosmetic. Will investigate, as it looks somehow AQM is never really enabled.
>>>>        Question do I need to install any package under the system->software tab for AQM to fully work? I assume not.
>>> 
>>> No, aside from the web interface being as yet untested...
>>> 
>>>> 
>>>>> 
>>>>> 1) Neither the AQM nor qos script does ADSL overhead right,
>>>>> and I'd got puzzled on what was 'right' after fiddling with it.
>>>> 
>>>>        Well, I agree that the overhead calculation as implemented in generate.sh is quite dubious (it looks like a stochastic approach).
>>> 
>>> Completely dubious and probably dates back to before the stab work.
>>> 
>>>> So I used the fact that cewrowrt comes with quite recent tc and used tc's "stab" option as that seems theoretically solve both the ATM carrier packet quantization as well as the per packet overhead issues quite well.
>>> 
>>> Yes.
>>>> 
>>>>> 
>>>>> 2) both qos and aqm calculated the sfq 'limit' variable wrong, and
>>>>> neither did ipv6 work right at all.
>>>> 
>>>>        I still have no IPv6 available so I did not test that. And even with the limit error QoS still works okay. (And I quite sure so will AQM once I manage to actually activate it :) )
>>> 
>>> Well, my concern is mostly that bittorrent will misbehave worse under
>>> this system than otherwise.
>>> 
>>> Qos-scripts uses hfsc + sfq for two bins, and hfsc + red for two other
>>> bins. Both sfq and red have improvements that qos-scripts should now
>>> be automatically picking up - red was entirely broken before kernel
>>> 3.2, actually.
>>> 
>>> AQM-scripts - at least this cut at it - will use hfsc + sfqred for all
>>> bins, and saner limits for both sfq and the red component of sfqred
>>> which will hopefully
>>> 
>>> I have to admit that the simplest possible implementation of the new
>>> stuff in debloat is performing pretty well - which is merely htb + 1
>>> bin of sfqred.
>>> 
>>> So if you pull down the latest debloat from the deBloat repo, and just
>>> run a command line of
>>> 
>>> IFACE=ge00 QMODEL=htb_sfq_red UPLINK=whatever_in_kbits /usr/sbin/debloat
>>> 
>>> the results should be pretty good.
>>> 
>>> I'm thinking a two tier model (Best effort and background) will be
>>> pretty good, 3 tiers and
>>> I can emulate most of pfifo_fast's behavior, but I don't see a need
>>> for the 4 tier model in qos-scripts, but that's why we test...
>>> 
>>>> 
>>>>> 
>>>>> I believe, but don't remember, that at least those fixes got made in
>>>>> the 3.3rc4-1 code. Actually there's a better fix for the ipv6 issue
>>>>> than what's there…
>>>> 
>>>>        Ah, so I will keep changing my firmware :)
>>> 
>>> Like I said, it's mostly just scripts now.... no huge need for that.
>>> 
>>>>> 
>>>>> 3) I am not intending to stick with the aqm script as structured now,
>>>>> but to finish modifying the 'debloat' script to have all the features required.
>>>>> 
>>>>> that one has a bunch of semi-working queue models in it.
>>>>> 
>>>>> If yer gonna hack scripts, please take a look at that one.
>>>>> There are plenty of things it needs and the qos and aqm scripts
>>>>> are more feature complete, tho…
>>>> 
>>>>        OH, thanks for the pointer, I have not looked at debloat recently, but I am somewhat confused by the generate.sh and trulls.awk combination, so I hope that debloat is more accessible for non-programmers...
>>> 
>>> There is some really good stuff in the current combo, but I too found
>>> the amalagation of shell and awk kind of difficult. Wanted one
>>> language, with floating point, which was why I ended up
>>> going for lua, which has it's own problems too, but...
>>>> 
>>>> 
>>>>> 
>>>>> 4) re updates: I have to warn against doing sysupgrade "and keep files
>>>>> in place", as the based filesystem does change, and I'm not making
>>>>> huge attempts at dealing with that. so doing a backup
>>>>> then a sysupdate -n (-n meaning don't preserve files over the backup)
>>>>> is generally a good idea.
>>>> 
>>>>        Thanks for the advise, I actually reflashed the factory firmware for bql-40 and called it update, sorry for being unclear. Actually the installation flashing instructions (http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_flashing_instructions) were quite specific about which method one should use.
>>> 
>>> Yep. Large red letters and everything.
>>>> 
>>>> 
>>>>> 
>>>>> anyway:
>>>>> 
>>>>> commit be09b8c15b6dc6bf4cb7da3112c598138a9c77ef
>>>>> Author: Dave Taht <dave.taht@bufferbloat.net>
>>>>> Date:   Tue Feb 14 14:38:40 2012 +0000
>>>>> 
>>>>>    SFQ is limited in packets. RED is in bytes. tcrules.awk conflated these
>>>>> 
>>>>>    The original openwrt shaper took the RED byte calculation...
>>>>>    and reused it to specify a limit for sfq. However, sfq uses
>>>>>    packets rather than bytes, so it was specifying, say 16000 bytes
>>>>>    and translating that to 16000 packets.
>>>>> 
>>>>>    This was not an error I prior to 3.3, because SFQ had a
>>>>>    hard coded limit of 127 packets. It is now.
>>>>> 
>>>>>    So this commit puts a lower and upper bound on the maximum packets
>>>>>    that is sane, but is not pre 3.2 compatible.
>>>>> 
>>>>> commit 44f8febbd34686564516c3261a911bd7cffcf714
>>>> 
>>>>        Thanks a lot for the great project.
>>> 
>>> Getting there!
>>> 
>>>> Best
>>>>        Sebastian
>>>> 
>>>> 
>>>>> 
>>>>> 
>>>>> On Thu, Feb 23, 2012 at 6:21 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>>>>>> Hi Dave,
>>>>>> 
>>>>>> I finally got around to update from rc6 to bql-40, to try the ATM shaping. The update was a breeze, great work!
>>>>>>        I am sad to report that for my ATM link AQM does not work for me as well as QoS does. My measurement consists out of using ping to get the RTT to the first ISP hop (as taken from trace route) while concurrently saturating the up link with a dropbox upload (which I usually give that a headstart of 10 seconds to go into bandwidth ceiling): AQM gives the same bad avg RTT of 1.2 seconds as no shaping at all does, while QoS gives me an avg RTT of around 24ms (best case RTT is around 13ms on my link, so the link stays pretty useable).
>>>>>>        I tried to apply the same changes to /usr/lib/aqm/generate.sh and /usr/lib/qos/generate.sh to make the them better understand the peculiarities of my ATM adsl1 connection, but it seems I did something wrong for the AQM script since my change does not have any effect there… (both modified files attached). I usually only  shape up- and down-stream to 97% of the line rate, which works ok with QoS. (And all my tests have been done, very unscientifically, using my mac laptop over the 5GHz wireless band of the router… )
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>        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
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Dave Täht
>>>>> SKYPE: davetaht
>>>>> US Tel: 1-239-829-5608
>>>>> http://www.bufferbloat.net
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Dave Täht
>>> SKYPE: davetaht
>>> US Tel: 1-239-829-5608
>>> http://www.bufferbloat.net
>> 
> 
> 
> 
> -- 
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://www.bufferbloat.net

Re: [Cerowrt-devel] smoketest BQL-40 is out

[Dave Taht]

Well, it's too bad (in some ways!) you are upgrading to cable.

Just to confirm, that was on a ~760kb upload parameter?

Good stuff: high probabilistic packet drop, decent rtts, etc
Bad: Ping loss seems high.

On that workload I might try a much larger packet limit (say,
200-300), lower packet depth limit (say, 12), and a lower redflowlimit

On Fri, Feb 24, 2012 at 3:12 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Dave,
>
> I managed to squeeze that test in, hope it helps.
>
>
>
> On Feb 23, 2012, at 2:19 PM, Dave Taht wrote:
>
>> your min time is higher than I'd expected, but certainly the mean and
>> max and stddev have improved.
>>
>> Could you send the output of
>>
>> tc -s qdisc show dev ge00
>
>
> Here the BEFORE test run output:
> root@nacktmulle:~# tc -s qdisc show dev ge00
> qdisc hfsc 1: root refcnt 2 default 30
>  Sent 42751655 bytes 128031 pkt (dropped 1635, overlimits 244784 requeues 2)
>  backlog 0b 0p requeues 2
> qdisc sfq 100: parent 1:10 limit 60p quantum 1514b depth 24 headdrop divisor 1024
>  ewma 2 min 3174b max 9522b probability 0.12 ecn
>  prob_mark 0 prob_mark_head 0 prob_drop 0
>  forced_mark 0 forced_mark_head 0 forced_drop 0
>  Sent 10785394 bytes 96191 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
> qdisc sfq 200: parent 1:20 limit 60p quantum 1514b depth 24 headdrop divisor 1024
>  ewma 2 min 3174b max 9522b probability 0.12 ecn
>  prob_mark 0 prob_mark_head 0 prob_drop 0
>  forced_mark 0 forced_mark_head 0 forced_drop 0
>  Sent 72822 bytes 370 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
> qdisc sfq 300: parent 1:30 limit 60p quantum 1514b depth 24 headdrop divisor 1024
>  ewma 2 min 3174b max 9522b probability 0.12 ecn
>  prob_mark 0 prob_mark_head 0 prob_drop 972
>  forced_mark 0 forced_mark_head 0 forced_drop 3
>  Sent 31856604 bytes 31239 pkt (dropped 2438, overlimits 975 requeues 0)
>  backlog 0b 0p requeues 0
> qdisc sfq 400: parent 1:40 limit 60p quantum 1514b depth 24 headdrop divisor 1024
>  ewma 2 min 3174b max 9522b probability 0.12 ecn
>  prob_mark 0 prob_mark_head 0 prob_drop 0
>  forced_mark 0 forced_mark_head 0 forced_drop 0
>  Sent 36835 bytes 231 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
>
> And here AFTER the test run:
> root@nacktmulle:~# tc -s qdisc show dev ge00
> qdisc hfsc 1: root refcnt 2 default 30
>  Sent 51812429 bytes 170042 pkt (dropped 4040, overlimits 325311 requeues 2)
>  backlog 0b 0p requeues 2
> qdisc sfq 100: parent 1:10 limit 60p quantum 1514b depth 24 headdrop divisor 1024
>  ewma 2 min 3174b max 9522b probability 0.12 ecn
>  prob_mark 0 prob_mark_head 0 prob_drop 0
>  forced_mark 0 forced_mark_head 0 forced_drop 0
>  Sent 14805550 bytes 130775 pkt (dropped 24, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
> qdisc sfq 200: parent 1:20 limit 60p quantum 1514b depth 24 headdrop divisor 1024
>  ewma 2 min 3174b max 9522b probability 0.12 ecn
>  prob_mark 0 prob_mark_head 0 prob_drop 0
>  forced_mark 0 forced_mark_head 0 forced_drop 0
>  Sent 74783 bytes 387 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
> qdisc sfq 300: parent 1:30 limit 60p quantum 1514b depth 24 headdrop divisor 1024
>  ewma 2 min 3174b max 9522b probability 0.12 ecn
>  prob_mark 0 prob_mark_head 0 prob_drop 1067
>  forced_mark 0 forced_mark_head 0 forced_drop 40
>  Sent 36890173 bytes 38621 pkt (dropped 5546, overlimits 1107 requeues 0)
>  backlog 0b 0p requeues 0
> qdisc sfq 400: parent 1:40 limit 60p quantum 1514b depth 24 headdrop divisor 1024
>  ewma 2 min 3174b max 9522b probability 0.12 ecn
>  prob_mark 0 prob_mark_head 0 prob_drop 0
>  forced_mark 0 forced_mark_head 0 forced_drop 0
>  Sent 41923 bytes 259 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
>
>
>>
>> after a test run?
>
> Here is the ping probe with AQM at 97% of line rates (line up 512 k)
> --- netblock-75-79-143-1.dslextreme.com ping statistics ---
> 100 packets transmitted, 70 packets received, 30.0% packet loss
> round-trip min/avg/max/stddev = 10.246/92.621/203.575/39.855 ms
>
> So it looks the minimum and STD are quite variable between test runs...
>
>
> Best Regards
>        Sebastian
>
>>
>>>        Yes, that did the trick! Now AQM actually is even better than QoS for my worst case scenario, saturating uplink, starting one downlink elephant and open 93 media heavy tabs in the browser.
>>> I now get:
>>> 100 packets transmitted, 73 packets received, 27.0% packet loss
>>> round-trip min/avg/max/stddev = 33.941/108.083/177.825/22.795 ms
>>>
>>> while using QoS I got:
>>> 100 packets transmitted, 75 packets received, 25.0% packet loss
>>> round-trip min/avg/max/stddev = 18.111/181.506/325.416/45.006 ms
>>>
>>> AQM is even better behaved than QoS now. That is pretty cool.
>>>
>>> BTW the web AQM interface manged to set the enabled line in /etc/config/aqm just fine it just did not seem to manage to do the equivalent of /etc/init.d/aqm start.
>>>
>>> Cool stuff.
>>>
>>> Best
>>>        Sebastian
>>>
>>>
>>>
>>>>
>>>>>>
>>>>>> This will not be the final url for the 3.3 development
>>>>>> series, but
>>>>>>
>>>>>> http://huchra.bufferbloat.net/~cero1/3.3/
>>>>>>
>>>>>> has that.
>>>>>>
>>>>>> I made a small dent in the qos/aqm problem there,
>>>>>> (my intent was to basically treat the above as 'bql-41' -
>>>>>> I wanted to treat 3.3 issues and bql issues separately,
>>>>>> but lack time to do both, and 3.3 is going swimmingly, so...)
>>>>>>
>>>>>> but I'm puzzled as to what you are seeing below.
>>>>>>
>>>>>> 0) Did you enable the aqm script? If you merely run it
>>>>>> without enabling it, nothing happens. Similarly, the qos script
>>>>>> needs to be disabled.
>>>>>
>>>>>        Sorry for not being clear, I always had only the module under test enabled, the other one was always disabled. One thing I noticed, when enabling QoS I get the "Applying changes" info widget and it will state "/etc/config/qos" while enabling AQM will not show any "/etc/config" info, but that might be purely cosmetic. Will investigate, as it looks somehow AQM is never really enabled.
>>>>>        Question do I need to install any package under the system->software tab for AQM to fully work? I assume not.
>>>>
>>>> No, aside from the web interface being as yet untested...
>>>>
>>>>>
>>>>>>
>>>>>> 1) Neither the AQM nor qos script does ADSL overhead right,
>>>>>> and I'd got puzzled on what was 'right' after fiddling with it.
>>>>>
>>>>>        Well, I agree that the overhead calculation as implemented in generate.sh is quite dubious (it looks like a stochastic approach).
>>>>
>>>> Completely dubious and probably dates back to before the stab work.
>>>>
>>>>> So I used the fact that cewrowrt comes with quite recent tc and used tc's "stab" option as that seems theoretically solve both the ATM carrier packet quantization as well as the per packet overhead issues quite well.
>>>>
>>>> Yes.
>>>>>
>>>>>>
>>>>>> 2) both qos and aqm calculated the sfq 'limit' variable wrong, and
>>>>>> neither did ipv6 work right at all.
>>>>>
>>>>>        I still have no IPv6 available so I did not test that. And even with the limit error QoS still works okay. (And I quite sure so will AQM once I manage to actually activate it :) )
>>>>
>>>> Well, my concern is mostly that bittorrent will misbehave worse under
>>>> this system than otherwise.
>>>>
>>>> Qos-scripts uses hfsc + sfq for two bins, and hfsc + red for two other
>>>> bins. Both sfq and red have improvements that qos-scripts should now
>>>> be automatically picking up - red was entirely broken before kernel
>>>> 3.2, actually.
>>>>
>>>> AQM-scripts - at least this cut at it - will use hfsc + sfqred for all
>>>> bins, and saner limits for both sfq and the red component of sfqred
>>>> which will hopefully
>>>>
>>>> I have to admit that the simplest possible implementation of the new
>>>> stuff in debloat is performing pretty well - which is merely htb + 1
>>>> bin of sfqred.
>>>>
>>>> So if you pull down the latest debloat from the deBloat repo, and just
>>>> run a command line of
>>>>
>>>> IFACE=ge00 QMODEL=htb_sfq_red UPLINK=whatever_in_kbits /usr/sbin/debloat
>>>>
>>>> the results should be pretty good.
>>>>
>>>> I'm thinking a two tier model (Best effort and background) will be
>>>> pretty good, 3 tiers and
>>>> I can emulate most of pfifo_fast's behavior, but I don't see a need
>>>> for the 4 tier model in qos-scripts, but that's why we test...
>>>>
>>>>>
>>>>>>
>>>>>> I believe, but don't remember, that at least those fixes got made in
>>>>>> the 3.3rc4-1 code. Actually there's a better fix for the ipv6 issue
>>>>>> than what's there…
>>>>>
>>>>>        Ah, so I will keep changing my firmware :)
>>>>
>>>> Like I said, it's mostly just scripts now.... no huge need for that.
>>>>
>>>>>>
>>>>>> 3) I am not intending to stick with the aqm script as structured now,
>>>>>> but to finish modifying the 'debloat' script to have all the features required.
>>>>>>
>>>>>> that one has a bunch of semi-working queue models in it.
>>>>>>
>>>>>> If yer gonna hack scripts, please take a look at that one.
>>>>>> There are plenty of things it needs and the qos and aqm scripts
>>>>>> are more feature complete, tho…
>>>>>
>>>>>        OH, thanks for the pointer, I have not looked at debloat recently, but I am somewhat confused by the generate.sh and trulls.awk combination, so I hope that debloat is more accessible for non-programmers...
>>>>
>>>> There is some really good stuff in the current combo, but I too found
>>>> the amalagation of shell and awk kind of difficult. Wanted one
>>>> language, with floating point, which was why I ended up
>>>> going for lua, which has it's own problems too, but...
>>>>>
>>>>>
>>>>>>
>>>>>> 4) re updates: I have to warn against doing sysupgrade "and keep files
>>>>>> in place", as the based filesystem does change, and I'm not making
>>>>>> huge attempts at dealing with that. so doing a backup
>>>>>> then a sysupdate -n (-n meaning don't preserve files over the backup)
>>>>>> is generally a good idea.
>>>>>
>>>>>        Thanks for the advise, I actually reflashed the factory firmware for bql-40 and called it update, sorry for being unclear. Actually the installation flashing instructions (http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_flashing_instructions) were quite specific about which method one should use.
>>>>
>>>> Yep. Large red letters and everything.
>>>>>
>>>>>
>>>>>>
>>>>>> anyway:
>>>>>>
>>>>>> commit be09b8c15b6dc6bf4cb7da3112c598138a9c77ef
>>>>>> Author: Dave Taht <dave.taht@bufferbloat.net>
>>>>>> Date:   Tue Feb 14 14:38:40 2012 +0000
>>>>>>
>>>>>>    SFQ is limited in packets. RED is in bytes. tcrules.awk conflated these
>>>>>>
>>>>>>    The original openwrt shaper took the RED byte calculation...
>>>>>>    and reused it to specify a limit for sfq. However, sfq uses
>>>>>>    packets rather than bytes, so it was specifying, say 16000 bytes
>>>>>>    and translating that to 16000 packets.
>>>>>>
>>>>>>    This was not an error I prior to 3.3, because SFQ had a
>>>>>>    hard coded limit of 127 packets. It is now.
>>>>>>
>>>>>>    So this commit puts a lower and upper bound on the maximum packets
>>>>>>    that is sane, but is not pre 3.2 compatible.
>>>>>>
>>>>>> commit 44f8febbd34686564516c3261a911bd7cffcf714
>>>>>
>>>>>        Thanks a lot for the great project.
>>>>
>>>> Getting there!
>>>>
>>>>> Best
>>>>>        Sebastian
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Feb 23, 2012 at 6:21 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>>>>>>> Hi Dave,
>>>>>>>
>>>>>>> I finally got around to update from rc6 to bql-40, to try the ATM shaping. The update was a breeze, great work!
>>>>>>>        I am sad to report that for my ATM link AQM does not work for me as well as QoS does. My measurement consists out of using ping to get the RTT to the first ISP hop (as taken from trace route) while concurrently saturating the up link with a dropbox upload (which I usually give that a headstart of 10 seconds to go into bandwidth ceiling): AQM gives the same bad avg RTT of 1.2 seconds as no shaping at all does, while QoS gives me an avg RTT of around 24ms (best case RTT is around 13ms on my link, so the link stays pretty useable).
>>>>>>>        I tried to apply the same changes to /usr/lib/aqm/generate.sh and /usr/lib/qos/generate.sh to make the them better understand the peculiarities of my ATM adsl1 connection, but it seems I did something wrong for the AQM script since my change does not have any effect there… (both modified files attached). I usually only  shape up- and down-stream to 97% of the line rate, which works ok with QoS. (And all my tests have been done, very unscientifically, using my mac laptop over the 5GHz wireless band of the router… )
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>        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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Dave Täht
>>>>>> SKYPE: davetaht
>>>>>> US Tel: 1-239-829-5608
>>>>>> http://www.bufferbloat.net
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Dave Täht
>>>> SKYPE: davetaht
>>>> US Tel: 1-239-829-5608
>>>> http://www.bufferbloat.net
>>>
>>
>>
>>
>> --
>> Dave Täht
>> SKYPE: davetaht
>> US Tel: 1-239-829-5608
>> http://www.bufferbloat.net
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net