From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net,
bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: cerowrt-next plans
Date: Fri, 23 Nov 2012 18:27:00 +0100 [thread overview]
Message-ID: <CAA93jw4SJv3buSbzR9aV8uHnRQ2MNxaMRJ9YJKDyCv=xpywmGA@mail.gmail.com> (raw)
I did finally get around to booting the ubnt linux 3.6.7 build I
talked about yesterday.
Yea! It worked.
Boo! I have a ton of patches to modify to get back to equivalence with
what's in cerowort-3.3.8-27
So I'm planning on forking the "stable" cerowrt 3.3 repository for new
development on 3.6,
and am calling it cerowrt-next. I may blow it away entirely and rebase
on openwrt. Nobody
look!
In the interim perhaps I'll stick up the ubnt-3.6.7 code, but there
seems to be no demand, sooo...
Updates:
* Steven Walker made a bunch of updates to ceropackages the other day,
I haven't tested.
thx steven. If anyone wants an updated ccnx-6.2, in particular, it's there...
* Openwrt Head
* Radvd must die - in favor of either dnsmasq or quagga
Backports:
* IPv6 performance patch
* Multiple versions of fq_codel
* QFQ+
* Wireless diffserv patch
* Memory reduction patches in pfifo_fast and codel
Whatever other patches didn't make it up to openwrt
New development:
* Randomness/entropy framework infrastructure buildout
The new randomness frame in 3.6 and later requires driver support in
order to work well.
Good crypto in things like WPA, and SSL requires good entropy.
A lot of people have been thinking "ooh, random numbers fixed in
embedded linux since 3.6"
Um, no. Well, partially...
http://lwn.net/Articles/507115/
* TCP Fast Open test support
TCP fast open is supported server side in 3.6. There is some
preliminary support for it in netperf now
* AHCP in dnsmasq
After watching the deliberations on homenet, and knowing ahcp fits a
niche not addressed there,
and knowing that it solves a need that cannot be met by SLAAC, dhcp,
dhcp-pd, or ospf+pd,
and after losing many battles with ahcpd, and knowing AHCP NEEDS TWO
implementations
to go ietf standard track...
I started hacking on the core idea one weekend 18 months ago. I
figured if I just got a couple weekends
more free I'd be able to get the protocol into dnsmasq at the cost
of a couple k in binary, and save a mb of ram.
I decided that dnsmasq was the right place to stick it, given that
it managed address assignment
already for multiple other protocols. It turns out than an AHCP
server is even simpler than the
client. I then started having some thoughts towards having prefix
distribution and border discovery in it...
and felt that writing a fresh implementation would be a good start
towards understanding these
complex issues.
Sadly, those weekends have not happened yet. :(
It would be nice to find someone to work with to continue getting
this into dnsmasq. ? Even as an exercise,
it's a good exploration into how ipv6 multicast actually works....
Anyway I just folded in somepatches that compiled and opened up the
port into the current dnsmasq tree
and put it up on github. It does very little else...
My github repo for dnsmasq-ahcp: https://github.com/dtaht/dnsmasq-ahcp
Protocol Specification:
http://www.pps.univ-paris-diderot.fr/~jch/software/ahcp/draft-chroboczek-ahcp-00.html
existing ahcp server/client code and doc:
http://www.pps.univ-paris-diderot.fr/~jch/software/ahcp/
Alternatively getting another ahcp server written in another
language would be good.
* DLNA (?)
* small DHCP-PD support
Wide is not working out, isc and dibbler are too huge. It's time for
someone to write a small one... (not me!)
Other suggestions for the upcoming development cycle?
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next reply other threads:[~2012-11-23 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 17:27 Dave Taht [this message]
2012-11-23 21:26 ` [Cerowrt-devel] " dpreed
2012-11-23 22:42 ` David Lang
2012-11-23 23:27 ` dpreed
2013-01-08 5:18 ` Juliusz Chroboczek
2012-11-23 21:29 ` Outback Dingo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4SJv3buSbzR9aV8uHnRQ2MNxaMRJ9YJKDyCv=xpywmGA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--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