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
Subject: Re: [Cerowrt-devel] cerowrt 3.8.6-3 released
Date: Tue, 9 Apr 2013 23:38:55 -0700	[thread overview]
Message-ID: <CAA93jw6LaX1cK-NAg8uXumfLBEVS3jLWD4uieUyF+tq7fxfOGQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4OH5Kf5QQZX_dN+WWh8Y-HvBtX4W+6AMmhiBv7Vw2Orw@mail.gmail.com>

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

get it at:

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.8.6-3/


On Tue, Apr 9, 2013 at 11:37 PM, Dave Taht <dave.taht@gmail.com> wrote:

> This has a merge from openwrt from over the weekend (fixes to qos-scripts,
> some ipv6 gui support, I forget what else)
>
> also the requested mtr package is built and available via opkg.
> the openvpn gui didn't build.
>
> This is 100% totally untested. I'm getting on a train in a few minutes.
> The usual warnings about the possibility of the universe collapsing to a
> high infrared emitting point source apply even more than usual.
>
> What I'm mostly thinking is this month meet a few backlogged feature
> requests like the upnp issue, update the doc to match reality and call it
> another stable release.
>
> then... finish figuring out a new board to work on (the buffalo wzr and
> zedboard head the list), and get working on the new stuff in linux 3.10,
> and so on, over the spring.
>
> but who knows, perhaps the upcoming battlemesh will prove productive for
> the backlog of new needed stuff, particularly on wifi.
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html




-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

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

  reply	other threads:[~2013-04-10  6:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  6:37 Dave Taht
2013-04-10  6:38 ` Dave Taht [this message]
2013-04-11  2:32 ` Rich Brown

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=CAA93jw6LaX1cK-NAg8uXumfLBEVS3jLWD4uieUyF+tq7fxfOGQ@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