From: Wang Jian <lark@linux.net.cn>
To: Pablo Neira <pablo@eurodev.net>
Cc: netfilter-devel@lists.netfilter.org, Amin Azez <azez@ufomechanic.net>
Subject: Re: nfnetlink-ctnetlink working: INSTRUCTIONS
Date: Sat, 16 Apr 2005 07:50:32 +0800 [thread overview]
Message-ID: <20050416073637.0352.LARK@linux.net.cn> (raw)
In-Reply-To: <42602331.6060706@eurodev.net>
Hi Pablo Neira,
Thanks for you information :)
I will look into conntrack-tool.
BTW:
Is there any documentation about ct-event notification API /
libnfnetlink / libctnetlink?
If there is none, I think I can help drafting it. But I need some hints
on the big picture.
On Fri, 15 Apr 2005 22:25:21 +0200, Pablo Neira <pablo@eurodev.net> wrote:
> Wang Jian wrote:
> > Hi Pablo Neira,
> >
> > The current patches (dated 14-Apr), seems to not emit event messages,
> > such as when new connection is established.
>
> Hm it works just fine here.
>
> o The ct-event notification API is ok, try this test:
> http://people.netfilter.org/~pablo/patches/test/ct-event-test.tar.gz
>
> o Netlink notification works fine as well via:
> http://people.netfilter.org/~pablo/conntrack-tool/
>
> Try:
> # conntrack -E conntrack
>
> So I don't see any problem.
>
> > The only event emitter I find is in ip_conntrack_in()
> >
> > if (set_reply && !test_and_set_bit(IPS_SEEN_REPLY_BIT, &ct->status))
> > ip_conntrack_event_cache(IPCT_STATUS, *pskb);
> >
> > set_reply is set to 1 only when the first reply packet seen from server
> > end of a "connection", and !test_and_set_bit(IPS_SEEN_REPLY_BIT, &ct->status)
> > is supposed to be true at the moment. So it will emit event once. But
> > in my test, cntltest doesn't receive this event.
> >
> > Did I miss something?
>
> I'll update ctnltest.c soon since it's currently broken. I haven't mind
> about it so far.
>
> --
> Pablo
--
lark
next prev parent reply other threads:[~2005-04-15 23:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 10:45 nfnetlink-ctnetlink working: INSTRUCTIONS Amin Azez
2005-04-14 8:35 ` Wang Jian
2005-04-14 9:40 ` Pablo Neira
2005-04-14 9:59 ` Wang Jian
2005-04-14 10:20 ` Pablo Neira
2005-04-15 6:54 ` Wang Jian
2005-04-15 20:25 ` Pablo Neira
2005-04-15 23:50 ` Wang Jian [this message]
2005-04-18 7:14 ` Wang Jian
2005-04-18 12:49 ` Amin Azez
2005-04-14 16:05 ` Amin Azez
2005-04-14 10:15 ` Wang Jian
2005-04-14 16:03 ` Amin Azez
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=20050416073637.0352.LARK@linux.net.cn \
--to=lark@linux.net.cn \
--cc=azez@ufomechanic.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@eurodev.net \
/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.