Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Martin <mylists@itcom.com.ar>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>, netfilter@vger.kernel.org
Subject: Re: ip_conntrack vs. nf_conntrack
Date: Tue, 20 May 2008 10:05:03 -0300	[thread overview]
Message-ID: <1211288704.23968.4406.camel@kr0sty.1.com.ar> (raw)
In-Reply-To: <alpine.LNX.1.10.0805191942020.15136@fbirervta.pbzchgretzou.qr>


On Mon, 2008-05-19 at 19:42 +0200, Jan Engelhardt wrote:
> On Monday 2008-05-19 15:13, Martin wrote:
> >> On Friday 2008-05-16 18:07, Martin wrote:
> >> >
> >> >So I've just one question at least. If there aren't nf_conntrack_*
> >> >modules or aliases, does the amanda, ftp, quake3, etc. modules work just
> >> >loading nf_conntrack? If so, I think I'm ready to go with this kernel
> >> >history.
> >> 
> >> No, nf_conntrack_ftp is required for FTP (and similarly for the
> >> others).
> >
> >But there isn't nf_conntrack_ftp.ko module. May be it have been renamed
> >to /lib/modules/2.6.25/kernel/net/ipv4/netfilter/nf_nat_ftp.ko ?
> 
> 19:34 yaguchi:~/pub/Documents > modinfo nf_conntrack_ftp
> filename:
> /lib/modules/2.6.23.17-ccj64-rt/kernel/net/netfilter/nf_conntrack_ftp.ko
> alias:          ip_conntrack_ftp
> description:    ftp connection tracking helper
> author:         Rusty Russell <rusty@rustcorp.com.au>
> license:        GPL
> srcversion:     5719E7793C1052C8385FF11
> depends:        nf_conntrack
> vermagic:       2.6.23.17-ccj64-rt SMP preempt mod_unload 586 REGPARM 
> parm:           ports:array of ushort
> parm:           loose:bool
> 
> When I say nf_conntrack_ftp, I meant nf_conntrack_ftp.


Pascal explained me that. Sorry, my fault. I made
nf_conntrack_(ftp/amanda) build-in kernel, not as a module, so there
isn't any *.ko with that name to modprobe.

Thanks for your advice, I'll search for more docs about difference
module--build-in, just to see if I can change some parameters while
modprobe or so.


Cheers


Martín


  reply	other threads:[~2008-05-20 13:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 14:24 ip_conntrack vs. nf_conntrack Martin
2008-05-16 15:08 ` Pascal Hambourg
2008-05-16 15:14   ` Jan Engelhardt
2008-05-16 15:15     ` Jan Engelhardt
2008-05-16 15:45     ` Pascal Hambourg
2008-05-16 16:07       ` Martin
2008-05-17 11:30         ` Jan Engelhardt
2008-05-19 13:13           ` Martin
2008-05-19 17:42             ` Jan Engelhardt
2008-05-20 13:05               ` Martin [this message]
2008-05-20 14:41                 ` Pascal Hambourg
2008-05-20 14:58                   ` Martin
2008-05-20 15:31                 ` Jan Engelhardt
2008-05-17 11:36         ` Pascal Hambourg
2008-05-19 13:20           ` Martin
2008-05-19 14:41             ` Pascal Hambourg
2008-05-19 14:55               ` Martin
2008-05-19 17:10                 ` Pascal Hambourg
2008-05-16 15:32   ` Martin
2008-05-17 11:28     ` Pascal Hambourg

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=1211288704.23968.4406.camel@kr0sty.1.com.ar \
    --to=mylists@itcom.com.ar \
    --cc=jengelh@medozas.de \
    --cc=netfilter@vger.kernel.org \
    --cc=pascal.mail@plouf.fr.eu.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