From: Christian Hammers <ch@westend.com>
To: Filip Sneppe <filip.sneppe@cronos.be>
Cc: netfilter@lists.netfilter.org
Subject: Re: /proc/net/ip_conntrack filling without ipt_conntrack.o loaded?
Date: Tue, 14 Jan 2003 17:01:34 +0100 [thread overview]
Message-ID: <20030114160134.GC6664@westend.com> (raw)
In-Reply-To: <1042559354.464.770.camel@xbox>
On Tue, Jan 14, 2003 at 04:49:14PM +0100, Filip Sneppe wrote:
> If *all* your traffic is essentially asymetric in
> nature, you'de be better off not using ip_conntrack at all...
Yes, thought so, too. - The question that I was trying to ask in this
thread was, why the /proc/net/ip_conntrack is filled by the kernel
although I *already did* remove the module!
I would have guessed that just after I removed the ipt_conntrack module
and all the sub modules (ipt_conntrack_ftp, nat etc) the
/proc/net/ip_conntrack would either vanish or at least return nothing
because the code at the other end of the virtual device has gone.
But apparently it did not go away so I suspected a kernel function that
was fogotten to free or similar...
bye,
-christian-
--
Christian Hammers WESTEND GmbH | Internet-Business-Provider
Technik CISCO Systems Partner - Authorized Reseller
Lütticher Strasse 10 Tel 0241/701333-11
ch@westend.com D-52064 Aachen Fax 0241/911879
next prev parent reply other threads:[~2003-01-14 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 9:37 filtering asym. routing without "ip_conntrack: table full"? Christian Hammers
2003-01-14 12:12 ` /proc/net/ip_conntrack filling without ipt_conntrack.o loaded? Christian Hammers
2003-01-14 13:43 ` Filip Sneppe
2003-01-14 15:06 ` Christian Hammers
2003-01-14 15:49 ` Filip Sneppe
2003-01-14 16:01 ` Christian Hammers [this message]
2003-01-14 16:09 ` Filip Sneppe
2003-01-14 16:37 ` Christian Hammers
2003-01-14 16:58 ` Filip Sneppe
2003-01-21 6:16 ` filtering asym. routing without "ip_conntrack: table full"? ard-netfilter
2003-01-21 10:45 ` Jakub Jakacki
2003-01-29 2:14 ` Arnt Karlsen
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=20030114160134.GC6664@westend.com \
--to=ch@westend.com \
--cc=filip.sneppe@cronos.be \
--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