From: Amin Azez <azez@ufomechanic.net>
To: netfilter-devel@lists.netfilter.org
Subject: Re: no ctstat? Re: building libctnetlink
Date: Wed, 06 Apr 2005 15:59:32 +0100 [thread overview]
Message-ID: <d30tcp$tsc$1@sea.gmane.org> (raw)
In-Reply-To: <d2rpmi$3n8$1@sea.gmane.org>
Sam Liddicott wrote:
> Pablo Neira wrote:
>
>> Just another UFO mechanic wrote:
>>
>>> I am still trying to compile libctnetlink and libnfnetlink I cannot find
>>> a whole lot of info on it. I have 2 questions
>>>
>>> When I try compile
>>> I get the error
>>> libctnetlink.c:32:39 linux/nfnetlink_conntrack.h: No such file or
>>> directory
>>
>>
>>
>> Have you applied `nfnetlink-ctnetlink-0.13' in pom-ng? Add
>> -I/your/kernel/include/path to your compilation script.
>
>
> Thanks for the tip Pablo; probably a case of user error; but:
>
> When I try to apply nfnetlink-ctnetlink-0.13 from the latest pom-ng
> (20050403), I am told:
>
> nfnetlink-ctnetlink-0.13 has dependency on ctstat, but ctstat is not known
> cannot apply (9 rejects out of 42 hunks)
>
> As far as I can tell ctstats was added to pom-ng in around September
> 2004 time. There is a ctstat folder in my un-tar'd pom-ng, but it is empty.
>
> I'm running patch-o-matic against iptables 1.2.11 and kernel 2.6.10
> source.
So after much looking, for my part, according to section 6.2 of the 2004
workshop summary at
http://www.netfilter.org/documentation/conferences/nf-workshop-2004-summary.html
ctstat has already been merged with... with....
and there you have it.
I can't tell if ctstat has been merged with any particular kernel
version or any particular iptables version or both.
This file,
http://people.netfilter.org/gandalf/old/ctstat/ctstat-040215-2.6, hints
that ctstat may have been merged with kernel 2.6
So assuming that you do have ctstat merged somehow (and
ct_cpu_seq_show() seems to be defined in ip_conntrack_standalone.c on
2.6.10), edit nfnetlink-ctnetlink-0.13/info and remove the dependancy on
ctstat and then apply with
... ... ./runme --batch nfnetlink-ctnetlink-0.13
You'll still get a failure to apply though, which I'm looking into. I'll
post back when I find out more, I'm going to try it on 2.6.11 and then
look at the rejects more closely if that doesn't work.
Amin
next prev parent reply other threads:[~2005-04-06 14:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 9:34 [PATCH] REJECT for 2.6.9+ Jonas Berlin
2005-03-19 9:46 ` Jonas Berlin
2005-03-20 16:11 ` building libctnetlink Just another UFO mechanic
2005-03-20 16:17 ` Just another UFO mechanic
2005-03-20 22:29 ` Pablo Neira
2005-03-21 13:36 ` Just another UFO mechanic
2005-03-21 17:12 ` Pablo Neira
2005-03-24 12:35 ` Just another UFO mechanic
2005-03-24 12:58 ` Pablo Neira
2005-04-04 16:25 ` no ctstat? " Sam Liddicott
2005-04-06 14:59 ` Amin Azez [this message]
2005-04-06 15:48 ` Amin Azez
2005-04-06 16:59 ` Just another UFO mechanic
2005-04-06 16:30 ` Amin Azez
2005-03-26 12:31 ` Wichert Akkerman
2005-03-19 10:50 ` [PATCH] REJECT for 2.6.9+ Jonas Berlin
2005-03-20 16:15 ` Patrick McHardy
2005-03-21 20:51 ` Jonas Berlin
2005-03-30 2:05 ` Yasuyuki KOZAKAI
2005-04-01 6:13 ` Harald Welte
2005-04-03 18:26 ` Patrick McHardy
2005-04-08 7:58 ` Yasuyuki KOZAKAI
2005-04-08 8:32 ` (usagi-core 22742) " YOSHIFUJI Hideaki / 吉藤英明
2005-04-08 9:41 ` Yasuyuki KOZAKAI
2005-04-08 9:48 ` (usagi-core 22748) " YOSHIFUJI Hideaki / 吉藤英明
2005-04-17 22:00 ` Patrick McHardy
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='d30tcp$tsc$1@sea.gmane.org' \
--to=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.