Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: ip_conntrack vs. nf_conntrack
Date: Fri, 16 May 2008 17:45:13 +0200	[thread overview]
Message-ID: <482DAC09.90304@plouf.fr.eu.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0805161714090.15590@fbirervta.pbzchgretzou.qr>

Jan Engelhardt a écrit :
> On Friday 2008-05-16 17:08, Pascal Hambourg wrote:
> 
>>>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.
> 
> No aliases have been defined.
> 
> $ modinfo nf_conntrack

I meant aliases for helper modules. In most cases other netfilter 
modules should be autoloaded by iptables rules creation or other module 
dependencies, so it should be useless to load them explicitly.

  parent reply	other threads:[~2008-05-16 15:45 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 [this message]
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
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=482DAC09.90304@plouf.fr.eu.org \
    --to=pascal.mail@plouf.fr.eu.org \
    --cc=netfilter@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