From: Martin <mylists@itcom.com.ar>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: netfilter@vger.kernel.org
Subject: Re: ip_conntrack vs. nf_conntrack
Date: Fri, 16 May 2008 12:32:47 -0300 [thread overview]
Message-ID: <1210951968.23968.2614.camel@kr0sty.1.com.ar> (raw)
In-Reply-To: <482DA36B.6070801@plouf.fr.eu.org>
On Fri, 2008-05-16 at 17:08 +0200, Pascal Hambourg wrote:
> Hello,
>
> Martin a écrit :
> >
> > I use to have a 2.6.18 kernel with some patches, including POM and
> > netfilter ones. The modules I insmod are ip_conntrack_ftp,
> > ip_conntrack_irc, ip_conntrack_tftp, ip_conntrack_amanda and
> > ip_conntrack_sip.
> >
> > Asking around, have finally find that to get patches on mainstream, some
> > names've changed and some code have been modified ¿is that right?
>
> nf_conntrack is layer 3-independent and works with both IPv4 and IPv6,
> while ip_conntrack was IPv4-only.
>
> > Anyway, there aren't nf_conntrack_amanda, nf_conntrack_irc, etc. ¿are
> > there available by now, or need some extra patches or something else?
>
> Most of them were introduced in kernel 2.6.20 along with IPv4 stateful
> NAT. Aliases have been defined, so you can keep using the old names.
Thanks Pascal for the response.
Couldn't find any documentation about that on netfilter site, but've
seen that on the list.
When compiling kernel there are potions to introduce them in netfilter
modules, but there aren't modules or aliases to those names ¿can you
tell me how to add those alias? insmod keep telling me that
ip_conntrack_amanda and ftp couldn't be loaded (I keep trying to load
them on my firewall script).
I've found nf_conntrack_* files, but are .h ones, and are at the include
path of the kernel source code, at netfilter section.
I'll keep searching for more info.
Cheers.
Martin
next prev parent reply other threads:[~2008-05-16 15:32 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
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 [this message]
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=1210951968.23968.2614.camel@kr0sty.1.com.ar \
--to=mylists@itcom.com.ar \
--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