From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] very development build: cerowrt-3.10.41-2 with some homenet support
Date: Fri, 6 Jun 2014 08:07:15 -0700 [thread overview]
Message-ID: <CAA93jw7rHzT=1MiGHi+SkJ7GwLFN6AZsvmAnUq1cD4yym46muw@mail.gmail.com> (raw)
- totally untested, absolutely do not install on your main gateway!
the intent with this build is to start getting an interior router to
work better,
and multiple bits of code are underconfigured or outright busted
and/or a step backwards.
+ resync with openwrt
Among other things, this contains ani fixes for wireless that might be
relevant for bug 442. As fatal as having that bug has been to doing a
final, stable release, it has thus far been resistant to analysis.
+ miniupnpd w/ipv6 pcp support
note that I'm unsure if I got the conf file right
+- avahi deprecated
(losing our last dependency on dbus, which is also ripped out)
The end binary firmware still got a bit bigger for some reason
+ mdsnd substituted -
+ ohybridproxy installed by default
+ hnetd NOT installed by default but built as an optional package
It messes with dhcp serving in particular.
odhcp, mdnsd, hybridproxy, hnetd, and dnsmasq all have to play together
and they don't right now.
+ AHCP left in (for now)
Get it at:
http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/dev/3.10.41-2/
I've had a bit of discussion with the members of homewrt about how to
integrate this stuff in cero, but it looks like a bit of hacking on the
scripts and default conf is necessary to get all the pieces to fit
together. If there are those
out there that would like to participate in getting the pieces to fit,
the best place to pitch in and help is on the #hnet-hackers channel on irc.
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
reply other threads:[~2014-06-06 15:07 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='CAA93jw7rHzT=1MiGHi+SkJ7GwLFN6AZsvmAnUq1cD4yym46muw@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