All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin <mylists@itcom.com.ar>
To: netfilter@vger.kernel.org
Subject: ip_conntrack vs. nf_conntrack
Date: Tue, 13 May 2008 11:24:46 -0300	[thread overview]
Message-ID: <1210688686.2956.69.camel@kr0sty.1.com.ar> (raw)

Hi to all.

I've some doubts in what changes have been done to conntrack modules,
but can't find some info about.

Here is my situation:

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?
Anyway, there aren't nf_conntrack_amanda, nf_conntrack_irc, etc. ¿are
there available by now, or need some extra patches or something else?


Thanks in advance, hope someone can give me some light here...


Martin


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

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 14:24 Martin [this message]
2008-05-16 15:08 ` ip_conntrack vs. nf_conntrack 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
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=1210688686.2956.69.camel@kr0sty.1.com.ar \
    --to=mylists@itcom.com.ar \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.