All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Ezust <alan.ezust@presinet.com>
To: "Pablo Neira Ayuso" <pablo@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: testing installation of conntrack command line tool
Date: Thu, 12 Oct 2006 16:09:46 -0700	[thread overview]
Message-ID: <200610121609.47726.alan.ezust@presinet.com> (raw)
In-Reply-To: <200610121301.06023.alan.ezust@presinet.com>

Here is a little follow-up - I discovered that
regardless of what kernel options I enabled, I am unable to actually build the 
nf_conntrack_core or nf_conntrack_standalone sources in net/netfilter with 
the Makefile that is generated by linux 2.6.16.29.

Currently, the generated Makefile in net/netfilter only builds these files: 
nf_conntrack_core, nf_conntrack_standalone, if CONFIG_NF_CT_NETLINK is 
defined. 

However, there doesn't seem to be such a config option available in the kernel 
configuration for this version. Adding a line CONFIG_NF_CT_NETLINK to 
my .config file doesn't seem to make a difference. 

So in fact, when I thought I was building conntrack, I was not. 

Is this a known issue?


On Thursday 12 October 2006 13:01, Alan Ezust wrote:
> Hi Pablo,
>
> I'm still having the same problem. I built libnfnetlink and libnfconntrack
> from svn, adn then I built conntrack userspace tool 1.0beta2. All of the
> errors in dmesg are gone now.
>
> conntrack -L conntrack still lists nothing.
>
> Here is my latest kernel .config file. I am still having the same problem
> with the conntrack userspace tool, running with Linux 2.6.16.29 - so I'm
> thinking I will have to upgrade to 2.6.18, but alas, that causes breakages
> with some of the patchlets that we are maintaining, so I wanted to put that
> off til later.
>
> Is there anything obviously wrong/missing about this kernel configuration?
>
> If there are definite incompatibilities with conntrack 1.00beta2 and linux
> 2.6.16.29, please let me know and I'll stop barking up this tree...
>
> $ lsmod
>
> nfnetlink_queue        12384  0
> ipt_recent             11180  2
> ipt_LOG                 6496  4
> ipt_bin                22020  7
> iptable_promisc         1856  1
> ipt_multiport           2432  10
> ip_conntrack_pptp      10544  0
> ip_conntrack_netbios_ns     2784  0
> ip_conntrack_irc        6456  0
> xt_CONNMARK             2208  2
> xt_connmark             1760  2
> ipt_DATA                4192  5
> ipt_psd                44036  1
> xt_state                1888  4
> xt_conntrack            2304  4
> xt_pkttype              1664  1
> xt_MARK                 2368  0
> ipt_regex               7752  1
> tulip                  49952  0
> eepro100               30576  0
> 8139too                25376  0
> 3c59x                  44104  0

      reply	other threads:[~2006-10-12 23:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03 22:18 testing installation of conntrack command line tool Alan Ezust
2006-10-04 19:48 ` Pablo Neira Ayuso
2006-10-04 20:33   ` Alan Ezust
2006-10-04 22:04     ` Pablo Neira Ayuso
2006-10-04 22:31       ` Alan Ezust
2006-10-05 10:23         ` Pablo Neira Ayuso
2006-10-06 20:14           ` Alan Ezust
2006-10-07 11:32             ` Pablo Neira Ayuso
2006-10-10 19:15               ` Alan Ezust
2006-10-12 20:01               ` Alan Ezust
2006-10-12 23:09                 ` Alan Ezust [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=200610121609.47726.alan.ezust@presinet.com \
    --to=alan.ezust@presinet.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@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.