Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Richard E. Brown" <richb.hanover@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] CeroWrt 3.10.18-1 Field Report
Date: Wed, 13 Nov 2013 10:53:33 -0500	[thread overview]
Message-ID: <1EE10E51-1878-426A-8A26-52B881DC9DBF@gmail.com> (raw)
In-Reply-To: <D5A1D94F-1153-4E20-BB95-A97AAABA6561@gmx.de>

Hi Sebastian,

Thanks for looking at this. So it seems that keeping the configuration when using sysupgrade caused the problem.

> I now begin to understand why Dave recommends against using the "keep configuration" setting for sys upgrade :) there is just too much in flux for it to work for all sub packages.
> That said it should be possible to restrict the set of kept settings to those settings that should not differ between cerowrt and openWRT (I think the PPPoE setting should qualify). But I have not looked into that yet.

Another (and better, and simpler) alternative would be for me to add the PPPoE credential-setting lines to the existing script on the Files tab of the wiki. That way, I could use sysupgrade back to the factory defaults, then use the script to get consistent settings on my router.

I’ll post when I’ve updated it. Best,

Rich

  reply	other threads:[~2013-11-13 15:53 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 [this message]
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

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=1EE10E51-1878-426A-8A26-52B881DC9DBF@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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