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] 3.3rc6-3 is out
Date: Thu, 8 Mar 2012 15:43:53 -0800	[thread overview]
Message-ID: <CAA93jw4kRHHQv_zNA7D6GMji4Xa2agJSjJ9-1HnwsCZYdTSxoQ@mail.gmail.com> (raw)

http://huchra.bufferbloat.net/~cero1/3.3/3.3-rc6-3/

This release contains updates to the latest versions of strongswan and openvpn.
It also contains 'git head' versions of iptables, iproute2, and dnsmasq.

It should also be independently buildable now, although the automated
build script needs a bit more work.

It works (I'm typing this at you now via a meshed connection, actually).

I hope at this point that these are the 'final' new packages for the upcoming
cerowrt-3.3 release. I will track git head closely on these and update to
the final, released versions as time goes along.

Of the newish packages, dnsmasq is very interesting as it has support for ra
announcements, dhcpv6, lua based scripting, and dnssec proxying, not
that all of that is compiled in at the moment.

I do hope to find a final answer for the interaction of dhcpv6-pd and
distributing ipv6 addresses with a sane dns naming scheme at some
point, as well as resolving the persistent ntp + dnssec bug.
dibbler-client has some problems that I've as yet been unable to
resolve.

I do not have time set aside at present for fiddling with openvpn and
strongswan either, but as I'm dealing with an encapsulation bug elsewhere
I'll probably have to get a vpn setup again sometime soon. The updates
to these two tools were trivial and after a little testing should end up right
in openwrt. In the meantime, vpn junkies, please run amuck.

I still have a large number of updated packages that are broken -

upnp*
ccnx
lisp
lig
dhcp-latest

but none are mission critical.

Next up is glue, fit, and finish issues, improving the guis, making the
aqm code 'just work', etc. Also I will be disabling (commenting out)
the automatic 6to4 support presently in there, and reviewing the
firewall rules.

I have another project that will be tying into this starting up, too,
which basically involves 'PCP' support, to what extent that will
end up in cerowrt or in a separate build, I don't know.

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

                 reply	other threads:[~2012-03-08 23:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw4kRHHQv_zNA7D6GMji4Xa2agJSjJ9-1HnwsCZYdTSxoQ@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