From: Pablo Neira <pablo@eurodev.net>
To: Swaroop Ashish <sashish@novell.com>, netfilter-devel@lists.netfilter.org
Subject: Re: Unable to receive data Netlinks sockets
Date: Thu, 25 Mar 2004 10:28:07 +0100 [thread overview]
Message-ID: <4062A627.3070002@eurodev.net> (raw)
In-Reply-To: <s06214ce.076@prv-mail25.provo.novell.com>
Hi,
Swaroop Ashish wrote:
> I want to write a test program to
>receive all the packets recieved on the system via this test program
>using Netlinks sockets. Can anyone please tell me what is wrong in the
>following program and what configuration/rules should be added to
>Iptables to do the same.
>
>
if you want to play around with ip_queue, the module which let you send
packets from kernel space to user space and vice-versa, you *should* use
libipq instead of using raw netlink sockets, please have a look at
libipq available in iptables source code.
regards,
Pablo
next prev parent reply other threads:[~2004-03-25 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 6:07 Unable to receive data Netlinks sockets Swaroop Ashish
2004-03-25 9:28 ` Pablo Neira [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-25 9:37 Swaroop Ashish
[not found] <s06245ee.076@prv-mail25.provo.novell.com>
2004-03-25 10:10 ` Pablo Neira
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=4062A627.3070002@eurodev.net \
--to=pablo@eurodev.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=sashish@novell.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.