public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefano Pettini <spettini@inwind.it>
To: linux-kernel@vger.kernel.org
Subject: ip_conntrack_ftp and ip_nat_ftp module problem
Date: Fri, 04 Apr 2003 22:05:04 +0200	[thread overview]
Message-ID: <3E8DE570.6050801@inwind.it> (raw)

Hi Kernel guys!

I'm running a 2.4.20 (i686, configured with "make menuconfig") and I 
have the following problem:

If I compile into the kernel ip_conntrack module, and its ftp and irc 
extensions, I can't insert ip_nat_ftp because it "can't find 
ip_conntrack_ftp module". If I want ftp nat and connection tracking, I 
have to compile ip_conntrack_* as modules because it seems that ip_nat_* 
are always compiled as modules instead of being compiled directly into 
the kernel when requested to do so, like ip_conntrack_*.

I think it's only a makefile problem. Can you fix it for 2.4.21 ?? I see 
"CONFIG_IP_NF_NAT_IRC=m" in config file, but that line doesn't exist in 
menuconfig.

Thank you very much.

PS.
Another question:

To have a working FTP or IRC NAT and connection tracking, I have to 
insert their modules (*_ftp and *_irc) manually with insmod or modprobe. 
lsmod tells they're usage count is always 0, even if they "work". Why 
can't those modules be automagically probed when required, like every 
other module, for example when I add a nat or a state rule with 
iptables? This inserts ip_conntrack, but not ip_conntrack_* and 
ip_nat_*. And with their usage count = 0, there's a risk that rmmod -a 
removes them.

Stefano from Rome


                 reply	other threads:[~2003-04-04 19:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3E8DE570.6050801@inwind.it \
    --to=spettini@inwind.it \
    --cc=linux-kernel@vger.kernel.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