Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] cerowrt 3.3.8-1 and related
Date: Fri, 8 Jun 2012 08:19:23 -0400	[thread overview]
Message-ID: <CAA93jw4h3vU10wOw5-6KrLVXTpgBcuuKDJFA4N+8oUvWmXTVZw@mail.gmail.com> (raw)

I have updated cerowrt 3.3 to Linux version 3.3.8-1 and merged with
openwrt head.

My goal for this release was simply to get caught up with openwrt, then push
out the remaining useful cerowrt stuff into openwrt. After taking 3 weeks
off it's amazing how difficult it was to get back in sync.

Changes in this release:

+ Linux 3.3.8
+ netifd support (more dynamic application startup/shutdown management)
+ Bind 9.1.1-P1 (Fix for a CVE)
+ transmission and transmission web server (uTP) added
+ Jabber chat server added

- I accidentally took a step back on dnsmasq (2.61 to 2.59)
- Firewall rules still need work (transmission support, block port 81, too)
- High performance hang (#379 and friends) untested (but possibly improved)
- UPnP work needs to be folded in
- quagga and gpsd didn't build

There are exciting things happening on the quagga front with babel -
there is a security architecture being prototyped as I write that
looks promising.
As for the gpsd issue, there was a flurry of controversy over how best
to stick it in openwrt, and obviously whatever one I picked lost.

And, of course, fq_codel is running on all interfaces.

I will try to resolve these issues by sunday and get out a 3.3.8-2

Let me know if any new ones have cropped up.

-- 
Dave Täht
SKYPE: davetaht
http://ronsravings.blogspot.com/

             reply	other threads:[~2012-06-08 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 12:19 Dave Taht [this message]
2012-06-08 14:54 ` Dave Taht
2012-06-14 17:36   ` Maciej Soltysiak
2012-06-14 18:37     ` 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=CAA93jw4h3vU10wOw5-6KrLVXTpgBcuuKDJFA4N+8oUvWmXTVZw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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