Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Norman Yarvin <yarvin@yarchive.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Firewall configuration in 3.10.50-1
Date: Mon, 15 Sep 2014 11:22:59 -0400	[thread overview]
Message-ID: <20140915152259.GA5225@muttonhead.home.lan> (raw)

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

             reply	other threads:[~2014-09-15 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 15:22 Norman Yarvin [this message]
2014-09-15 15:32 ` Dave Taht
2014-09-15 15:57   ` Norman Yarvin

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=20140915152259.GA5225@muttonhead.home.lan \
    --to=yarvin@yarchive.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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