netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ilninno <ilninno@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: Connection pid
Date: Mon, 26 Jan 2009 00:32:19 +0100	[thread overview]
Message-ID: <92770c820901251532v6e0f12a0w891ddbd0e2337680@mail.gmail.com> (raw)

Hello again!

I have some problems with libnetfilter_queue, I need connections pid.
My program captures outgoings connections(only new connections)

1- I tried with netstat but its too low.  (each netstat call changes
process context)
2- I tried with netstat code, but its too low because all the info is
in different files. The first problem is get connection inode
(/proc/net/tcp or /proc/net/udp), with inode then i must search in fd
(inodes) of each process (/proc/pid/fd/). This is too low, Im not
using cache because i only capture new connections.

There is any reference to process id or process name in struct
nfq_data *pkt or similar struct?


Thanks for your time and sorry for my english.

                 reply	other threads:[~2009-01-25 23:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=92770c820901251532v6e0f12a0w891ddbd0e2337680@mail.gmail.com \
    --to=ilninno@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).