From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 4604621F1DB for ; Mon, 24 Feb 2014 04:54:38 -0800 (PST) Received: by mail-we0-f172.google.com with SMTP id u56so4701100wes.31 for ; Mon, 24 Feb 2014 04:54:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=Ve28kaeazhX6b+lIUD46xeEz0f2JnQjmZ3BnAJN5kl0=; b=IywUQydGkDbHqdoZRoaV5aPW4UDUACgzjHBNjrToFoIYH6a9Oas6w7/6disS+s78R4 7nVcGCrpEVLVHp7+sG7eE0h8hEvnba1uCLcpNYlGaMtwBiqyQO0/5vULqypMmW7E+xA/ JeU63gIsWB3RnpIJFb7d/doGI9NlSXtseW3PmL9vCr4S/8fzVT8QHimG/TKpRYRq8FD8 nl9uFv5jltWeMszJ8lbz5Pq9e5hVncm8Q3m5z9smCCGZu5qkmD3ST74TuJe6SCHzmpzq toFD+GOrN/f+vdzGdepQUo6vLwAH0knHieNbAO9I2ir9lsbDkH1r3YbDR2u+l5WKGbNG NbWg== X-Received: by 10.180.73.173 with SMTP id m13mr14219178wiv.52.1393246475937; Mon, 24 Feb 2014 04:54:35 -0800 (PST) Received: from ?IPv6:2001:470:6aac:1:f07c:d650:105c:e6c9? ([2001:470:6aac:1:f07c:d650:105c:e6c9]) by mx.google.com with ESMTPSA id q15sm41909865wjw.18.2014.02.24.04.54.34 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Feb 2014 04:54:35 -0800 (PST) Message-ID: <530B4109.2060202@gmail.com> Date: Mon, 24 Feb 2014 12:54:33 +0000 From: Robert Bradley User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: cerowrt-devel@lists.bufferbloat.net References: <20140223172140.GB24483@lists.bufferbloat.net> <530A4791.8080903@ashtonfam.org> <128185AE-918F-4944-BB45-B5D20A1AD1E5@gmx.de> <530B1C8C.90100@imap.cc> <530B2703.3000505@imap.cc> <530B3F03.4010208@imap.cc> In-Reply-To: <530B3F03.4010208@imap.cc> X-Enigmail-Version: 1.6 Content-Type: multipart/alternative; boundary="------------050303050907010703090807" Subject: Re: [Cerowrt-devel] saner defaults for config/firewall X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Feb 2014 12:54:38 -0000 This is a multi-part message in MIME format. --------------050303050907010703090807 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 24/02/2014 12:45, Fred Stratton wrote: > There are no button presses to bring the box back, as you can with > some TP-Link routers. > > You could use a serial lead if you opened the case. No one has > mentioned trying this with cero on the list. > In my experience, reflashing via TFTP tends to work well in terms of resetting the configuration. As an aside, I've noticed that occasionally I get an "enable_vlan4k" sneaking into /etc/config/network if I've looked at the vlan page. If that happens, the wired LAN breaks. Perhaps it's worth checking that first via the wireless link? -- Robert Bradley --------------050303050907010703090807 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 24/02/2014 12:45, Fred Stratton wrote:
There are no button presses to bring the box back, as you can with some TP-Link routers.

You could use a serial lead if you opened the case. No one has mentioned trying this with cero on the list.


In my experience, reflashing via TFTP tends to work well in terms of resetting the configuration.

As an aside, I've noticed that occasionally I get an "enable_vlan4k" sneaking into /etc/config/network if I've looked at the vlan page.  If that happens, the wired LAN breaks.  Perhaps it's worth checking that first via the wireless link?
-- 
Robert Bradley
--------------050303050907010703090807--