Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Personette <dperson@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] CeroWrt 3.10.18-1 Field Report
Date: Thu, 14 Nov 2013 21:27:06 -0500	[thread overview]
Message-ID: <CAMybZqwEVbt+u-3exOn6Jn4YpJxcdB2RXJQZsHtcOx+2vfhTgw@mail.gmail.com> (raw)
In-Reply-To: <4D3A08F2-7A93-4D25-B5B7-45F9578592AB@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]

Also, while I haven't tested this. After reboots I got an IP a good bit
faster than previous builds (IE without the long timeout in fixdaemons),
it's possible that the dnsmasq (at least) startup issue is fixed in
3.10.18...

-- 
David P.


On Thu, Nov 14, 2013 at 8:56 PM, Richard E. Brown
<richb.hanover@gmail.com>wrote:

> Update on my field report:
>
> I reflashed from 3.7.5-2 to 3.10.18-1 using sysupgrade via the web GUI. I
> did *not* keep settings.
>
> After letting the router restart and setting up assorted parameters, it
> seems completely fine. It feels snappier than 3.7.5-2, but I have no
> objective measurements of this. I did watch ping times during a heavy-ish
> download, and they hardly changed.
>
> PPPoE comes up as desired on boot (in my earlier experiment with the
> 3.7.5-2 settings kept around, it didn’t)
>
> mDNS works as desired across interfaces/subnets of this router.
>
> I’m feeling pretty cocky, so I installed 3.10.18-1 as my primary router.
> But as my father used to remind me, "Pride cometh before a fall.” So I’m
> keeping the 3.7.5-2 binary handy.
>
> Good work, everyone!
>
> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 1915 bytes --]

      reply	other threads:[~2013-11-15  2:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12  5:47 Richard E. Brown
2013-11-12  9:11 ` Sebastian Moeller
     [not found]   ` <51BF9432-6FC2-4A14-B147-13F1E779CA93@gmail.com>
2013-11-12 17:26     ` Richard E. Brown
2013-11-12 21:17       ` Sebastian Moeller
2013-11-12 23:06         ` Sebastian Moeller
2013-11-12 23:11           ` Sebastian Moeller
2013-11-15 12:35             ` Sebastian Moeller
2013-11-13  4:21   ` Richard E. Brown
2013-11-13 13:56     ` Sebastian Moeller
2013-11-13 15:53       ` Richard E. Brown
2013-11-12  9:40 ` Fred Stratton
2013-11-12 17:24   ` Richard E. Brown
2013-11-15  1:56 ` Richard E. Brown
2013-11-15  2:27   ` David Personette [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=CAMybZqwEVbt+u-3exOn6Jn4YpJxcdB2RXJQZsHtcOx+2vfhTgw@mail.gmail.com \
    --to=dperson@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