[Cerowrt-devel] next cerowrt release plan (of sorts)

[Cerowrt-devel] next cerowrt release plan (of sorts)

[Dave Taht]

I took a few days off to get back to the east coast, take care of a
few family matters, and visit culturecon 2012 in Philly and Boston,
where I learned that "agile" had established a theoretical framework
around few things I was already doing (continuous integration,
engagement with testers and users, short development cycles, small
feature improvements, etc), that might guide some of my future
behavior around this project.

I liked very much the concept of just dealing with a small backlog of
items for a given 2 week (or less) scrum. It makes the overwhelming
backlog of 150 bugs in the cerowrt db along with coping with the
prospect of having to fix 2,000,000,000 machines in the long run a
little less overwhelming!

I have a backlog of related reading to do...

While I didn't drink all the kool-aid at the conferences, (I was
attracted to the kanban concept, and need to think about the
sociocratic principles as outlined in:
http://www.amazon.com/We-People-Consenting-Deeper-Democracy/dp/0979282705
) I did meet a lot of interesting people and got a chance to exercise
the non-coding portion of my brain a bit.

So while I did that and tried to also deal with the funding floor
problem, I did get some bits of cerowrt done

+ updated quagga and babeld to git head
+ Merge with openwrt, which contains a major upgrade to
wireless-compat and the usual ream of bug fixes
+ Fixed yet another CVE in bind
+ Added aiccu and ipset back into the build. I don't know when ipset
vanished, sorry about that.


- Along the way I managed to break opkg support. I note that a very
important and out-of-openwrt tree feature has been in cerowrt for a
while - that of the ability to sign packages, added by stephen walker
a while back. Due to the need for manual intervention to actually sign
packages, I've never actually used it, and now both opkg and opkg
with-signing are broken as I write in the main trees. Apologies.

My own focus for this release is to be able to A/B the current linux
codel and the ns2 implementation I put in the last cerowrt release in
the same firmware, to determine (after lots of testing!) which is
better. I've also burned a lot of time trying to come up with a
wfq_codel, that uses a codel implementation with a few single fifio
assumptions removed and some saner support for a background queue for
things like bittorrent. There will also need to be patches to
iproute2. Getting those kernel modules and iproute2 patches done is my
personal blocker for getting a new release out. Simultaneously I plan
on getting an x86 version of the kernel done on 3.6-rcX....

I'd like very much to get aqm-scripts/simple_qos.sh actually pulling
data from the luci web page and conf file, too, but find my own gui
and uci skills lacking. anyone? I find the qos-script's usage of awk
and sh to be impossible to understand and would prefer to just come up
with something in lua that could do the job - particularly as I'd like
to be able to A/B/C the various variants of the underlying algos via
remote control on the testbed boxes.... but I don't care how it
interfaces, just so that (someone!) comes up with an interface.


Other things in my backlog are two multicast responder-like daemons -
but can't remember their names mldna?
Need to give gw.home.lan a DNS entry for dnsmasq


The code name for this release attempt is "sugarland" -  see
http://esr.ibiblio.org/?p=4566 for details

I'm shooting for wednesday.
If you have trivial feature requests, please make 'em now!
If you have code you want to check in, please get them in by tuesday!


-- 
Dave Täht

Re: [Cerowrt-devel] next cerowrt release plan (of sorts)

[Maciej Soltysiak]

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

On Sun, Sep 16, 2012 at 4:02 PM, Dave Taht <dave.taht@gmail.com> wrote:
> Other things in my backlog are two multicast responder-like daemons -
> but can't remember their names mldna?
It was minissdpd and miniupnpd, which are pre-requisites for allowing
minidlna to work between multiple network segments like we have in
cerowrt with 172.30.42.X/Y/Z...

What needs to be done is:
1) add minissdpd and miniupnpd to the build
2) patch their default configs to cater for lan->se00 sw00 sw10 and wan->ge00

miniupnpd will also allow portforwarding negotiation for things like
IM clients and, say, uTorrent. Also, it will score in netalyzr support
for UPNP.

> If you have trivial feature requests, please make 'em now!
> If you have code you want to check in, please get them in by tuesday!
See attached CRLF file. Since I had trouble and low patience for
getting a normal cero build to even get a new package in, sorry for
sending non-patch file with instructions. If it's unacceptable, please
let me know, I'll try to juggle time to try again.

p.s. have fun in Sugarland :-)

Regards,
Maciej

[-- Attachment #2: minissdp_miniupnpd_cero.txt --]
[-- Type: text/plain, Size: 1803 bytes --]

== 1. MINISSDPD Source ==
Example openwrt build which includes is at:
http://enduser.subsignal.org/~trondah/tree/feeds/custom/minissdpd/

On a running openwrt I can just:
http://enduser.subsignal.org/~trondah/latest-release-is-r33409/packages/minissdpd_1.2-1_ar71xx.ipk

== 2. MINISSDPD Config ==
Replace lan to a space-delimited list of internal interfaces.

vi /etc/config/minissdpd (http://enduser.subsignal.org/~trondah/tree/feeds/custom/minissdpd/files/)

--- minissdpd.old
+++ minissdpd
@@ -1,4 +1,4 @@
 config 'minissdpd' 'config'
        option 'enabled' '1'
        option 'log_output' '0'
-       option 'internal_iface' 'lan'
+       option 'internal_iface' 'se00 sw00 sw10'



/etc/init.d/minissdpd enable
/etc/init.d/minissdpd start

== 3. MINIUPNPD Source ==
OpenWRT has it in the build, so probably should be easy to include in Cero. Please include the luci-app-miniupnpd too.
http://downloads.openwrt.org/attitude_adjustment/12.09-beta/ar71xx/generic/packages/

However, it might be prudent to pull a 1.7 version or a CVS - I think I was told it contains some patches for doing a better job coexisting with minissdpd.

On a running openwrt I can just:
http://enduser.subsignal.org/~trondah/latest-release-is-r33409/packages/miniupnpd_1.7-1_ar71xx.ipk

== 4. MINIUPNPND Config ==

vi /etc/config/upnpd

--- upnpd.old
+++ upnpd
@@ -6,8 +6,8 @@
        option log_output '0'
        option download '1024'
        option upload '512'
-       option external_iface 'wan'
-       option internal_iface 'lan'
+       option external_iface 'ge00'
+       option internal_iface 'se00 sw00 sw10'
        option port '5000'
        option uuid '61809265-e55e-43dd-92d1-8b1cc9c0dd5c'


/etc/init.d/miniupnpd enable
/etc/init.d/miniupnpd start

Re: [Cerowrt-devel] next cerowrt release plan (of sorts)

[Török Edwin]

On 09/16/2012 05:02 PM, Dave Taht wrote:
> 
> I'm shooting for wednesday.
> If you have trivial feature requests, please make 'em now!
> If you have code you want to check in, please get them in by tuesday!

Just noticed that WiFi doesn't work with my Android phone anymore. It works with my other devices.
Don't know when this happened (WiFi is off on the phone most of the time), will have to do some more digging and file a proper bug report.
Any hints? (the 2.4Ghz SSID doesn't show up at all on a scan from my Android)

--Edwin

Re: [Cerowrt-devel] next cerowrt release plan (of sorts)

[Török Edwin]

On 09/17/2012 08:02 PM, Török Edwin wrote:
> On 09/16/2012 05:02 PM, Dave Taht wrote:
>>
>> I'm shooting for wednesday.
>> If you have trivial feature requests, please make 'em now!
>> If you have code you want to check in, please get them in by tuesday!
> 
> Just noticed that WiFi doesn't work with my Android phone anymore. It works with my other devices.
> Don't know when this happened (WiFi is off on the phone most of the time), will have to do some more digging and file a proper bug report.
> Any hints? (the 2.4Ghz SSID doesn't show up at all on a scan from my Android)
> 

Nevermind, changing it to be on channel 11 instead of channel 12 makes it show up on Android.
Apparently channel 12 is not supported there.

Sorry for the noise,
--Edwin

Re: [Cerowrt-devel] next cerowrt release plan (of sorts)

[Dave Taht]

I continue to hack primarily on getting a bunch of codels primed for
this release, on x86, working with htb and a few other things in
conjunction.

Preliminary notes:

ns2_codel smokes straight codel under heavy load. In my 150
bidirectional stream test, ns2_codel can reduce a backlog far more
than codel.

It's difficult to tell the difference between fq_codel (using the
original codel) and nfq_codel, but it seems to be a win. Have tons of
data that I'd need to plot.

Using a smaller quantum than 1514 in the general case seems to be a
good idea, it pushes big data to the back of the queue and allows
interactive traffic to work mildly better.

I completed "efq_codel" which attempts to remove all single fifo
dependencies from the codel algo.

I think I succeeded in doing that. It's kind of ugly though.

Performance is comparable to nfq_codel, and perhaps, with some more
thought as to how to grow the window, there's some room to manoeuvre
ultimately that might drain the horizontal queue better, but I'll
settle for "equivalent" right now.

bfq_codel - which is my first attempt at handling the bittorrent
problem - currently crashes. If I can't get it to work before the end
of today, I'm going to bail on it for this release. I'm not happy with
the idea anyway...

Working with htb at speeds below 4Mbit is a real disappointment. Given
that a big packet at 1Mbit is 13ms I'm tempted to set codel's target
at above that when fiddling at these low rates to see what happens.
Adding hfsc + fq_codel to the mix of tests as I write (or rather, as I
compile new kernels)

I think having flows > 1024 is a small win.

also:

I will try to get the daap stuff done tonight

also:

Steven walker has fixed package signing in the Cerowrt-3.3 repo. I'm
still throwing ENOTIME errors, and he's included some interesting,
fragmentary documentation on it, which could use a third party to
try...

One thought of mine would be that it would be nice to allow for
multiple signing keys on the keyring, so that folk that build more of
cero (or one day openwrt) and are trusted, can also make their binary
repos available.

Anyway, he laid out the following instructions. If there is anyone out
there building cero, they might want to try this....


Add your key:
mkdir -p /tmp/etc/opkg
gpg --export <key> | <buildroot>/staging_dir/host/bin/opkg-key -o /tmp add -
Push /tmp/etc/opkg/{secring,trustdb,trusted}.gpg to
cerofiles-3.3/files/etc/opkg/

The signing script would:
Download bin/ar71xx/packages/Packages, sign it with
https://github.com/dtaht/Cerowrt-3.3/blob/master/package/Makefile#L64
and upload Packages.sig
Download the images in bin/ar71xx/, sign them with
https://github.com/dtaht/Cerowrt-3.3/blob/master/include/image.mk#L157
and upload *.asc

Enable signature checking on an opkg-gpg enabled build:
echo "option check_signature 1" >> /etc/opkg.conf

Packages.sig should be verified upon an opkg update




On Sun, Sep 16, 2012 at 7:02 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I took a few days off to get back to the east coast, take care of a
> few family matters, and visit culturecon 2012 in Philly and Boston,
> where I learned that "agile" had established a theoretical framework
> around few things I was already doing (continuous integration,
> engagement with testers and users, short development cycles, small
> feature improvements, etc), that might guide some of my future
> behavior around this project.
>
> I liked very much the concept of just dealing with a small backlog of
> items for a given 2 week (or less) scrum. It makes the overwhelming
> backlog of 150 bugs in the cerowrt db along with coping with the
> prospect of having to fix 2,000,000,000 machines in the long run a
> little less overwhelming!
>
> I have a backlog of related reading to do...
>
> While I didn't drink all the kool-aid at the conferences, (I was
> attracted to the kanban concept, and need to think about the
> sociocratic principles as outlined in:
> http://www.amazon.com/We-People-Consenting-Deeper-Democracy/dp/0979282705
> ) I did meet a lot of interesting people and got a chance to exercise
> the non-coding portion of my brain a bit.
>
> So while I did that and tried to also deal with the funding floor
> problem, I did get some bits of cerowrt done
>
> + updated quagga and babeld to git head
> + Merge with openwrt, which contains a major upgrade to
> wireless-compat and the usual ream of bug fixes
> + Fixed yet another CVE in bind
> + Added aiccu and ipset back into the build. I don't know when ipset
> vanished, sorry about that.
>
>
> - Along the way I managed to break opkg support. I note that a very
> important and out-of-openwrt tree feature has been in cerowrt for a
> while - that of the ability to sign packages, added by stephen walker
> a while back. Due to the need for manual intervention to actually sign
> packages, I've never actually used it, and now both opkg and opkg
> with-signing are broken as I write in the main trees. Apologies.
>
> My own focus for this release is to be able to A/B the current linux
> codel and the ns2 implementation I put in the last cerowrt release in
> the same firmware, to determine (after lots of testing!) which is
> better. I've also burned a lot of time trying to come up with a
> wfq_codel, that uses a codel implementation with a few single fifio
> assumptions removed and some saner support for a background queue for
> things like bittorrent. There will also need to be patches to
> iproute2. Getting those kernel modules and iproute2 patches done is my
> personal blocker for getting a new release out. Simultaneously I plan
> on getting an x86 version of the kernel done on 3.6-rcX....
>
> I'd like very much to get aqm-scripts/simple_qos.sh actually pulling
> data from the luci web page and conf file, too, but find my own gui
> and uci skills lacking. anyone? I find the qos-script's usage of awk
> and sh to be impossible to understand and would prefer to just come up
> with something in lua that could do the job - particularly as I'd like
> to be able to A/B/C the various variants of the underlying algos via
> remote control on the testbed boxes.... but I don't care how it
> interfaces, just so that (someone!) comes up with an interface.
>
>
> Other things in my backlog are two multicast responder-like daemons -
> but can't remember their names mldna?
> Need to give gw.home.lan a DNS entry for dnsmasq
>
>
> The code name for this release attempt is "sugarland" -  see
> http://esr.ibiblio.org/?p=4566 for details
>
> I'm shooting for wednesday.
> If you have trivial feature requests, please make 'em now!
> If you have code you want to check in, please get them in by tuesday!
>
>
> --
> Dave Täht



-- 
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"

Re: [Cerowrt-devel] next cerowrt release plan (of sorts)

[Dave Taht]

On Sun, Sep 16, 2012 at 11:48 AM, Maciej Soltysiak <maciej@soltysiak.com> wrote:
> On Sun, Sep 16, 2012 at 4:02 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> Other things in my backlog are two multicast responder-like daemons -
>> but can't remember their names mldna?
> It was minissdpd and miniupnpd, which are pre-requisites for allowing
> minidlna to work between multiple network segments like we have in
> cerowrt with 172.30.42.X/Y/Z...
>
> What needs to be done is:
> 1) add minissdpd and miniupnpd to the build
> 2) patch their default configs to cater for lan->se00 sw00 sw10 and wan->ge00
>
> miniupnpd will also allow portforwarding negotiation for things like
> IM clients and, say, uTorrent. Also, it will score in netalyzr support
> for UPNP.
>
>> If you have trivial feature requests, please make 'em now!
>> If you have code you want to check in, please get them in by tuesday!
> See attached CRLF file. Since I had trouble and low patience for
> getting a normal cero build to even get a new package in, sorry for
> sending non-patch file with instructions. If it's unacceptable, please
> let me know, I'll try to juggle time to try again.
>
> p.s. have fun in Sugarland :-)

I see that a minidlna package is in the main package feed for openwrt,
but it doesn't want to feeds install. The version you pointed me at in
the previous mail is someone's checkout of another feed. It would be
more fruitful to have this be working in openwrt first....

It could be that my feeds database is borked?

same goes for sdpd. I'd kind of prefer the maintainer of the package
push it out into openwrt mainline, or make it available as an official
alternate feed I can pull a checkout from in cerowrt, rather than copy
directly into ceropackages.

Does "trondah" have a public email addy?

cc-ing our packager emeritus...

>
> Regards,
> Maciej



-- 
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"

Re: [Cerowrt-devel] next cerowrt release plan (of sorts)

[Stephen Walker]

On Mon, Sep 17, 2012 at 3:53 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Sun, Sep 16, 2012 at 11:48 AM, Maciej Soltysiak <maciej@soltysiak.com> wrote:
>> On Sun, Sep 16, 2012 at 4:02 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>> Other things in my backlog are two multicast responder-like daemons -
>>> but can't remember their names mldna?
>> It was minissdpd and miniupnpd, which are pre-requisites for allowing
>> minidlna to work between multiple network segments like we have in
>> cerowrt with 172.30.42.X/Y/Z...
>>
>> What needs to be done is:
>> 1) add minissdpd and miniupnpd to the build
>> 2) patch their default configs to cater for lan->se00 sw00 sw10 and wan->ge00
>>
>> miniupnpd will also allow portforwarding negotiation for things like
>> IM clients and, say, uTorrent. Also, it will score in netalyzr support
>> for UPNP.
>>
>>> If you have trivial feature requests, please make 'em now!
>>> If you have code you want to check in, please get them in by tuesday!
>> See attached CRLF file. Since I had trouble and low patience for
>> getting a normal cero build to even get a new package in, sorry for
>> sending non-patch file with instructions. If it's unacceptable, please
>> let me know, I'll try to juggle time to try again.
>>
>> p.s. have fun in Sugarland :-)
>
> I see that a minidlna package is in the main package feed for openwrt,
> but it doesn't want to feeds install. The version you pointed me at in
> the previous mail is someone's checkout of another feed. It would be
> more fruitful to have this be working in openwrt first....
>
> It could be that my feeds database is borked?
>
> same goes for sdpd. I'd kind of prefer the maintainer of the package
> push it out into openwrt mainline, or make it available as an official
> alternate feed I can pull a checkout from in cerowrt, rather than copy
> directly into ceropackages.
>
> Does "trondah" have a public email addy?
>
> cc-ing our packager emeritus...

Cshore would be the person to ask as he maintains miniupnpd and also
owns https://dev.openwrt.org/ticket/8988 for minissdpd.

>>
>> Regards,
>> Maciej
>
>
>
> --
> Dave Täht
> http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
> with fq_codel!"

Re: [Cerowrt-devel] next cerowrt release plan (of sorts)

[Michael Richardson]

>>>>> "Dave" == Dave Taht <dave.taht@gmail.com> writes:
    Dave> involved in the codel effort is at this upcoming ietf in vancouver, so
    Dave> it is my hope that we can get together and get a set of common
    Dave> simulations against the algorithmic variants, and decide on something
    Dave> then.

What are the plans?  Maybe we need a doodle?

[Cerowrt-devel] next cerowrt release plan (of sorts)

[Dave Taht]

3.3.8-10 and -11 were not as good as I'd hoped.

I have been doing continuous integration while on this trip but have
not been in a position to test anything. And after -11 - well, I'm not
putting out anything without more serious testing.

The biggest issue we have is that there are multiple attempts in
motion to improve codel's behavior under load. We have a half dozen
competing ideas that all need simulation and testing. Nearly everybody
involved in the codel effort is at this upcoming ietf in vancouver, so
it is my hope that we can get together and get a set of common
simulations against the algorithmic variants, and decide on something
then.

So my plan is to get a cerowrt build out sometime next week. (aug 1-3)

An issue I fixed in the cerowrt source tree today is ipv6 default
routes weren't making it out via babel - It's apparently fixed now,
(thx to a patch from denis and now in the net-next linux tree).

Pretty much everything else is now stable - for example, dnsmasq 2.62
with AAAA reverse DNS and dhcpv6 support is now in openwrt mainline.

As things grow stabler in openwrt/cerowrt, the linux mainline tree
continues to advance. I'd like to backport Eric Dumazet's TCP small
queues work to this release of cerowrt, if I get time. This looks very
promising to reduce host bufferbloat still further:
http://lwn.net/Articles/506237/ - and de-heisenbug some tests.

BUT THAT'S IT.

For example: I am not planning on adding TCP fast open support on this
go-round. I do hope to ensure that TCP fast open can work, and perhaps
put means in play to measure it working or not, but that's it.

Anyway, I got off all my mailing lists while I took this break. So I
am out of touch. And refreshed.

If you have any bug fixes for cerowrt let me know soonest.

-- 
Dave Täht