From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alan Ezust <alan.ezust@presinet.com>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: problems building conntrack w/ uclibc - no output
Date: Wed, 20 Dec 2006 12:01:14 +0100 [thread overview]
Message-ID: <458917FA.2080406@netfilter.org> (raw)
In-Reply-To: <200612191557.43981.alan.ezust@presinet.com>
Alan Ezust wrote:
> Anyway, I'm still not quite sure what my problem is with building conntrack.
> I have an older executable that I somehow built successfully, and I can make
> my currently needed changes to libnetfilter_conntrack and run the original
> executable against my patched versions, so I am able to proceed for now, but
> it would be so nice to know why my conntrack builds are always creating
> executables that HANG here:
>
> libnetfilter_conntrack.c
> int nfct_event_conntrack(struct nfct_handle *cth)
> {
> cth->handler = nfct_conntrack_netlink_handler;
> return nfnl_listen(cth->nfnlh, &callback_handler, cth); // NEVER RETURNS FROM
> HERE
> }
It's *not* hanging, nfnl_listen blocks waiting to receive events from
kernel space, this is the *expected behaviour*. Make sure you have
enabled the conntrack event API.
--
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
prev parent reply other threads:[~2006-12-20 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 19:43 problems building conntrack w/ uclibc - no output Alan Ezust
2006-11-28 2:36 ` Pablo Neira Ayuso
2006-11-28 17:38 ` Alan Ezust
2006-11-28 23:14 ` Alan Ezust
[not found] ` <200612081043.59816.alan.ezust@presinet.com>
[not found] ` <457CB353.1010409@netfilter.org>
[not found] ` <200612191557.43981.alan.ezust@presinet.com>
2006-12-20 11:01 ` 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=458917FA.2080406@netfilter.org \
--to=pablo@netfilter.org \
--cc=alan.ezust@presinet.com \
--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.