From: Rich Brown <richb.hanover@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt 3.8.6-3 released
Date: Wed, 10 Apr 2013 22:32:00 -0400 [thread overview]
Message-ID: <81719D44-55DC-476F-ADF2-CF955B53D9DC@gmail.com> (raw)
In-Reply-To: <CAA93jw4OH5Kf5QQZX_dN+WWh8Y-HvBtX4W+6AMmhiBv7Vw2Orw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]
A quick test of 3.8.6-3 on my WNDR3800 looked good. I was able to execute my scripts for setting up the config the way I like and for obtaining a 6in4 address through Hurricane Electric (see the wiki for the scripts).
There was a peculiar behavior with wireless immediately after configuring the IPv6 script. It was hit or miss whether I could get connected to wireless. for for a few minutes after running the config scripts. This seems to have resolved and it is working.
I have not yet made the adjustments to simple_qos.sh as suggested in the wiki, but my performance using iperf seemed just fine.
Rich
On Apr 10, 2013, at 2:37 AM, Dave Taht <dave.taht@gmail.com> wrote:
> This has a merge from openwrt from over the weekend (fixes to qos-scripts, some ipv6 gui support, I forget what else)
>
> also the requested mtr package is built and available via opkg.
> the openvpn gui didn't build.
>
> This is 100% totally untested. I'm getting on a train in a few minutes.
> The usual warnings about the possibility of the universe collapsing to a high infrared emitting point source apply even more than usual.
>
> What I'm mostly thinking is this month meet a few backlogged feature requests like the upnp issue, update the doc to match reality and call it another stable release.
>
> then... finish figuring out a new board to work on (the buffalo wzr and zedboard head the list), and get working on the new stuff in linux 3.10, and so on, over the spring.
>
> but who knows, perhaps the upcoming battlemesh will prove productive for the backlog of new needed stuff, particularly on wifi.
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 2499 bytes --]
prev parent reply other threads:[~2013-04-11 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 6:37 Dave Taht
2013-04-10 6:38 ` Dave Taht
2013-04-11 2:32 ` Rich Brown [this message]
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=81719D44-55DC-476F-ADF2-CF955B53D9DC@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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