From: Paul Handly <paul@hand.ly>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt 3.8.6-2 released
Date: Sun, 7 Apr 2013 14:56:50 -0400 [thread overview]
Message-ID: <88B19169-B314-4036-AFEB-326CD5B5AC52@hand.ly> (raw)
In-Reply-To: <CAA93jw4Hq9C8dAR=RNt50jkQS-vcZfJOO4hgo9SiMt0JKhiQ6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2973 bytes --]
Any chance of getting a miniupnpd package refresh added to the TODO? I've been hitting a SSDP bug when interfaces have IPv6 addresses assigned, and it LOOKS like that code path has been refactored since 1.6.20110730.
3.7.5-2 has been rock-solid on my WNDR3800.
On Apr 7, 2013, at 7:35 AM, Dave Taht <dave.taht@gmail.com> wrote:
> This is mostly just a refresh of openwrt head into Cerowrt, notably a kernel update to 3.8.6. My hope is to merge some patches up into openwrt this week as I'm in berlin hanging with several openwrt devs.
>
> Cerowrt 3.8.6-2 might gnaw your children to death, cause cancer, and world famine, so I'd advise against installing it as your default router.
>
> Things like ipv6 and wireless are totally untested.
>
> Also as there is a ton of newer stuff on the todo list (more suggestions wanted - is there anything interesting in kernel 3.8?) that isn't in here, that might get done over the next month or two, so there really isn't a lot of point to the update that I can see besides establishing a base for further development, but if you are bored and want to see what stuff I broke, get it at:
>
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.8.6-2/
>
>
> todo list:
>
> * change name to Berlin release
> ** DONE update to dnsmasq 2.66rc4
> ** DONE update iptables
> But is there npt66 support?
> ** DONE fix igmp patch
> ** DONE update quagga, netperf,
> ** TODO babel refresh
> ** DONE Change name to berlin
> ** DONE Fix kernel config for additional TCPs
> ** Refresh other ceropackages
> *** TODO update babeld
> *** TODO Fix Bind (update from openwrt main?)
> *** TODO update iproute2 (3.7)
> *** TODO Update gpsd
> *** TODO FIx kerberos package again (does anyone care?)
> ** Review bug list
>
> * TODO New Work under consideration
> ** Add support for still shipping buffalo WZR router
> ** Gui for simple_qos
> ** Wifi sort on dequeue from aggregate
> ** wifi Xfq_codel at driver level
> ** sfqcodel from ns2
> ** cake in C
> ** Make independently buildable again
> ** Check into bismark's status
> ** HTB improvements (try to scale to 120Mbits)
> ** ACC - measure outgoing rate dynamically (see gargoyle project)
> ** RFC6013 related fixes
> ** homenet rfc
> ** hipnet rfc
> ** package signing
> ** src/dst routing
> ** mdnsext http://datatracker.ietf.org/doc/draft-lynn-mdnsext-requirements/?include_text=1
>
> I am travelling heavily through the eu (anyone at battlemesh? uknof? Rite?) and am not generally going to have a lot of time for this until after late may, but will try to slide stuff in in relation to wherever I am and whoever I'm nearby....
>
> --
> Dave Täht
>
> 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
-pH
[-- Attachment #2: Type: text/html, Size: 3758 bytes --]
next prev parent reply other threads:[~2013-04-07 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 11:35 Dave Taht
2013-04-07 12:23 ` Maciej Soltysiak
2013-04-07 18:56 ` Paul Handly [this message]
2013-04-07 19:20 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88B19169-B314-4036-AFEB-326CD5B5AC52@hand.ly \
--to=paul@hand.ly \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox