From: Vincent Frentzel <zcecc22@c3r.es>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] saner defaults for config/firewall
Date: Mon, 24 Feb 2014 11:05:07 +0100 [thread overview]
Message-ID: <CACCCjEVE+Un+M2vKm=SaHw-7-mPqVCByxZToQX-Xmz43j2YUYg@mail.gmail.com> (raw)
In-Reply-To: <128185AE-918F-4944-BB45-B5D20A1AD1E5@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]
> 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)
>
Hi Sebastian,
Understood. I will come back to you with the ifconfig.
For info, I did try both se00 and eth0.1. The reason I stuck with eth0.1
was that barrier breaker usually uses eth0.1 for br-lan with vlan enabled
(eth0.1 appears in Luci in cerowrt). So in cero I just reenabled the vlan
and used a type "bridge" on the network section (I renamed this section
se99 instead of se00).
I then added se99 it to the "lan" zone of the firewall. In the wireless
config I specified network as "se99" instead of sw10 and sw00. I confirmed
that the setup was correct in the web interface where eth0.1 sw00 and sw10
appeared under the new bridged interface ( there was the nice icon with the
iface in brackets).
I went on to modify the dhcp config of se00 and changed se00 occurences for
se99 and commented out entries for sw10/sw00. --> this would give me dhcp
running on my new bridge.
After a dnsmasq restart dnsmasq.conf shows the dhcp ranges line with
interface se99. (I was expecting to see br-se99 but maybe that file is
alias aware, could be wrong here).
After a network restart I lost connectivity on cable. Wireless was working.
I played a tad more and eventually lost wifi as well and had to reflash the
router via tftp/factory image (maybe there is a reset trick you could give
me to avoid this step).
Are you running cerowrt in bridge mode? If yes could you share your
network/firewall/dhcp config? Is there another file I should have edited
and missed?
Cheers,
V
[-- Attachment #2: Type: text/html, Size: 2411 bytes --]
next prev parent reply other threads:[~2014-02-24 10: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 [this message]
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='CACCCjEVE+Un+M2vKm=SaHw-7-mPqVCByxZToQX-Xmz43j2YUYg@mail.gmail.com' \
--to=zcecc22@c3r.es \
--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