From: Robert Bradley <robert.bradley1@gmail.com>
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 13:48:19 +0000 [thread overview]
Message-ID: <530B4DA3.4080507@gmail.com> (raw)
In-Reply-To: <CACCCjEVL2X9ux8O6m6G=mJWBGM4cae1y1jBYkZmveJiuBSj0jA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
On 24/02/2014 13:05, Vincent Frentzel wrote:
> 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?
>
>
I'm open to corrections, but from what I have seen here the se00
interface in Luci maps to a physical se00 interface by default. That
interface receives vlan tagged packets from the embedded switch which
then appear untagged on eth0.x. With VLANs enabled you'd remap the Luci
"se00" from the raw se00 Ethernet interface to eth0.1 via the "Physical
Settings" tab for vlan 1 and create new interfaces in Luci for your new
vlans.
--
Robert Bradley
[-- Attachment #2: Type: text/html, Size: 1418 bytes --]
next prev parent reply other threads:[~2014-02-24 13:48 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
2014-02-24 13:48 ` Robert Bradley [this message]
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=530B4DA3.4080507@gmail.com \
--to=robert.bradley1@gmail.com \
--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