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: Re: [Cerowrt-devel] cerowrt-3.10.48-2 released
Date: Thu, 17 Jul 2014 15:36:06 -0700	[thread overview]
Message-ID: <CAA93jw710xiaSSSEao3rZ-7+dybs0tE+8Vb5zAPbW6C++x-7uQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4hXVM0Fbnme64rg9YZx6Ame5JQmzMimoj6A4Hz49021g@mail.gmail.com>

I forgot:

+ ntp startup re-integrated with dnsmasq dnssec support. (thx toke!)
if it wasn't for bug 442, and the integration of hnetd mdns proxy, I'd
love to just say, we're done...

On Thu, Jul 17, 2014 at 3:18 PM, Dave Taht <dave.taht@gmail.com> wrote:
> Get it at: http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.48-2/
>
> + resync with openwrt head
>    (it's not clear how to deal with the barrier breaker freeze yet)
> + hopefully a fix for bug #442
>  - but only extensive testing will tell
>  - we have some rumored negative data so don't get your hopes up
> + sqm improvements
>    inbound diffserv squashing works now as does not squashing - you can actually
>    see inbound shaping working semi-properly now if you choose to trust
>    your inbound connection's classification.
>    gui support for above
> + babel improvements
>    latest source specific code from the main openwrt-routing repo
>    simplification of the default route export mechanism
>    diversity routing enabled by default
>    link detection enabled by default
>    (if you aren't using babel, just disable it)
>
> - wire-incompatible change to babels
>   if you are using babels on another router you don't want to upgrade,
> you will need to uninstall the babeld package and install the current
> babels package from this release. Carefully, as you need to copy over
> the new config files (/etc/firewall.user /etc/babeld.conf
> /etc/config/babeld) from this release also.
>
> - I am focused on getting ready for ietf, and thus unable to give ipv6
> a shakeout without risking my vpn failing while I'm away. I was hoping
> to get some time tomorrow to deploy on ipv6. It's looking less likely
> by the minute, I'd rather have an extensive test up and running
> continuously before I leave of what I got.
>
> - I won't have time for another release for 2 weeks. If it breaks in
> some new, crazy way, please revert to a prior version.
>
> --
> Dave Täht
>
> NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article



-- 
Dave Täht

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

  reply	other threads:[~2014-07-17 22:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 22:18 Dave Taht
2014-07-17 22:36 ` Dave Taht [this message]
2014-07-18 14:23 ` Valdis.Kletnieks
2014-07-18 14:31   ` Dave Taht
2014-07-18 14:43     ` Dave Taht
2014-07-18 20:04     ` Dave Taht
2014-07-23 15:44       ` Jim Reisert AD1C
2014-07-25 18:04 Jim Reisert AD1C
2014-07-25 18:08 ` Jim Reisert AD1C

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=CAA93jw710xiaSSSEao3rZ-7+dybs0tE+8Vb5zAPbW6C++x-7uQ@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