All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Amin Azez <azez@ufomechanic.net>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: problems with conntrackd-0.8.2 and 0.8.1
Date: Fri, 28 Jul 2006 16:54:28 +0200	[thread overview]
Message-ID: <44CA2524.2040008@netfilter.org> (raw)
In-Reply-To: <44C790BD.3090207@ufomechanic.net>

Amin Azez wrote:
> I'm trying out the new ctnetlink with conntrackd-0.8.2
> 
> I've got the latest libnfnetlink and libnetfilter_conntrack from svn,
> but conntrackd-0.8.2 and 0.8.1 give this error:
> /opt/KERNEL/conntrackd/conntrackd-0.8.2/src/events.c:67: undefined
> reference to `nfct_conntrack_is_snatted'
> events.o(.text+0x260):/opt/KERNEL/conntrackd/conntrackd-0.8.2/src/events.c:58:
> undefined reference to `nfct_conntrack_is_dnatted'
> 
> and loads more.
 >
> I can't find reference to nfct_conntrack_is_snatted anywhere in any of
> my source trees, even google and gmane have nothing to say.
 >
> nm -as /usr/local/lib/libnetfilter_conntrack.a doesn't find the symbol
> either, or any symbol with "snat" within it.
> 
> Is there a file missing from conntrackd?

No, probably you forgot to apply the patches included in the directory 
"patches" inside conntrackd-0.8.2 that provides those functions.

-- 
The dawn of the fourth age of Linux firewalling is coming; a time of 
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris

      reply	other threads:[~2006-07-28 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25 13:17 [PATCH 0/8] ctnetlink updates incarnation #2 Pablo Neira Ayuso
     [not found] ` <44C646C7.2030704@ufomechanic.net>
     [not found]   ` <44C66068.6020000@netfilter.org>
2006-07-26 15:56     ` problems with conntrackd-0.8.2 and 0.8.1 Amin Azez
2006-07-28 14:54       ` Pablo Neira Ayuso [this message]

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=44CA2524.2040008@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=azez@ufomechanic.net \
    --cc=netfilter-devel@lists.netfilter.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.