From: alvin <alvin.sm@Mail.Linux-Consulting.com>
To: John Miller <johnmill@brandeis.edu>
Cc: netfilter@vger.kernel.org
Subject: Re: Tree view for rules/chains?
Date: Wed, 5 Aug 2015 12:30:40 -0700 [thread overview]
Message-ID: <20150805193040.GA14052@Mail.Linux-Consulting.com> (raw)
In-Reply-To: <CAGYMsbtfZWaFfE7XzKOhJCoSexZ50KBMmzngwhi4i3h_fUNYFA@mail.gmail.com>
hi ya john
On Wed, Aug 05, 2015 at 12:50:43PM -0400, John Miller wrote:
> Hi folks,
>
> We keep pretty simple firewall rulesets for the most part. That said,
> it'd be nice to be able to display chains and rules in a tree-based
> format: it'd help to visualize more complex rulesets. Do you all know
> of any existing tools that'll let me display things in a tree
> structure--sort of the iptables equivalent of the 'tree' command for
> files and directories?
how and what would you want to change for the output of "iptables -nvL"
you could start with:
iptables -nvL | awhk '{ show only what you want to see}'
pixie dust
alvin
# http://IPtables-BlackList.net
#
next prev parent reply other threads:[~2015-08-05 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 16:50 Tree view for rules/chains? John Miller
2015-08-05 19:30 ` alvin [this message]
2015-08-05 20:22 ` John Miller
2015-08-05 20:52 ` alvin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150805193040.GA14052@Mail.Linux-Consulting.com \
--to=alvin.sm@mail.linux-consulting.com \
--cc=johnmill@brandeis.edu \
--cc=netfilter@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.