From: Balazs Scheidler <bazsi@balabit.hu>
To: Tim Gardner <timg@tpi.com>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: 2.4 SNAT fails randomly
Date: Tue, 18 Nov 2003 17:20:45 +0100 [thread overview]
Message-ID: <20031118162045.GF4086@balabit.hu> (raw)
In-Reply-To: <200311180835.09794.timg@tpi.com>
On Tue, Nov 18, 2003 at 08:35:09AM -0700, Tim Gardner wrote:
> I've been thinking more about this scenario. When a standard distribution like
> SuSE-9.0 boots, the interfaces are IFF_UP sometime before firewall rules are
> installed. This is particularly a problem in the case of a NAT router. Is
> there any way to flush /proc/net/ip_conntrack to make sure that you get rid
> of entries that were established between the time the interfaces were brought
> up and the time the rules were installed? Removing the ip_conntrack modules
> seems kind of brute force, and does not work on kernels where ip_conntrack is
> not a module.
I think this scenario is inherently broken and the distribution should be
fixed. It is meant to be possible to load rulesets when the interfaces are
not yet configured.
Nevertheless the possibility to clear the conntrack table is desperately
needed as well as other conntrack manipulations. This area is getting less
neglected with the introduction of ctnetlink, albeit process is slow.
--
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
next prev parent reply other threads:[~2003-11-18 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 18:03 2.4 SNAT fails randomly Tim Gardner
2003-11-16 9:52 ` Balazs Scheidler
2003-11-16 16:53 ` Tim Gardner
2003-11-18 15:35 ` Tim Gardner
2003-11-18 16:20 ` Balazs Scheidler [this message]
2003-11-19 7:46 ` Eldad Zack
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=20031118162045.GF4086@balabit.hu \
--to=bazsi@balabit.hu \
--cc=netfilter-devel@lists.netfilter.org \
--cc=timg@tpi.com \
/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.