From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Cerowrt-3.3.8-11 development only version released
Date: Thu, 12 Jul 2012 17:24:26 -0400 [thread overview]
Message-ID: <CAA93jw676-JD8RrS2rzfYDRESsqFpXgZ63P5hiu+aOiY_XGBmA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7vN5xGv-FveRnQRsu9QB1QkdvpjZKdLhNcgjHvkNRzaA@mail.gmail.com>
Grumble. No, the configuration gui in 3.3.8-11 is fine, I got bit by
the default firewall rules not allowing meshed access to the gui.
However -11 doesn't bring up the AP at all on the 5ghz radio, so steer
clear until
these outstanding bugs are resolved.
On Thu, Jul 12, 2012 at 5:05 PM, Dave Taht <dave.taht@gmail.com> wrote:
> The gui in this release appears to be borked entirely. Don't use unless you
> want in on bugs 401 and 402.
>
> This is what I get for rushing a fix. Going back to packing now.
>
> On Thu, Jul 12, 2012 at 4:54 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> Due to the severity of bug #401, I felt it was best to get this out before
>> I got on a plane tomorrow.
>>
>> You can do an update in place from -10 except for the one liner fix in bug 399.
>>
>> Out of the cerowrt bug database:
>>
>> Bug #399 - Problem starting avahi-daemon - Fixed (but if you do an
>> upgrade in place it won't be - see the bug for the fix. Thx)
>> Bug #401 - major retries in the VI AMPDU queue on ath9k - In the
>> process of being fixed, hopefully
>> Bug #402 - Tail drop behavior on fq_codel/debloat on ack-mostly
>> streams - defaults doubled
>>
>> 401 and 402 are interrelated (probably), but are going to require some
>> fiddling to debug (need a serial port and crash logging or
>> to twiddle various variables like qlen_vi, or to lower codel's memory
>> limits again - and shouldn't happen in the general case for most
>> uses/users but see #401 and #402 for details. I am not in a position
>> to do serial debugging for a while)
>>
>> Quagga - update to support the "babelz" diversity routing option
>>
>> Openwrt bug #11847 (https://dev.openwrt.org/ticket/11847 )
>> mac80211: fix an ap + sta mode regression that prevented the sta from connecting
>>
>> I need to note that in a meshed setup with more than router, avahi
>> should only be on on one at most.
>>
>> For those that track bugs, the cerowrt buglist keeps growing and
>> growing. Some of these are basically closed but need review and
>> testing. The bugs noted in the previous release note for 3.3.8-10 are
>> in there...
>>
>> http://www.bufferbloat.net/projects/cerowrt/issues
>>
>>
>> --
>> Dave Täht
>> http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-10 is out
>> with fq_codel!"
>
>
>
> --
> Dave Täht
> http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-6 is out
> with fq_codel!"
--
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-6 is out
with fq_codel!"
prev parent reply other threads:[~2012-07-12 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 20:54 Dave Taht
2012-07-12 21:05 ` Dave Taht
2012-07-12 21:24 ` Dave Taht [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=CAA93jw676-JD8RrS2rzfYDRESsqFpXgZ63P5hiu+aOiY_XGBmA@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