From: Philip Craig <philipc@snapgear.com>
To: Jeff Machesky <jeff@codebest.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: NAT rules not clearing, delays in loading
Date: Mon, 27 Feb 2006 11:44:55 +1000 [thread overview]
Message-ID: <44025997.6080105@snapgear.com> (raw)
In-Reply-To: <43FF4744.8040706@codebest.com>
On 02/25/2006 03:49 AM, Jeff Machesky wrote:
> When rule #1 is first put in place the packets do not start to route
> right away, they often take up to a minute or so to take hold. Once in
> a while I'll get lucky and the rule appears to take effect right away.
> This is verified by ethereal dumps.
>
> The other problem, after removing rule #1 or for that matter flushing
> the entire nat chain (iptables -t nat -F) the rules will keep working
> for several minutes.
This is probably due to the conntrack entry still existing.
The new NAT rules are not applied until the conntrack expires.
Check this with 'cat /proc/net/ip_conntrack'.
The relatively new conntrack tool can delete them
(and provides a faster way of listing them too).
http://netfilter.org/projects/conntrack/downloads.html
prev parent reply other threads:[~2006-02-27 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 17:49 NAT rules not clearing, delays in loading Jeff Machesky
2006-02-27 1:44 ` Philip Craig [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=44025997.6080105@snapgear.com \
--to=philipc@snapgear.com \
--cc=jeff@codebest.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox