Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
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:37:02 -0700	[thread overview]
Message-ID: <CAA93jw6ND5rvKYSgVSOtf3wsQAAA8ZeaWc-MYCbtq5W6JBOmSw@mail.gmail.com> (raw)
In-Reply-To: <20140624160944.41e7317d@nehalam.linuxnetplumber.net>

On Tue, Jun 24, 2014 at 4:09 PM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> 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

I think bug 442 is universal across openwrt derived versions for the
last 5+ months. There is (no longer) any real difference between the
network stacks of cero and openwrt. I do think cero triggers it more
often by using adhoc mode, multiple wifi interfaces, and routing, and
I'd suggest to those using it to disable the guest and adhoc
interfaces entirely and see what happens. (definately kill adhoc
unless you are using it)

otherwise...

I too, despair. What I have been doing is developing means to saturate
links for long periods, take big packet captures, and for all that
I've only seen that bug 3 times, all 3 uncaptured. Yet others get it
all the time.

It is costing users hair, me time, and money I cannot spend on this
project, and hurting other efforts. I would have released a "stable"
version months ago if it wasn't for this.

I'll miss you if you leave! but if you had a stabler version that you
liked, you can regress to that - or by all means! give modern dd-wrt a
shot - it's got most of the core features cero has by now, and I
haven't tried it lately.

-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

  reply	other threads:[~2014-06-24 23:37 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
2014-06-24 23:37   ` Dave Taht [this message]
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=CAA93jw6ND5rvKYSgVSOtf3wsQAAA8ZeaWc-MYCbtq5W6JBOmSw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=stephen@networkplumber.org \
    /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