From: "Christoph A." <casmls@gmail.com>
To: Elison Niven <elison.niven@gmail.com>
Cc: netfilter@vger.kernel.org, elison.niven@matrixtelesol.com,
"cas >> \"Christoph A.\"" <casmls@gmail.com>
Subject: Re: Get source IP of packet through PREROUTING CHAIN
Date: Tue, 11 Aug 2009 15:44:51 +0200 [thread overview]
Message-ID: <4A8175D3.3050705@gmail.com> (raw)
In-Reply-To: <21df6cb70908110637s60abb999y5358fd22eeb89486@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
On 11.08.2009 15:37, Elison Niven wrote:
> Hi,
>
> What I need is to be able to know the source IP and port of the
> packets received at a particular port (10000 here) in user space
> through a C language interface or may be can I read somewhere from the
> proc directory?
I guess
/proc/net/nf_conntrack
will be handy for you.
kind regards,
Christoph A.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-08-11 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 4:39 Get source IP of packet through PREROUTING CHAIN Elison Niven
2009-08-11 12:36 ` Gáspár Lajos
2009-08-11 13:37 ` Elison Niven
2009-08-11 13:44 ` Christoph A. [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=4A8175D3.3050705@gmail.com \
--to=casmls@gmail.com \
--cc=elison.niven@gmail.com \
--cc=elison.niven@matrixtelesol.com \
--cc=netfilter@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