Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: yoann.juet@univ-nantes.fr
Cc: netfilter@vger.kernel.org
Subject: Re: Second failover failure with conntrackd - INVALID packets
Date: Wed, 04 Feb 2009 11:43:07 +0100	[thread overview]
Message-ID: <4989713B.2010502@netfilter.org> (raw)
In-Reply-To: <49896FEA.3050803@univ-nantes.fr>

Yoann Juet wrote:
> Hi pablo,
> 
> I still have an error as follows with conntrack 0.9.10:
> 
> #make
> ...
> netfilter_conntrack.so -lnfnetlink
> mcast.o: In function `mcast_dump_stats_extended':
> /root/conntrack-tools-0.9.10/src/mcast.c:529: undefined reference to
> `nlif_get_ifflags'
> sync-mode.o: In function `mcast_iface_handler':
> /root/conntrack-tools-0.9.10/src/sync-mode.c:203: undefined reference to
> `nlif_get_ifflags'
> sync-mode.o: In function `mcast_iface_candidate':
> /root/conntrack-tools-0.9.10/src/sync-mode.c:185: undefined reference to
> `nlif_get_ifflags'
> collect2: ld returned 1 exit status
> make[1]: *** [conntrackd] Erreur 1
> make[1]: quittant le répertoire « /root/conntrack-tools-0.9.10/src »
> make: *** [all-recursive] Erreur 1
> 
> Do you have an idea ? The compilation of conntrack 0.9.9 works on the
> same machine.
> 
> Regards,
> 
> Pablo Neira Ayuso wrote:
>> Hi Yoann,
>>
>> Yoann Juet wrote:
>>>> Could you try latest conntrack-tools 0.9.10? I released them yesterday
>>>> along with accumulated updates/fixes. Thanks!
>>> I experience right now some difficulties to compile version 0.9.10 on
>>> lenny. I keep you in touch with test results.
>>
>> Any update? I'm interested in your setup.

Damn. I forgot to update library dependencies. conntrack-tools-0.9.10
requires libnfnetlink-0.0.40. I'm going to fix this now in the git tree.

-- 
"Los honestos son inadaptados sociales" -- Les Luthiers

  reply	other threads:[~2009-02-04 10:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 17:52 Second failover failure with conntrackd - INVALID packets Yoann Juet
2009-01-21 20:52 ` Pablo Neira Ayuso
2009-01-22  9:54   ` Yoann Juet
2009-01-22 16:55     ` Pablo Neira Ayuso
2009-01-23 12:39       ` Yoann Juet
2009-01-25 10:51         ` Pablo Neira Ayuso
2009-01-25 17:55           ` Pablo Neira Ayuso
2009-01-26 19:27             ` Yoann Juet
2009-01-26 23:01               ` Pablo Neira Ayuso
2009-01-29 16:10                 ` Yoann Juet
2009-02-03 10:10                   ` Pablo Neira Ayuso
2009-02-04 10:37                     ` Yoann Juet
2009-02-04 10:43                       ` Pablo Neira Ayuso [this message]
2009-02-06  9:18                         ` Yoann Juet
2009-02-09 11:29                           ` Pablo Neira Ayuso
2009-02-10 13:13                             ` Yoann Juet
2009-02-11  8:49                               ` Pablo Neira Ayuso
2009-02-13  8:21                                 ` Yoann Juet
2009-02-13 15:20                                   ` Pablo Neira Ayuso
     [not found]                                     ` <499B0696.2020300@netfilter.org>
2009-02-23 15:38                                       ` Yoann Juet
2009-02-23 20:40                                         ` Pablo Neira Ayuso
2009-02-24 12:03                                           ` Yoann Juet

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=4989713B.2010502@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=netfilter@vger.kernel.org \
    --cc=yoann.juet@univ-nantes.fr \
    /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