From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@lists.netfilter.org
Subject: Re: packet filter rules updating
Date: Thu, 01 Jun 2006 00:05:33 +0200 [thread overview]
Message-ID: <447E132D.7070002@plouf.fr.eu.org> (raw)
In-Reply-To: <6770617.1149090967505.JavaMail.root@ps12>
Hello,
moniacheli@tiscali.it a écrit :
> I have configured iptables for modifying ip source
> of syslog packets outgoing from one of my router interfaces.
[...]
> If I delete the previuos rules, I have no effect on syslog traffic and
> also if I give new iptables command with different ip source
> syslog pkt maintains the previous ip source (2.2.2.2) while no rule is
> configured with this ip.
The reason of this apparently (but only apparently) unexpected behaviour
is explained in chapter 5 of the NAT-HOWTO
http://www.netfilter.org/documentation/HOWTO//NAT-HOWTO-5.html :
"At each of the points above, when a packet passes we look up what
connection it is associated with. If it's a new connection, we look up
the corresponding chain in the NAT table to see what to do with it. The
answer it gives will apply to all future packets on that connection."
So, once a NAT operation has been associated to a connection and as long
as the connection exists (or, at least, as long as Netfilter connection
tracking keeps track of that connection), the same NAT operation applies
to every packet belonging to that connection. This is independant of any
subsequent iptables rule modification.
> Is there some iptables options that I have to give to force the rules
> updating?
No, iptables cannot help you on this. All you can do is close the
affected connection to delete the entry in the conntrack table and the
NAT operation associated to it. When a new connection is established,
the new NAT rule will apply to it.
next prev parent reply other threads:[~2006-05-31 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 15:56 packet filter rules updating moniacheli
2006-05-31 22:05 ` Pascal Hambourg [this message]
2006-06-01 5:48 ` Philip Craig
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=447E132D.7070002@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--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.