From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.44-5 released
Date: Tue, 24 Jun 2014 16:09:44 -0700 [thread overview]
Message-ID: <20140624160944.41e7317d@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAA93jw6jmWssdQ-NJqpN6gU0mztggpknsyu4X8N2pRjpUVC4xA@mail.gmail.com>
On Tue, 24 Jun 2014 15:33:59 -0700
Dave Taht <dave.taht@gmail.com> wrote:
> + resync with openwrt head
> updates to iw, mac80211
> various routing table fixes in netifd
>
> + dnsmasq 2.71 with mini-gmp and libnettle mainlined
> also moved into procd for better automagic restart
> (this leaves babel as the only major daemon not managed by procd. sigh)
>
> - totally untested (I tested -4 pretty thoroughly though)
> I won't have time for this personally til later this week.
> - still no answer for bug 442 - I do get bad things to happen on a
> ubnt device now
> - left off on the homewrt integration for now
>
> I need to get around to submitting sqm upstream again, but am busy on
> other tasks.
> IETF is coming up, also.
>
Is this going to be any more stable? I almost about to give up
on cerowrt for home use and go to dd-wrt or something else.
Wireless still crashes once a week with 3.10.36-6
next prev parent reply other threads:[~2014-06-24 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 22:33 Dave Taht
2014-06-24 23:09 ` Stephen Hemminger [this message]
2014-06-24 23:37 ` Dave Taht
2014-06-25 2:15 ` 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=20140624160944.41e7317d@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--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