From: Pablo Neira Ayuso <pablo@netfilter.org>
To: laurent.brando@mindspeed.com
Cc: netfilter-devel@vger.kernel.org
Subject: Re: NFCT_Q_UPDATE and IPv6
Date: Mon, 15 Oct 2007 17:18:48 +0200 [thread overview]
Message-ID: <471384D8.9070205@netfilter.org> (raw)
In-Reply-To: <OF38CFDD8B.3B74F76F-ONC125736B.0053E9D0-C125736B.0055898A@mindspeed.com>
laurent.brando@mindspeed.com wrote:
> I'm facing some issues trying to update UDP/TCP timeout attribut of an
> existing Ipv6 conntrack.
>
> It looks like call to nfct_query(ct_handler, NFCT_Q_UPDATE, ct) never
> returns and my application thread
> gets killed.
>
> I'm about to put some debug after the call to nfct_query , but I would
> like to know if any of you is aware of such
> problem or similar issue.
>
> Also, any proposal to narrow down the issue in an efficient way would be
> appreciated.
>
> I'm using linux 2.6.21 + libnfnetlink 0.0.30 + libnetfilter_conntrack
> 0.0.81.
Any update on this report?
--
"Los honestos son inadaptados sociales" -- Les Luthiers
prev parent reply other threads:[~2007-10-15 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 15:34 NFCT_Q_UPDATE and IPv6 laurent.brando
2007-10-08 5:11 ` Patrick McHardy
2007-10-15 15:18 ` 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=471384D8.9070205@netfilter.org \
--to=pablo@netfilter.org \
--cc=laurent.brando@mindspeed.com \
--cc=netfilter-devel@vger.kernel.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.