Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.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.36-4 released
Date: Thu, 10 Apr 2014 12:46:45 -0400	[thread overview]
Message-ID: <CAGhGL2DT7ae_r9UEMUhq1nMbYnGw3LjjMpK0qjiy73+G1oPMsg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5xB4EzmHziuDNDH7E92yFAnfcXWgM+B+Rwyvk3odVgSQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

I'm up on 3.10.36-4 on a WNDR3800.  Installed via the gui, no problems with
performing the install.  I did not preserve settings.
                                      - Jim



On Thu, Apr 10, 2014 at 2:45 AM, Dave Taht <dave.taht@gmail.com> wrote:

> + dnsmasq 2.69 with dnssec enabled by default
> + possible workaround for wifi bug #442 in increased qlen_*
> + fix for ipv6 access to https://gw.home.lan:81
> + fresh merge with opewrt
> + update to 2048 bit cert generation
> + fix for openssl heartbleed (fix also in -3) bug
> + tested for an hour
> + change to sqm to basically always use "simplest.qos" on inbound
>
> - I'm very, very, very, very, very, very, very, very, very tired.
>
> I really hope this results in a stable cerowrt. Please beat the hell out
> of it.
>
> I'm already planning a vacation.
>
> --
> Dave Täht
>
> NSFW:
> https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 2034 bytes --]

  parent reply	other threads:[~2014-04-10 16:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10  6:45 Dave Taht
2014-04-10  6:46 ` Dave Taht
2014-04-10 17:33   ` Dave Taht
2014-04-11 18:25   ` Jim Gettys
2014-04-10 13:48 ` Valdis.Kletnieks
2014-04-10 14:06   ` Robert Bradley
2014-04-10 14:32     ` Toke Høiland-Jørgensen
2014-04-10 15:18       ` Robert Bradley
2014-04-10 15:21         ` Toke Høiland-Jørgensen
2014-04-10 17:29         ` Dave Taht
2014-04-10 17:57           ` Toke Høiland-Jørgensen
2014-04-10 19:06           ` Sebastian Moeller
2014-04-11 12:34           ` Robert Bradley
2014-04-10 16:40     ` Valdis.Kletnieks
2014-04-10 16:48       ` Toke Høiland-Jørgensen
2014-04-10 16:51         ` Valdis.Kletnieks
2014-04-10 16:54           ` Toke Høiland-Jørgensen
2014-04-10 18:02       ` Sebastian Moeller
2014-04-13  0:22         ` Jim Reisert AD1C
2014-04-13  0:30           ` Sebastian Moeller
2014-04-13  0:44             ` Jim Reisert AD1C
2014-04-10 16:46 ` Jim Gettys [this message]
2014-04-10 17:31   ` Dave Taht
2014-04-10 17:35     ` Jim Gettys
2014-04-11  9:50       ` David Personette
2014-04-11 10:43         ` Aaron Wood
2014-04-12 11:45         ` Neil Shepperd
2014-04-12 19:04           ` Dave Taht
     [not found] ` <CANp2as81TR_kCR8a_sZs045tXFGADL1W4CFtNEJiJrjutmL7cg@mail.gmail.com>
2014-04-11 16:31   ` 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=CAGhGL2DT7ae_r9UEMUhq1nMbYnGw3LjjMpK0qjiy73+G1oPMsg@mail.gmail.com \
    --to=jg@freedesktop.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