The Netlinksocket family is a Linux kernel interface used for inter-process communication between both the kernel and userspace processes, and between different userspace processes, in a way similar to the Unix domain sockets. Similarly to the Unix domain sockets, and unlike INET sockets, Netlink communication cannot traverse host boundaries. However, while the Unix domain sockets use the file system namespace, Netlink processes are usually addressed by process identifiers. Netlink is designed and used for transferring miscellaneous networking information between the kernel space and userspace processes. Networking utilities, such as the iproute2 family and the utilities used for configuring mac80211-based wireless drivers, use Netlink to communicate with the Linux kernel from userspace. Netlink provides a standard socket-based interface for userspace processes, and a kernel-side API for internal use by kernel modules. Originally, Netlink used the socket family. Netlink is designed to be a more flexible successor to ioctl; describes the protocol in detail.
History
Netlink was created by Alexey Kuznetsov as a more flexible alternative to the sophisticated but awkward ioctl| communication method used for setting and getting external socket options. The Linux kernel continues to support for backward compatibility. Netlink was first provided in the 2.0 series of the Linux kernel, implemented as a character device. By 2013, this interface is obsolete, but still forms an ioctl communication method; compare the use of. The Netlink socket interface appeared in 2.2 series of the Linux kernel.
Packet structure
Unlike BSD sockets using Internet protocols such as TCP, where the message headers are autogenerated, the Netlink message header must be prepared by the caller. The Netlink socket generally works in a -like mode, even if was used to create it. The data portion then contains a subsystem-specific message that may be further nested.
Netlink socket families
The family offers multiple protocol subsets. Each interfaces to a different kernel component and has a different messaging subset. The subset is referenced by the protocol field in the socket call: int socket Lacking a standard, and are not guaranteed to be implemented in a given Linux release. Some sources state that both options are legitimate, and the reference below from Red Hat states that is always the parameter. However, iproute2 uses both interchangeably.
Netlink protocols
A non-exhaustive list of the supported protocol entries follows: ; NETLINK_ROUTE provides routing and link information. This information is used primarily for user-space routing daemons. Linux implements a large subset of messages:
Link layer: RTM_NEWLINK, RTM_DELLINK, RTM_GETLINK, RTM_SETLINK
; NETLINK_FIREWALL provides an interface for a user-space app to receive packets from the firewall. ; NETLINK_NFLOG provides an interface used to communicate between Netfilter and iptables. ; NETLINK_ARPD provides an interface to manage the ARP table from user-space. ; NETLINK_AUDIT provides an interface to the audit subsystem found in Linux kernel versions 2.6.6 and later. ; NETLINK_IP6_FW provides an interface to transport packets from netfilter to user-space. ; NETLINK_ROUTE6 ; NETLINK_TAPBASE ; NETLINK_NETFILTER ; NETLINK_TCPDIAG ; NETLINK_XFRM provides an interface to manage the IPsecsecurity association and security policy databases - mostly used by key-manager daemons using the Internet Key Exchange protocol. ; NETLINK_KOBJECT_UEVENT provides the interface in which the kernel broadcasts uevents, typically consumed by udev. ; NETLINK_GENERIC One of the drawbacks of the Netlink protocol is that the number of protocol families is limited to 32.This is one of the main reasons that the generic Netlink family was created—to provide support for adding a higher number of families. It acts as a Netlink multiplexer and works with a single Netlink family. The generic Netlink protocol is based on the Netlink protocol and uses its API.
User-defined Netlink protocol
Users can add a Netlink handler in their own kernel routines. This allows the development of additional Netlink protocols to address new kernel modules.
