From: Norman Yarvin <yarvin@yarchive.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Firewall configuration in 3.10.50-1
Date: Mon, 15 Sep 2014 11:57:33 -0400 [thread overview]
Message-ID: <20140915155733.GA5394@muttonhead.home.lan> (raw)
In-Reply-To: <CAA93jw7AAU-HPHrJ5OR0f=K2WgyhU3Zmx27J-9ZbQ6uXFJcjLg@mail.gmail.com>
Ah, okay.
It seems like the GUI could be fixed by just nuking the "firewall
settings" tab. (Since if someone does try to use it, it'll interact
in some unspecified way with the existing "s+" and "gw+" rules.)
On Mon, Sep 15, 2014 at 06:32:09PM +0300, Dave Taht wrote:
>It is a bug in the gui. To get efficiency in the firewall rules cero
>uses a pattern match
>to blend together all the interfaces. So you see in
>/etc/config/firewall file lines that use
>
>s+ To pattern match the three secure interfaces (se00, sw00, sw10)
>gw+ To pattern match the guest interfaces.
>
>
>
>On Mon, Sep 15, 2014 at 6:22 PM, Norman Yarvin <yarvin@yarchive.net> wrote:
>> I was just bringing up a router with 3.10.50-1, and noticed something
>> that seemed amiss in the default firewall configuration. That is,
>> under the Network / Interfaces tab, most of the interfaces, under
>> "Firewall Settings", weren't assigned to any "firewall zone" ("guest",
>> "wan", or "lan"), but rather were left as "unspecified".
>>
>> Maybe this is on purpose for some reason, but it seems worth
>> mentioning.
>>
>>
>> --
>> Norman Yarvin http://yarchive.net/blog
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
>--
>Dave Täht
>
>https://www.bufferbloat.net/projects/make-wifi-fast
prev parent reply other threads:[~2014-09-15 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 15:22 Norman Yarvin
2014-09-15 15:32 ` Dave Taht
2014-09-15 15:57 ` Norman Yarvin [this message]
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=20140915155733.GA5394@muttonhead.home.lan \
--to=yarvin@yarchive.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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