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"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] cerowrt-3.10.38-1 released
Date: Sun, 27 Apr 2014 12:16:26 -0700	[thread overview]
Message-ID: <CAA93jw6O7YwZHfixZ2LPJK5EQvCHecDo+HekQrvx2kzDpv6esg@mail.gmail.com> (raw)

On the previous try wifi stayed up 16hrs under a moderate load, and
fixed 2 of the 3 outstanding
dnssec/dnsmasq related issues so this rolls that up with a new kernel,
another noise rejection
patch for wifi, and downgrading the wifi multicast rate to the default 1mbit.

Get it at:

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.38-1/

+ merge with openwrt head
   ANI fix
   Some interface assignment stuff fixed
   Felix's queue patch (from previous release)
+ mcast_rate returned to default
+ Kernel upgrade to 3.10.38
   3.10.37 had a couple worthwhile looking patches, one for a routing bug
+ Tested with kindle, nexus 4, nexus 7 (new)

- it takes a while for checking the time to reset dnsmasq, and to
  get a default gw, thus some devices (a yamaha receiver, for one)
which try to get
  an address as soon as the ethernet goes up don't seem to get a gateway or
  dns right unless restarted after cero has fully initialized.

- untested with ipv6 (can't tunnel from this location, no native)

- on the (DSL) network I'm on I fail to get upstream dns servers

- still unknown what's going wrong after much traffic and much uptime.
Just because
I've only seen it fail once in 72 hours prior to the past two
releases, and none since
doesn't mean much. I plan to run a couple units under load for a
couple days, so feel
free to take a holiday from the endless upgrade cycle...

- in general I'm going to recomend a reboot after changes to wifi
interfaces for now


-- 
Dave Täht

                 reply	other threads:[~2014-04-27 19:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw6O7YwZHfixZ2LPJK5EQvCHecDo+HekQrvx2kzDpv6esg@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