From: Patrick McHardy <kaber@trash.net>
To: Sumit Pandya <sumit@elitecore.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: libnfnetlink/libctnetlink ctrace
Date: Fri, 06 Jun 2003 15:44:14 +0200 [thread overview]
Message-ID: <3EE09AAE.8040902@trash.net> (raw)
In-Reply-To: <019201c32c2c$b66b89f0$010f430a@elitecore7>
If you like danger you could try my enhanced ctnetlink patch,
an slightly outdated version (1 1/2 weeks) is available at
trash.net/~kaber/ctnetlink. It adds notifications for all conntrack
events. This is work in progress and is not ready for serious use, but i
would of course be glad if someone else would try it. I'm syncing my
workstation and my gateway for about a week now, so it probably won't
crash your machine. If you would like to try it, i'm going to update the
patch and the userspace tool this weekend. i don't know ctrace but the
updated tool can display all events in userspace.
Bye,
Patrick
Sumit Pandya wrote:
>Hi All,
> Refrencing from below mentioned link I try to search
>libnfnetlink/libctnetlink ctrace but couldnot locate source/binary of these
>2 packages.
>http://lists.netfilter.org/pipermail/netfilter-devel/2002-April/007515.html
> It seems that www.linux-sna.org is closed. Do I've pointer to access
>source for those libraries and program? I think from
>http://cvs.netfilter.org/netfilter/iptables2/ libraries can be downloaded
>but what about ctrace?
>
>-- Sumit
>
>
next prev parent reply other threads:[~2003-06-06 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030602222644.6397.85967.Mailman@kashyyyk>
2003-06-06 13:08 ` libnfnetlink/libctnetlink ctrace Sumit Pandya
2003-06-06 13:44 ` Patrick McHardy [this message]
2003-06-11 12:41 ` Harald Welte
2003-06-11 13:19 ` Patrick McHardy
2006-02-22 6:33 ` Sumit
2006-02-22 6:42 ` 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=3EE09AAE.8040902@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=sumit@elitecore.com \
/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.