From: Patrick McHardy <kaber@trash.net>
To: Retesh Chadha <retesh.chadha@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Parsing ULOG message received on netlink socket
Date: Fri, 29 Sep 2006 15:40:43 +0200 [thread overview]
Message-ID: <451D225B.6030908@trash.net> (raw)
In-Reply-To: <b322db070609272111o4e0b097cw9ee64dc4614810dc@mail.gmail.com>
Retesh Chadha wrote:
> Hi All
> I am trying to ULOG certain packets based on a iptable rule.
>
> When the ulog daemon receives data on the netlink socket, it is raw
> data, which I dont know how to parse, apart from structure nlmsghdr,
> that is its header.
>
> My requirement is to parse the received buffer on netlink socket so as
> to get the source IP address of the IP packet. Are there any routines
> or macros to do so? I think struct sk_buff is the buffer received on
> netlink socket, but not sure.
>
> Please let me know if someone is aware of the same, or some pointers
> where I can get this info.
Check out ulogd or nfnetlink_log and libnfnetlink.
next prev parent reply other threads:[~2006-09-29 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 4:11 Parsing ULOG message received on netlink socket Retesh Chadha
2006-09-29 13:40 ` Patrick McHardy [this message]
2006-09-29 14:07 ` Maik Hentsche
2006-10-05 7:11 ` Retesh Chadha
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=451D225B.6030908@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=retesh.chadha@gmail.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.