From: Dave Taht <dave.taht@gmail.com>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Cerowrt 3.3.8-10 is released
Date: Thu, 12 Jul 2012 17:51:24 -0400 [thread overview]
Message-ID: <CAA93jw71TA9uy=3nF7n7oFR97hjWX-TbaU3KC8KQUfdyk2g8RQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7y95yyUnjRu19G7N2yvepj860E-JmHCGcpuvz3ir0B2w@mail.gmail.com>
I enabled crypto not via on the 2.4ghz interface on the -11 release
and it worked.
I DID have to do a clean reboot tho.
5.x is showing a new problem.
On Thu, Jul 12, 2012 at 4:55 PM, Dave Taht <dave.taht@gmail.com> wrote:
> Might have been the bug felix fixed in -11
>
> Might also have corrupted the /etc/config/wireless and/or
> /etc/config/network file too. if you ended up with a wlan0-1 in there
> that would be it...
>
> I too rarely use the gui interface.
>
> On Thu, Jul 12, 2012 at 4:45 PM, Maciej Soltysiak <maciej@soltysiak.com> wrote:
>> Hi,
>>
>> Just flashed WNDR3800 with 3.3.8-10 and I get a weird problem.
>> After flashing it works fine, until I change radio0 and 1 wifi settings: set
>> WPA2, set channel, etc.
>> After save&apply, on a cilent PC I am able to see the networks on the list
>> but it's not possible to connect.
>> I believe the client associates with the AP, but it has an APIPA address.
>> Happens to normal and guest interfaces too, even if I don't touch guest
>> interfaces.
>>
>> I logged in over the wire to see if dhcpd was running and it was, but since
>> I can't find logs in the usual place I will now fallback to different
>> firmware.
>>
>> Could that be a known issue?
>>
>> Regards,
>> Maciej
>>
>> On Wed, Jul 11, 2012 at 6:56 PM, Maciej Soltysiak <maciej@soltysiak.com>
>> wrote:
>>>
>>> Hi Dave,
>>>
>>> Thanks for a good, lengthy update. I wish you pleasant time travelling.
>>>
>>> One question on ECN though.
>>>
>>>
>>> On Tue, Jul 10, 2012 at 3:43 AM, Dave Taht <dave.taht@gmail.com> wrote:
>>>>
>>>> - ECN dropping - after several high level conversations with many
>>>> people smarter than me, I decided that dropping ECN packets at a
>>>> certain point made sense. So did everyone else. The "certain point"
>>>> remains puzzling to all, and
>>>> rather than continue to waste time on it in cero I decided to play
>>>> with models instead, and frankly, hope that someone else comes up with
>>>> some sane way to combine ECN and codel sojourn time.
>>>
>>> So if we're dropping ECN packets and not of trying to allow them through
>>> to communicate congestion am I better of enabling ECN on clients on my
>>> network or not?
>>>
>>> Regards,
>>> Maciej
>>
>>
>
>
>
> --
> 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!"
next prev parent reply other threads:[~2012-07-12 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 1:43 Dave Taht
2012-07-10 21:38 ` [Cerowrt-devel] [Bloat] " Jim Reisert AD1C
2012-07-11 16:56 ` [Cerowrt-devel] " Maciej Soltysiak
2012-07-12 20:45 ` Maciej Soltysiak
2012-07-12 20:55 ` Dave Taht
2012-07-12 21:51 ` Dave Taht [this message]
2012-07-13 0:43 ` 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='CAA93jw71TA9uy=3nF7n7oFR97hjWX-TbaU3KC8KQUfdyk2g8RQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=maciej@soltysiak.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