From: Geert van der Ploeg <netfilter@geert.triple-it.nl>
To: netfilter@lists.netfilter.org
Subject: iptables-restore: commit not at end of table
Date: Wed, 09 Mar 2005 12:43:02 +0100 [thread overview]
Message-ID: <422EE146.1070808@geert.triple-it.nl> (raw)
Hi all,
After updating a firewall from iptables 1.2.7a to a later version, my
ruleset doesn't work anymore.
It fails on COMMIT-lines that are not at the end of a table definition.
I used commits for cutting my (sometimes quite large) rulesets into
smaller parts and make sure I always keep a working configuration, even
if some rules fail.
For example:
- define management-access definitions (allow SSH from
management-stations, etc)
- COMMIT
- define other rules that get changed a lot and thus have a larger
chance of containing errors.
Having looked at the source-code, I discovered that it is caused by some
extra checks on 'in_table' (in iptables-restore.c), which got inserted
between 1.2.7a and 1.2.8. The changelog doesn't say why.
My questions:
1. Does anybody know what was the reason for the extra checks?
2. Is the effect of not-working-commits-in-middle-of-table-definition
intended or not? If so, what was the intention?
2. Did anybody use those commits like I did? And if so, how do you
accomplish the same without this feature?
3. Is this the right list to ask these questions or should they be asked
on the developer-list?
Thanks!
Geert van der Ploeg
next reply other threads:[~2005-03-09 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 11:43 Geert van der Ploeg [this message]
2005-03-09 13:45 ` iptables-restore: commit not at end of table Pablo Neira
2005-03-11 13:45 ` Geert van der Ploeg
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=422EE146.1070808@geert.triple-it.nl \
--to=netfilter@geert.triple-it.nl \
--cc=netfilter@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.