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] Cerowrt-devel Digest, Vol 1, Issue 15
Date: Sat, 31 Dec 2011 06:11:19 -0800	[thread overview]
Message-ID: <E65AE69B-0AC7-434F-AEF4-987BB2C7B4F4@intermapper.com> (raw)
In-Reply-To: <mailman.0.1324756802.19843.cerowrt-devel@lists.bufferbloat.net>

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

Hi Dave,

Thanks for the clarifications on the status of cerowrt and your expectations for how people should use the current builds.

Right now, for example, the bql-9 smoketest mentioned above works
pretty good (it's missing some features like bind and ahcp at the
moment) - but my attempts at adding several new AQMs appear to be
triggering kernel bugs. RED was proven broken for three years of the
kernel prior to 3.1.5, btw...

A little feedback. I have installed two cerowrt builds:

rc6 - worked fine. I got snmpd installed, and could try the newly-built fprobe again.

bql-9 from 24 Dec. I was surprised when I couldn't connect to gw.home.lan.

What's your advice for continuing to play with cerowrt? What version should I look at? I don't have to put it "in production" - currently, its WAN port is connected to my home router's LAN port, so I can still load in experimental stuff without affecting other family members.

Happy New Year.

Rich

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

       reply	other threads:[~2011-12-31 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1324756802.19843.cerowrt-devel@lists.bufferbloat.net>
2011-12-31 14:11 ` Richard Brown [this message]
2012-01-02 22:11   ` 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=E65AE69B-0AC7-434F-AEF4-987BB2C7B4F4@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