netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH net-next 0/3] virtual netlink device for packet sockets
Date: Fri, 21 Jun 2013 19:38:05 +0200	[thread overview]
Message-ID: <1371836288-13122-1-git-send-email-dborkman@redhat.com> (raw)

This set allows for a virtual netlink device that can be easily used
without modification by tools like tcpdump, Wireshark et al. to debug
and troubleshoot netlink traffic that is exchanged between user and
kernel space. We could even record pcap files for a later analysis.
No code change would be needed on the side of such analyzers, except
adding a simple protocol dissector, for example.

Please have a look at the main description in patch 3. Patch 1 and 2
are just prerequisits for the actual 3rd patch.

I think the device idea is the cleanest solution. We have packet sockets
and they do exactly what we want and expect from them, they have all the
features etc, and user space would not even need to implement code. Thus
adding more and more functionality into af_netlink would be a bigger
surgery and further bloat it up with duplicate code, imho. By taking the
approach with what I'm proposing, we have a clean segregation of
functionality (as: packet sockets vs. netlink sockets), thus keeping it
simple and stupid, and not too complex. 

Thanks !

Daniel Borkmann (3):
  net: if_arp: add ARPHRD_NETLINK type
  net: netlink: add registration/unregistration of virtual tap devices
  packet: nlmon: virtual netlink monitoring device for packet sockets

 drivers/net/Kconfig         |  10 +++
 drivers/net/Makefile        |   1 +
 drivers/net/nlmon.c         | 170 ++++++++++++++++++++++++++++++++++++++++++++
 include/linux/netlink.h     |  10 +++
 include/uapi/linux/if_arp.h |   1 +
 net/netlink/af_netlink.c    | 107 ++++++++++++++++++++++++++++
 6 files changed, 299 insertions(+)
 create mode 100644 drivers/net/nlmon.c

-- 
1.7.11.7

             reply	other threads:[~2013-06-21 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 17:38 Daniel Borkmann [this message]
2013-06-21 17:38 ` [PATCH net-next 1/3] net: if_arp: add ARPHRD_NETLINK type Daniel Borkmann
2013-06-21 17:38 ` [PATCH net-next 2/3] net: netlink: virtual tap device management Daniel Borkmann
2013-06-21 17:38 ` [PATCH net-next 3/3] packet: nlmon: virtual netlink monitoring device for packet sockets Daniel Borkmann
2013-06-24 23:39 ` [PATCH net-next 0/3] virtual netlink " David Miller

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=1371836288-13122-1-git-send-email-dborkman@redhat.com \
    --to=dborkman@redhat.com \
    --cc=davem@davemloft.net \
    --cc=netdev@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).