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 13:52:35 -0700 [thread overview]
Message-ID: <20150805205235.GA14241@Mail.Linux-Consulting.com> (raw)
In-Reply-To: <CAGYMsbtD7fKUh+W9kK-vQyqqgz2j2cfNK8-nK_oKASvvDreajw@mail.gmail.com>
hi ya john
On Wed, Aug 05, 2015 at 04:22:36PM -0400, John Miller wrote:
> On Wed, Aug 5, 2015 at 3:30 PM, alvin
> <alvin.sm@mail.linux-consulting.com> wrote:
...
> > how and what would you want to change for the output of "iptables -nvL"
> >
>
> Hi Alvin,
>
> What I'd really like is something like (let's see how well this displays):
>
> --filter table--
>
> INPUT (policy reject)
> PREROUTING, OUTPUT, FORWARD, user-defined top-level chains, etc.
> |
> ---------------------------------------------
> | | |
> Rule1 INPUT_USERCHAIN1 INPUT_USERCHAIN2
> Rule2 | | |
> Rule3 Rule1 SUBCHAIN1 Rule1
> Rule4 Rule2 | Rule2
> Rule3 Rule1 Rule3
> Rule4 Rule2 Rule4
> Rule3
> Rule4
>
> --nat table, mangle table, etc.--
doesn't look/sound like a "simple firewall" anymore :-)
reformatting the rules seems to be a job for perl or c :-)
i have "no immediate solution"
pixie dust
alvin
# IPtables-BlackList.net
> This is definitely not something I expect to see from iptables -nvL,
> but more as a shell script or separate standalone utility. If I can
> accomplish something like this with a simple pipe or two (like to
> gnuplot, for example), that'd be fine, too. I figured there might be
> an existing tool for this, or a relatively simple shell script that
> someone had run before.
>
> John
prev parent reply other threads:[~2015-08-05 20:52 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
2015-08-05 20:22 ` John Miller
2015-08-05 20:52 ` alvin [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150805205235.GA14241@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.