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: [Cerowrt-devel] cerowrt-3.7.4-3 released
Date: Sun, 27 Jan 2013 04:09:20 -0800	[thread overview]
Message-ID: <CAA93jw5CHasJkoVbvsjkZBG3PEP6zSVr4os+cr4AgwVQRT3u8A@mail.gmail.com> (raw)

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

thx  for the hard work of everybody here on straightening out the ipv6
configuration issues!

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

+ ipv6 traps dead, dead, dead
+ dnsmasq-2.66test12 with dhcpv6 (I hope!) by default
+ config for such
+ ntpclient/and luci app for such removed
+ ntp server enabled by default
+ nut (ups daemon) support added as a module (support for usbhid for
cyberpower upses, which I just got 3 of)

I *haven't tested this* however the delta from 3.7.4-2 is small (and it's
4AM, so the way things are going y'all will have found and fixed 2 more
bugs before I wake up).

Next up here from an ipv6 perspective is dhcpv6-pd, trying to come up with
something that will work again for ahcp, and hopefully cisco's "pie"
algorithm and a revised version of "cake"... at which point I'd like to
think "beta", and regardless, start updating the web site to point to
"modena" rather than "sugarland" as the release, updating the
documentation, etc, etc.

If anyone has any "must haves" before calling this release "feature
complete", and ready for beta, speak up now!

One thing waiting in the wings is a vmware vm of a complete ubuntu based
cerowrt build system. It is kind of my hope to lower the barriers to entry
to distribute that. I have that ready to go, I just don't have the
bandwidth available right now to upload a 2GB file.....

PS

There's also up a version for the picostation 2mHP and nanostation 5M
radios. This is a highly specialized build requiring babel and p2p links,
it goes up on on a /32 only by default, has my public key in it, and a few
other things. I'm at the yurtlab for a week and hope to test stuff at scale.

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/nano-m/3.7.4-3/

back to bed.

-- 
Dave Täht

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

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

             reply	other threads:[~2013-01-27 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27 12:09 Dave Taht [this message]
2013-01-27 22:12 ` Maciej Soltysiak

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=CAA93jw5CHasJkoVbvsjkZBG3PEP6zSVr4os+cr4AgwVQRT3u8A@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