Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Vincent Frentzel <zcecc22@c3r.es>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] saner defaults for config/firewall
Date: Mon, 24 Feb 2014 10:29:36 +0100	[thread overview]
Message-ID: <128185AE-918F-4944-BB45-B5D20A1AD1E5@gmx.de> (raw)
In-Reply-To: <CACCCjEXibgeepGo67ZSfx21NwRik8C+5x4Z5J7kroSGY1oPETA@mail.gmail.com>

Hi Vincent,


On Feb 24, 2014, at 09:07 , Vincent Frentzel <zcecc22@c3r.es> wrote:

> 
>> 1) a more "normal", bridged implementation more like people are used to.
> 
> 
> Regarding this scenario. I tried to revert cerowrt to a bridged setup and ended up with a completely broken system. 
> 
> I bridged the interface as follow, eth0.1 + sw10 + sw00. Connecting over wifi worked fine except that cabled host could not be pinged. Connecting over ethernet did nt work at all (no DHCP received, cannot ping router with manually assigned IP).

	I could be totally out for lunch here, but shouldn't that be se00 (secure ethernet) instead of eth0.1? At least on 3.10.28-14 neuter "ifconfig" nor /etc/config/network mentions eth0.1 at all. Could you post both of these (so the result of calling ifconfig on a terminal on the router and the content of /etc/config/network ;), I am sure you know what I meant, just dying to be verbose for the sake of people stumbling over the archive of the mailing list)


> 
> Was something related to bridges removed in cerowrt?
> 
> The config I used works fine on Barrier Breaker.
> 

best regards
	Sebastian


> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2014-02-24  9:29 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 [this message]
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
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=128185AE-918F-4944-BB45-B5D20A1AD1E5@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=zcecc22@c3r.es \
    /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