From: Victor Julien <victor@nk.nl>
To: Netfilter Developers List <netfilter-devel@lists.netfilter.org>
Subject: Re: Creating rules without the /sbin/iptables command?
Date: Fri, 19 Mar 2004 23:16:22 +0100 [thread overview]
Message-ID: <405B7136.9040807@nk.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0403192301220.13339-100000@filer.marasystems.com>
Henrik Nordstrom wrote:
> On Fri, 19 Mar 2004, Victor Julien wrote:
>
>
>>>Then you must use incremental commands, keepint the accounting rule
>>>untouched.
>>
>>Hmmm, that i don't want.
>
>
> Then your other option is to dump the existing rule, parse the counter and
> include this in the input.
>
>
>>So i have to read the current counters first by parsing
>>'iptables-save'-output. And i can then recreate the rules and set the
>>counters to their old values?
>
>
> Yes.
>
>
>>Using 'iptables-restore' can i flush one chain, but leave another
>>untouched?
>
>
> Yes, by using disabling the implicit flush (--noflush option) and then
> use the flush command explicitly.
>
>
>>If so, i can create an accounting chain which will not be
>>flushed...
>
>
> True. Probably much better approach than what is discussed above.
So the best option would be to create an accounting chain (e.g ACCOUNT).
If i, for example, want to recreate the rules in the INPUT chain it
should work like this:
Create a file for iptables-restore input:
*filter
:INPUT DROP
# flush this chain
-F INPUT
# now recreate the rules
-A INPUT -p tcp -s 192.168.0.1 --dport 80 -j ACCEPT
...more rules...
COMMIT
Now i would have to call 'iptables-restore --noflush'. This will clear
the entire INPUT chain, but will leave all other (including my ACCOUNT
chain) chains untouched.
Right?
Regards,
Victor
next prev parent reply other threads:[~2004-03-19 22:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 18:46 Creating rules without the /sbin/iptables command? Victor Julien
2004-03-17 19:25 ` Cedric Blancher
2004-03-17 20:59 ` Victor Julien
2004-03-18 8:56 ` Cedric Blancher
2004-03-17 21:34 ` Henrik Nordstrom
2004-03-17 21:34 ` Henrik Nordstrom
2004-03-17 21:53 ` Victor Julien
2004-03-17 23:08 ` John A. Sullivan III
2004-03-17 23:45 ` Henrik Nordstrom
2004-03-17 23:59 ` John A. Sullivan III
2004-03-18 1:15 ` Henrik Nordstrom
2004-03-18 1:30 ` John A. Sullivan III
2004-03-18 1:34 ` Scott MacKay
2004-03-18 8:17 ` Henrik Nordstrom
2004-03-18 7:25 ` Victor Julien
2004-03-18 8:07 ` Henrik Nordstrom
2004-03-18 12:49 ` Victor Julien
2004-03-18 23:45 ` Henrik Nordstrom
2004-03-19 19:01 ` Victor Julien
2004-03-19 22:03 ` Henrik Nordstrom
2004-03-19 22:16 ` Victor Julien [this message]
2004-03-19 22:41 ` Henrik Nordstrom
2004-03-19 22:56 ` Victor Julien
2004-03-20 1:52 ` Henrik Nordstrom
2004-03-18 11:29 ` John A. Sullivan III
2004-03-18 12:52 ` Victor Julien
2004-03-18 14:12 ` John A. Sullivan III
2004-03-23 16:23 ` Adding packet metadata Scott MacKay
2004-03-24 0:06 ` Henrik Nordstrom
2004-03-24 7:38 ` Mike-Ro-Chanel
2004-03-24 8:01 ` Henrik Nordstrom
2004-03-24 8:18 ` Mike-Ro-Chanel
2004-03-24 11:52 ` Scott MacKay
2004-03-24 15:05 ` Henrik Nordstrom
2004-03-17 23:04 ` Creating rules without the /sbin/iptables command? John A. Sullivan III
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=405B7136.9040807@nk.nl \
--to=victor@nk.nl \
--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.