From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] openwrt build for ar71xx (wndr3800, archer, picostation, etc)
Date: Wed, 17 Jun 2015 15:23:52 -0700 [thread overview]
Message-ID: <CAA93jw6Af42H0AXo4Uk45UrRkSisoGwVL1KHuSZL5skCXpyB1Q@mail.gmail.com> (raw)
get at:
http://snapon.lab.bufferbloat.net/~cero3/lupin/ar71xx/
Not doing versioning...
my mission is to come up with something *stable* I can deploy across
several routers more than fiddle with new stuff. Not having snmp is an
issue...
+ openwrt head
+ built with libmusl for the first time (bunch of tools missing now)
+ this includes the latest changes for sqm-scripts and gui (no direct
support for cake in the gui), from sebastian from this morning
+ minstrel-blues and andrew mcgregors "minimum variance" patches
+ the latest cake from last night
+ babeld-1.6.1 (with ecn on by default)
+ dnsmasq-2.73
tested for all of a half hour. NOT tested as a default gw in particular.
Notes:
- a really critical thing broke in the musl build - I use snmp a lot.
Can't deploy without it. Will try to fix.
- I missed setting the dnssec-timestamp option on by default in
/etc/config/dhcp correctly in the init file. Not sure what "correct"
is. (?)
- cake showed some issues in long rtt testing:
http://snapon.lab.bufferbloat.net/~d/latestcake/
(but I am still having cable modem weirdnesses - am moving to an
emulated longer rtt environment shortly... after I flash a couple more
routers)
- and thus far I have been unable to build anything (uclibc or musl)
for the linksys ac1900.
- babel in openwrt head defaults to logging to flash by default which
I think is a really bad idea for general use... but useful right
now...
- I would have thought that with
config globals 'globals'
option ula_prefix 'fd59:c767:7910::/48'
That the system would have announced a /48 route for that. I am not
particularly fond of random ula's showing up everywhere, so I tend to
comment ula_prefix out. It is locally "unreachable" which is correct,
but babel only exports p2p routes by default... /me puzzles over
syntax
- too scared to try hnetd again. Anyone fiddling with it? (I need a
bunch of interior routers to "just work" at the moment)
- it defaults to a bridged vlan now. I am unfond of that, but I left
the vlan on to see if it would break anything...
+ without nat, forwards through pie, cake, fq_codel at 110mbit.
--
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next reply other threads:[~2015-06-17 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 22:23 Dave Taht [this message]
2015-06-18 2:24 ` Rich Brown
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=CAA93jw6Af42H0AXo4Uk45UrRkSisoGwVL1KHuSZL5skCXpyB1Q@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