Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Vincent Frentzel <zcecc22@c3r.es>
To: Robert Bradley <robert.bradley1@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] saner defaults for config/firewall
Date: Mon, 24 Feb 2014 14:05:47 +0100	[thread overview]
Message-ID: <CACCCjEVL2X9ux8O6m6G=mJWBGM4cae1y1jBYkZmveJiuBSj0jA@mail.gmail.com> (raw)
In-Reply-To: <530B4109.2060202@gmail.com>

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

Thanks Robert.

I indeed had enable_vlan4k in the network. Will definitely try to remove
this. When you enable the vlan do you use the eth0.1, eth0.2, etc.. stanza
for the interface or se00? Is se00 an alias for eth0.1?


On Mon, Feb 24, 2014 at 1:54 PM, Robert Bradley
<robert.bradley1@gmail.com>wrote:

>  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
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>

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

  reply	other threads:[~2014-02-24 13:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 23:25 Vincent Frentzel
2014-02-23 17:21 ` Dave Taht
2014-02-23 19:10   ` J. Daniel Ashton
2014-02-24  8:07     ` Vincent Frentzel
2014-02-24  9:29       ` Sebastian Moeller
2014-02-24 10:05         ` Vincent Frentzel
2014-02-24 10:18           ` Fred Stratton
2014-02-24 11:03             ` Fred Stratton
2014-02-24 11:35               ` Vincent Frentzel
2014-02-24 12:45                 ` Fred Stratton
2014-02-24 12:54                   ` Robert Bradley
2014-02-24 13:05                     ` Vincent Frentzel [this message]
2014-02-24 13:48                       ` Robert Bradley
2014-02-24 13:35                 ` Sebastian Moeller
2014-02-24 13:29           ` Sebastian Moeller
2014-02-24 16:24     ` Dave Taht
2014-03-03 19:41     ` David Lang

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='CACCCjEVL2X9ux8O6m6G=mJWBGM4cae1y1jBYkZmveJiuBSj0jA@mail.gmail.com' \
    --to=zcecc22@c3r.es \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=robert.bradley1@gmail.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