From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] did a chaos calmer openwrt build, untested
Date: Mon, 16 Mar 2015 09:58:09 -0700 [thread overview]
Message-ID: <CAA93jw4EbA2C0O_1wUFrA8gvvPK1+eit+=XFWpTWHG+M4J8dxw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
I folded in the following:
* minstrel-blues
* minstrel patches for minimum variance (hurts udp, helps tcp)
* babel-1.6.0 release candidate
* cake and the usual slew of alternate bufferbloat-fighting qdiscs
I intended to use this build to test my ubnt gear and the archer c7v2. It
is NOT cerowrt...
http://snapon.lab.bufferbloat.net/~cero3/ubnt/ar71xx/
1) But before I even got so far as trying that build, ran across this
ticket.
https://dev.openwrt.org/ticket/19194
2) Is the consensus here we should resume using the "device naming by
security model" mode?
3) Things I would like to be developing and then testing
* latest dnsmasq code (with fixed date getting stuff to hopefully finally
make it up to openwrt)
* latest FIB patches backported to 3.18 (or, possibly, moving to 4.0)
* babel with atomic routing updates
* cake, etc.
* bobbie (policer)
* ???
4) Generic problem:
We need some form of autodetection of whether or not IPV6_SUBTREES is
enabled in the kernel (whether in userspace or with additional kernel
support for making the query - perhaps with kernel support) -
presently that is a compile time only option in babel and I'd like it to be
the
default.
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
[-- Attachment #2: Type: text/html, Size: 1956 bytes --]
next reply other threads:[~2015-03-16 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 16:58 Dave Taht [this message]
[not found] ` <550711A0.1080706@midlink.org>
2015-03-16 17:30 ` Dave Taht
2015-03-16 18:53 ` Felix Fietkau
2015-03-16 19:19 ` Dave Taht
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='CAA93jw4EbA2C0O_1wUFrA8gvvPK1+eit+=XFWpTWHG+M4J8dxw@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