netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Sam Roberts <vieuxtech@gmail.com>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: Any suggestions for getting a pcap of traffic over netlink?
Date: Tue, 22 Mar 2011 11:43:20 +0100	[thread overview]
Message-ID: <4D887D48.6060100@netfilter.org> (raw)
In-Reply-To: <AANLkTi==4LicoDZ5JqY3YD7zSrh=E1GvPp5TJ33L5+_d@mail.gmail.com>

On 22/03/11 00:15, Sam Roberts wrote:
> Obviously, there is no net device to pcap - I'm wondering if anybody
> knows of ways to watch netlink traffic? I don't know netlink well, I'm
> wondering if its possible to do a PF_NETLINK socket that promiscuously
> receives all netlink traffic on all sockets?

This, or any similar feature, does not exist yet.

We can add some NETLINK_CONTROL family that would allows us to sniff all
netlink traffic.

      reply	other threads:[~2011-03-22 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 23:15 Any suggestions for getting a pcap of traffic over netlink? Sam Roberts
2011-03-22 10:43 ` Pablo Neira Ayuso [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=4D887D48.6060100@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=vieuxtech@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 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).