Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Richard Brown <richard.e.brown@dartware.com>
Cc: "<cerowrt-devel@lists.bufferbloat.net>"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] CeroWrt 3.3.1-4
Date: Fri, 6 Apr 2012 19:48:05 -0700	[thread overview]
Message-ID: <CAA93jw5AWLZ+Em2i9SPEMPQCoatAZyD3p63GUbCTEa6vbnX+=g@mail.gmail.com> (raw)
In-Reply-To: <EAA9DD1E-DEEA-4D9D-AE33-639D44E5257E@intermapper.com>

On Fri, Apr 6, 2012 at 7:28 PM, Richard Brown
<richard.e.brown@dartware.com> wrote:
> Dave,
>
> Congratulations on taming the wifi,

hat off to the guys at openwrt for 99.% of that....

> adding CUBIC, and otherwise getting CeroWrt building and working again. Sorry you're still suffering with #113. Questions:

>
> 1) Is 3.3.1-4 worth posting for testing? I installed it and it seems to be operating fine. (DNS names *were* dead for a while after reboot. It seemed like only a couple minutes before the router began supplying them.)

Your tolerance for "first boot" time pain is higher than mine.

> 2) If 3.3.1-4 is good enough for testing, we should update the release notes. Let me know what has changed, and I'll update the page. http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_33_Release_Notes

I'm sitting here watching a video feed that Steinar Gunderson, just
gave me of the 'gathering'

http://www.gathering.org/tg12/en/

over ipv6. from norway. at 720p. over udp. through cerowrt. through
sfqred. to my laptop.

and it looks and sounds pretty darn good. Too bad I don't speak the language.

cero's otherwise been through the wrigner for 3 days, it's worth
letting out for more testing, so yes...

as for what changed... I guess I'll write it but not tonight.

> I'm corresponding with Travis at OpenWrt to see what is necessary to devote the spares cycles on my quad-core box at home to the OpenWrt buildbot system. I'll let you know when there's something to report.

I think that being able to distribute a linux vm that 'just works' to
build openwrt and/or cerowrt would be a goodness. It would help out
mac and pc guys a lot. (this is mildly different than having a vm
that's a buildslave... but doing both in one vm seems feasible and
desirable)

I'm trying to scrounge up more hardware. I could easily light up 40
boxes and over a hundred cpus on this task, even if the problem was
under control. I think I maybe able to scrounge a few boxes but the
electricity and rack space needed to run them...

>
> Best,
>
> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

      reply	other threads:[~2012-04-07  2:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.127.1333680653.1801.cerowrt-devel@lists.bufferbloat.net>
2012-04-07  2:28 ` Richard Brown
2012-04-07  2:48   ` Dave Taht [this message]

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='CAA93jw5AWLZ+Em2i9SPEMPQCoatAZyD3p63GUbCTEa6vbnX+=g@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richard.e.brown@dartware.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