From: Patrick Schaaf <bof@bof.de>
To: Bart De Schuymer <bdschuym@pandora.be>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: /etc/sysconfig/iptables format
Date: Sun, 24 Nov 2002 12:52:52 +0100 [thread overview]
Message-ID: <20021124115252.GD14672@oknodo.bof.de> (raw)
In-Reply-To: <200211241328.57401.bdschuym@pandora.be>
Hello Bart,
> I'd like your opinion about the way ebtables makes atomically writing a
> complete table to the kernel, possible.
[description of "reference file manipulation" approach to construct tables]
I like the scheme! May I have it for iptables, too, please?
Why do I like it? Using the reference file, permits test-construction
of an arbitrary rule set, with full rule consistency / error checking,
and inspection of the result, without modifying the runtime rule set
in any way. That's a great help when extending / modifying rule sets.
With the current iptables, about the only sane alternative is to
carefully construct a user mode linux instance mirroring your real
system, and testing table construction there. The idea of applying
all changes (optionally) to a reference file, saves big effort here.
Part of why I like this, is the possibility to run the ruleset
construction under an arbitrary uid. Only the final commit needs
to be done as root. When your construction scripts become large
that may be a great option, I think.
I have a small proposal to augment the idea: as an alternative to
specifying the reference file on the command line, could you define
a "standard environment variable" which, when set, gives the name
of the reference file to use? That way, one could run "rule set
construction scripts" completely unchanged, i.e. without fiddling
with the commandline of all the ??tables-commands in the scripts.
Just give something different in the environment before calling
the initial construction script.
> One could say the file being binary is a problem.
I don't think so. Having it binary, provides a rather strong hint that
nothing but the delivered tools (ebtables, in your case) are supposed
to understand the format. Doesn't raise futile expectations that way.
best regards
Patrick
next prev parent reply other threads:[~2002-11-24 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 5:21 /etc/sysconfig/iptables format Arch Harris
2002-11-24 10:40 ` Patrick Schaaf
2002-11-24 12:28 ` Bart De Schuymer
2002-11-24 11:52 ` Patrick Schaaf [this message]
2002-11-24 14:14 ` Bart De Schuymer
2002-11-24 15:16 ` kernel 2.5 and patch-o-matic laurent.ml
[not found] <Pine.LNX.4.44.0211241130360.17298-100000@azalea.cs.jmu.edu>
2002-11-24 20:06 ` /etc/sysconfig/iptables format Bart De Schuymer
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=20021124115252.GD14672@oknodo.bof.de \
--to=bof@bof.de \
--cc=bdschuym@pandora.be \
--cc=netfilter-devel@lists.netfilter.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.