From: Aristar <LeetMiniWheat@gmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] A stable cerowrt release in sight
Date: Sat, 17 May 2014 21:15:15 -0400 [thread overview]
Message-ID: <CAGHZhqHDVgy5kUHAMPyZ08LHTuooGfMwFuN5rZUR51BmLv5tcQ@mail.gmail.com> (raw)
In-Reply-To: <18393.1400309683@turing-police.cc.vt.edu>
I also have one thing to add, the "associated stations" hasn't been
working properly in LUCI, it only shows the master station instead of
the clients connected like it used to in 3.7.5, not sure who's to
blame here. Can others confirm this? Not a huge deal, but thought I
might throw this out there anyways.
On Sat, May 17, 2014 at 2:54 AM, <Valdis.Kletnieks@vt.edu> wrote:
> On Thu, 15 May 2014 23:36:11 -0700, Dave Taht said:
>
>> So hopefully the upcoming 3.10.40-4 build will be stable enough to
>> freeze on. If there is anything else that people want done before
>> freezing, let me know soonest.
>
> Upgraded just fine for me, been running for several hours on a wndr3800 without
> any big problems.
>
> Minor nit 1: It doesn't seem to save the 'Start UPNP now' setting, so that's
> something I need to re-set each time I upgrade. Seems to have been this way
> for a long time, 3.10.32-9 did it to me too. My PS3 says UPNP works once
> I start it.
>
> Minor nit 2: It grants IPv4 leases for 24 hours, but IPv6 for only 1 hour.
> That's OK - except my laptop running Fedora seems to think the lease is for 24
> hours, not 1, so the lease ends up expiring. Haven't chased this to see who's
> to blame. It's not a show stopper for me, because my laptop's
> SLAAC-autoconfigured address and RFC3041 privacy addresses keep working anyhow.
> It's probably been as long as the other one,
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
next prev parent reply other threads:[~2014-05-18 1:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 6:36 Dave Taht
2014-05-16 19:59 ` Török Edwin
2014-05-16 20:54 ` Dave Taht
2014-05-17 6:54 ` Valdis.Kletnieks
2014-05-18 1:15 ` Aristar [this message]
2014-05-18 13:48 ` Valdis.Kletnieks
2014-05-18 15:29 ` Dave Taht
2014-05-19 7:30 ` Maciej Soltysiak
2014-05-19 9:57 ` Sebastian Moeller
2014-05-19 16:29 ` Dave Taht
2014-05-19 17:49 ` Sebastian Moeller
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=CAGHZhqHDVgy5kUHAMPyZ08LHTuooGfMwFuN5rZUR51BmLv5tcQ@mail.gmail.com \
--to=leetminiwheat@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--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