Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Richard Brown <richard.e.brown@dartware.com>
To: "<cerowrt-devel@lists.bufferbloat.net>"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] preliminary codel and fq_codel support for cerowrt
Date: Tue, 15 May 2012 21:11:04 +0000	[thread overview]
Message-ID: <0B965654-57C1-4EA7-902D-D3B63F0FAC62@intermapper.com> (raw)
In-Reply-To: <mailman.4.1337108402.20843.cerowrt-devel@lists.bufferbloat.net>

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


On May 15, 2012, at 3:00 PM, Outback Dingo wrote:

Caveat:

This release suffers from an unrelated bug ( #379 ) and should NOT be
installed as your main router. I would love to beat this bug because
it's the only prio 1 remaining but thus far, no luck. Under lighter
loads CeroWrt appears to work just fine, but that's for me. YMMV.

Get it here: http://huchra.bufferbloat.net/~cero1/3.3/3.3.6-2/


Odd why is there no openwrt-ar71xx-generic-wndr3700-squashfs-factory.img ??
has it been combined with another ???

CeroWrt has no builds for the either the WNDR3700 v1 or v3. The WNDR3700v2 and WNDR3800 both work fine (and the WNDR3800 has more flash memory, so it's a bit more futureproof...)

Best,

Rich

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

       reply	other threads:[~2012-05-15 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4.1337108402.20843.cerowrt-devel@lists.bufferbloat.net>
2012-05-15 21:11 ` Richard Brown [this message]
2012-05-14 20:59 Dave Taht
2012-05-14 21:58 ` Outback Dingo
2012-05-16 16:34 ` Sebastian Moeller
2012-05-16 17:09   ` dave taht
2012-05-16 17:16     ` Outback Dingo
2012-05-16 17:52       ` Dave Taht
2012-05-16 19:51         ` Sebastian Moeller
2012-05-17  0:09           ` dpreed

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=0B965654-57C1-4EA7-902D-D3B63F0FAC62@intermapper.com \
    --to=richard.e.brown@dartware.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