From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 72E2821F214 for ; Mon, 17 Feb 2014 14:50:40 -0800 (PST) Received: by mail-qa0-f47.google.com with SMTP id j5so22701709qaq.34 for ; Mon, 17 Feb 2014 14:50:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fpqJNeCZFPLyL2tcrbcF4t0Vyx4O+JPetNQ6LksQ/y4=; b=ImZxPwAqHxM1/tBaagFeA/sDYvUQFvZ9a61rLXZ5XTm+k6DzmAeXFgM7DTZqYU0VMF PtEG15A7Wj99sY1GCGwhzDUhAOuPZ2ZYkF2qE73CPuoQauhZjpIJsvuzsTEGhzPv+yUQ VhfT+wOPcM37xbwzBe0OGCuwGDI3MfVvrIyFARyqXIg9SV+1y5TuGJ1Q1axSRT/AxEHs jAPmhsPHG2dIQPlcnC3ozKgaGQAkAsxosIQRlziCdHLfSUWa/ptatqvJgoGaVSjSM36F t+QrDuFBeMekDgCEMmPTel0DlAtzFJG9Ad46ZFRlvuwFTgL+45WCeaYsA0hP7oYS+7LG VKiA== MIME-Version: 1.0 X-Received: by 10.140.98.203 with SMTP id o69mr5347260qge.102.1392677438897; Mon, 17 Feb 2014 14:50:38 -0800 (PST) Received: by 10.224.27.133 with HTTP; Mon, 17 Feb 2014 14:50:38 -0800 (PST) In-Reply-To: References: <53028C06.4000903@xyz.am> <53028C35.9010904@imap.cc> Date: Mon, 17 Feb 2014 17:50:38 -0500 Message-ID: From: Dave Taht To: Fred Stratton Content-Type: multipart/alternative; boundary=001a1139849c08420a04f2a1fce2 Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Fwd: Re: more steps forward X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Feb 2014 22:50:40 -0000 --001a1139849c08420a04f2a1fce2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Heh. That's cool. It might be possible to leverage their tests for up/down/latency testing... usable xml too. http://www.speedtest.net/speedtest-config.php On Mon, Feb 17, 2014 at 5:28 PM, Dave Taht wrote: > > > > On Mon, Feb 17, 2014 at 5:24 PM, Fred Stratton wrot= e: > >> >> >> >> -------- Original Message -------- Subject: Re: [Cerowrt-devel] more >> steps forward Date: Mon, 17 Feb 2014 22:24:06 +0000 From: Fred >> Stratton To: Sebastian >> Moeller , >> cerowrt-devel@lists.bufferbloat.net >> >> For later in the process, this has appeared: >> https://github.com/sivel/speedtest-cli >> >> > Possibly useful. 500 lines of python. Could probably rewrite in C in less= . > > >> >> >> On 17/02/14 21:52, Sebastian Moeller wrote: >> > HI Dave, >> > >> > On Feb 17, 2014, at 20:36 , Dave Taht wrote: >> > >> >> -1) we are working on modernizing, replicating and securing key bits = of the >> >> bufferbloat.net infrastructure. >> >> >> >> 0) I would like to push the sqm scripts and gui up to openwrt-devel >> >> for review soon. It's still missing some things I'd like - inbound >> >> diffserv to BE squashing, >> >> support for dynamically setting the target, >> > Setting the target is still on my todo list; as you noted in the past= we will run into an issue once the target gets larger than interval though= ; what about setting interval to max(100ms, 100ms + (-5ms + new_target)), s= o that even for long targets we have some interval to average over? Anybody= with a better idea, please chime in. (My plan is to allow the user to spec= ify a target ala "12ms" or leave it empty for default or "auto" to do the f= ree scaling) >> > >> > But my most urgent point is making it possible to actually disable SQM= after enabling it :) >> > >> > Also of medium importance would be mutual exclusivity with regards to = openwrt QOS, the user should only be able to activate one of them... (Note = that the openwrt recommendation for he existing 3 qos systems is simply, do= not run/enable them concurrently, so doing nothing might be an option here= ) >> > >> > I currently am pressed for time, so I can not promise to finish any of= these three goals any time soon, but I will try... >> > >> > best regards >> > Sebastian >> > >> >> a drr emulation of what free.fr does, some stuff I have for emulating >> >> typical dsl and cable modem behavior... and any way of more easily >> >> doing custom prioritizations, but it is what it is, and can be >> >> improved with more eyeballs on it. >> >> >> >> 1) I am planning to rebase the cerowrt-next tree with a cleaner >> >> patchset, push as much up to openwrt as possible, and put it into >> >> cerowrt-3.10 on github. >> >> >> >> Along with that, rename ceropackages-3.3 to ceropackages-3.10. >> >> >> >> And retire cerowrt-next entirely. I don't really care much about the >> >> history lost here, >> >> I do care about having a clean patchset. >> >> >> >> (this is assuming Barrier Breaker, when frozen in the next quarter or= two >> >> stays on 3.10 for the ar71xx architecture.) >> >> >> >> This will become a longer term stable release for us. >> >> >> >> Most of that work is done, I'm still sorting through the patchsets on >> >> a couple fronts however, to cut them from, like dozens, to only a few >> >> that make coherent sense. >> >> >> >> I hope to get most of that out to openwrt-devel this week. >> >> >> >> 2) In terms of a shorter term stable release for us, it's evident tha= t >> >> it isn't going to be this month. My cup runneth over. >> >> >> >> I MIGHT get something stable enough to use as a test box >> >> after I finish item 1. >> >> >> >> 3) In sorting through the patchset I found a tiny patch that didn't >> >> make it upstream that is probably responsible for 90% of the new >> >> instruction traps. Not responsible for the older new ones, but right = now >> >> I can't even look at the instruction trap problem without crashing th= e >> >> router, so... >> >> >> >> 4) Got mosh working today for the first time. It's a cheap hack. >> >> >> >> I don't know if anybody else cares >> >> but as for me, I am so frequently blowing up my network and losing >> >> state on a dozen boxes >> >> that it's a relief to be able to cut over to pure mosh everywhere to >> >> survive that. >> >> >> >> 5) The latest mdnsresponder code landed, and the new hnetd and dns >> >> hybrid proxy code >> >> is being maintained in the homewrt group's repos, which I just added >> >> to cerowrt's feeds. >> >> >> >> This is the post-avahi, (probable) post-ahcp future, and it's got lot= s >> >> of rough edges as yet. >> >> >> >> building it as modules now. >> >> >> >> >> >> 6) I have *some* bcp38 code that works, and some ideas as to how to m= ake it >> >> "just work" *mostly* and be on by default, but it lacks uci and gui i= ntegration. >> >> >> >> Given the marked increase in spoofed udp attacks like the recent ntp = exploit, >> >> I'd like to get something that works "out there", but it's clearly a >> >> separate project >> >> that I'd like someone else to "own" and integrate. >> >> >> >> 7) Still would like to move babeld to run out of procd >> >> >> >> 8) The remainder of the backlog... >> >> >> >> -- >> >> Dave T=E4ht >> >> >> >> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subs= cribe.html >> >> _______________________________________________ >> >> Cerowrt-devel mailing list >> >> Cerowrt-devel@lists.bufferbloat.net >> >> https://lists.bufferbloat.net/listinfo/cerowrt-devel >> > _______________________________________________ >> > Cerowrt-devel mailing list >> > Cerowrt-devel@lists.bufferbloat.net >> > https://lists.bufferbloat.net/listinfo/cerowrt-devel >> >> >> >> >> _______________________________________________ >> Cerowrt-devel mailing list >> Cerowrt-devel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cerowrt-devel >> >> > > > -- > Dave T=E4ht > > Fixing bufferbloat with cerowrt: > http://www.teklibre.com/cerowrt/subscribe.html > --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html --001a1139849c08420a04f2a1fce2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Heh. That's cool. It might be possible to leverage the= ir tests for up/down/latency testing... usable xml too.

http://www.speedtest.net/spee= dtest-config.php


On Mon,= Feb 17, 2014 at 5:28 PM, Dave Taht <dave.taht@gmail.com> = wrote:



On Mon, Feb 17, 2014= at 5:24 PM, Fred Stratton <fredstratton@imap.cc> wrote:<= br>
=20 =20 =20



-------- Original Message --------
Subject: Re: [Cerowrt-devel] more steps forward
Date: Mon, 17 Feb 2014 22:24:06 +0000
From: Fred Stratton <fredstratton@xyz.am>
To: Sebastian Moeller <moeller0@gmx.de>, cerowrt-devel@lists.bufferbloat.net 


For later in the process, this has appeared:

https:=
//github.com/sivel/speedtest-cli
Possibly useful. 500 lines of python. Could probably rewr= ite in C in less.
 


On 17/02/14 21:52, Sebastian Moeller wrote:
> HI Dave,
>
> On Feb 17, 2014, at 20:36 , Dave Taht <dave.taht@gmail.com> wrote:
>
>> -1) we are working on modernizing, replicating and securing key bi=
ts of the
>> bufferbloat.n=
et infrastructure.
>>
>> 0) I would like to push the sqm scripts and gui up to openwrt-deve=
l
>> for review soon. It's still missing some things I'd like -=
 inbound
>> diffserv to BE squashing,
>> support for dynamically setting the target,
> 	Setting the target is still on my todo list; as you noted in the past=
 we will run into an issue once the target gets larger than interval though=
; what about setting interval to max(100ms, 100ms + (-5ms + new_target)), s=
o that even for long targets we have some interval to average over? Anybody=
 with a better idea, please chime in. (My plan is to allow the user to spec=
ify a target ala "12ms" or leave it empty for default or "au=
to" to do the free scaling)
>
> But my most urgent point is making it possible to actually disable SQM=
 after enabling it :)
>
> Also of medium importance would be mutual exclusivity with regards to =
openwrt QOS, the user should only be able to activate one of them… (=
Note that the openwrt recommendation for he existing 3 qos systems is simpl=
y, do not run/enable them concurrently, so doing nothing might be an option=
 here)
>
> I currently am pressed for time, so I can not promise to finish any of=
 these three goals any time soon, but I will try…
>
> best regards
> 	Sebastian
>
>> a drr emulation of what free.fr does, some stuff I have for emulating
>> typical dsl and cable modem behavior... and any way of more easily
>> doing custom prioritizations, but it is what it is, and can be
>> improved with more eyeballs on it.
>>
>> 1) I am planning to rebase the cerowrt-next tree with a cleaner
>> patchset, push as much up to openwrt as possible, and put it into
>> cerowrt-3.10 on github.
>>
>> Along with that, rename ceropackages-3.3 to ceropackages-3.10.
>>
>> And retire cerowrt-next entirely. I don't really care much abo=
ut the
>> history lost here,
>> I do care about having a clean patchset.
>>
>> (this is assuming Barrier Breaker, when frozen in the next quarter=
 or two
>> stays on 3.10 for the ar71xx architecture.)
>>
>> This will become a longer term stable release for us.
>>
>> Most of that work is done, I'm still sorting through the patch=
sets on
>> a couple fronts however, to cut them from, like dozens, to only a =
few
>> that make coherent sense.
>>
>> I hope to get most of that out to openwrt-devel this week.
>>
>> 2) In terms of a shorter term stable release for us, it's evid=
ent that
>> it isn't going to be this month. My cup runneth over.
>>
>> I MIGHT get something stable enough to use as a test box
>> after I finish item 1.
>>
>> 3) In sorting through the patchset I found a tiny patch that didn&=
#39;t
>> make it upstream that is probably responsible for 90% of the new
>> instruction traps. Not responsible for the older new ones, but rig=
ht now
>> I can't even look at the instruction trap problem without cras=
hing the
>> router, so...
>>
>> 4) Got mosh working today for the first time. It's a cheap hac=
k.
>>
>> I don't know if anybody else cares
>> but as for me, I am so frequently blowing up my network and losing
>> state on a dozen boxes
>> that it's a relief to be able to cut over to pure mosh everywh=
ere to
>> survive that.
>>
>> 5) The latest mdnsresponder code landed, and the new hnetd and dns
>> hybrid proxy code
>> is being maintained in the homewrt group's repos, which I just=
 added
>> to cerowrt's feeds.
>>
>> This is the post-avahi, (probable) post-ahcp future, and it's =
got lots
>> of rough edges as yet.
>>
>> building it as modules now.
>>
>>
>> 6) I have *some* bcp38 code that works, and some ideas as to how t=
o make it
>> "just work" *mostly* and be on by default, but it lacks =
uci and gui integration.
>>
>> Given the marked increase in spoofed udp attacks like the recent n=
tp exploit,
>> I'd like to get something that works "out there", bu=
t it's clearly a
>> separate project
>> that I'd like someone else to "own" and integrate.
>>
>> 7) Still would like to move babeld to run out of procd
>>
>> 8) The remainder of the backlog...
>>
>> --=20
>> Dave T=E4ht
>>
>> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt=
/subscribe.html
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



_______________________________________________
Cerowrt-devel mailing list
Ce= rowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel




--
Dave T=E4ht

Fixing bufferbloat with cerowrt: http:= //www.teklibre.com/cerowrt/subscribe.html=20



--
Dave T=E4ht

Fixi= ng bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.ht= ml=20
--001a1139849c08420a04f2a1fce2--