If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since september. Please use hippie2000@webnmail.de instead.
Netlink-Sockets
| BoxMatrix >> System >> Netlink-Sockets | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Gallery |
| Devices | Filesystems | Partitions | Sockets | Netlink | Pipes | Interfaces | Bridges | Ports | Events | Sources | Sinks | AVMIPC | Processes | Watchdogs | Memory | Slab | Vmalloc | ProcFS | SysFS | Research |
 |
Netlink sockets are similar to Linux-Sockets just they are not files in the filesystem so they don't have names. They only could be identified by the PID of the owner process, which is 0 for <kernel> internal sockets. Linux-Sockets rely on a running filessystem so they are used for communication between userspace processes. Netlink sockets don't have any dependency to devices, filesystems or network stacks, so they work at any time and could be used in kernel and userspace and between both.
Netlink sockets are grouped into protocol families for different purposes, which have names and could be listed here. For the dependencies the name of the owner process PID could be gathered for sockets of each family. This is not safe since these PIDs need to be unique and only the first socket created by a process can inherit its PID, further sockets of the same process get random unique IDs. These unresolvable dependencies are marked While Linux-Sockets can only unicast (one socket at each end) netlink sockets can additionally multicast. This is handled by a bitmask of up to 32 multicasting groups per family, each bit representing one group. |
Netlink-Sockets[edit]
Goto: Netlink-Families - Netlink-Groups - FRITZ!OS - TODO
Netlink-Families[edit]
Daily updated index of all netlink families found scanning Supportdata2 probes. Last update: 2022-08-16 05:19 GMT.
The label (netlink) in the Netlink-Family column shows there are other objects in this wiki using this name.
The Mod column shows the amount of models using the respective family. Click the column header to sort by this number.
This list only covers netlink families found in FRITZ!OS *so far*. This list may grow with more Supportdata2 probes.
| Netlink-Family | Mod | Firmware | Description | Processes | Groups | Type | Origin |
|---|---|---|---|---|---|---|---|
| NETLINK_AUDIT | 5 | 7.29 - 7.39 | Kernel part of the Linux Audit Subsystem (#9) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_CRYPTO | 5 | 6.88 - 7.39 | Send configuration to or request ciphers from the Kernel Crypto API (#21) | <kernel> (0x0), wland (0x1) | 0x0, 0x1 | Family | Linux |
| NETLINK_DM | 5 | 7.01 - 7.39 | Events from the Linux Device-Mapper Framework (#17) | <kernel> (0x0), dispatcher (0x0), wland (0x1) | 0x0, 0x1 | Family | Linux |
| NETLINK_ECRYPTFS | 5 | 6.88 - 7.39 | Enterprise Cryptographic Filesystem file open events (#19) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_FAMILY_24 | 4 | 7.01 - 7.39 | TODO (#24) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_FAMILY_28 | 1 | 7.29 | TODO (#28) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_FAMILY_29 | 4 | 7.01 - 7.39 | TODO (#29) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_FAMILY_31 | 4 | 7.01 - 7.39 | TODO (#31) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_FIB_LOOKUP | 8 | 4.72 - 7.39 | Kernel Forwarding Information Base (FIB) lookup (#10) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_FIREWALL | 1 | 4.72 | Transport IPv4 packets from netfilter to user space (#3) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_GENERIC | 7 | 6.88 - 7.39 | Generic Netlink (genetlink) family for simplified netlink usage (#16) | <kernel> (0x0), <unknown> (0x8000), <unknown> (0x8004), <unknown> (0x8008), <unknown> (0xFFFFFFFF), ctlmgr (0x8004), ctlmgr (0x8008), ctlmgr (0xFFFFFFFF), l2tpv3d (0x8000), multid (0x8004), multid (0x8008), multid (0xFFFFFFFF), nltest (0x8000), pcpd (0x8004), pcpd (0x8008), pcpd (0xFFFFFFFF) | 0x0, 0x8000, 0x8004, 0x8008, 0xFFFFFFFF | Family | Linux |
| NETLINK_KOBJECT_UEVENT | 8 | 4.72 - 7.39 | Kernel messages to userspace (#15) | <kernel> (0x0), <unknown> (0x0), <unknown> (0x1), udevd (0x0), udevd (0x1) | 0x0, 0x1 | Family | Linux |
| NETLINK_RDMA | 1 | 7.29 | Infiniband Remote Direct Memory Access (RDMA) packets (#20) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_ROUTE | 8 | 4.72 - 7.39 | Communication channel between routing dæmons and the kernel packet forwarding (#0) | <kernel> (0x0), <unknown> (0x1), <unknown> (0x440), <unknown> (0x551), <unknown> (0x55b), aha (0x551), avmnexusd (0x55b), cableinfo (0x55b), ctlmgr (0x551), ctlmgr (0x55b), ddnsd (0x55b), deviceinfod (0x55b), dsld (0x551), dsld (0x55b), hostapd (0x1), igdd (0x551), l2tpv3d (0x55b), multid (0x200055f), multid (0x551), multid (0x55b), nltest (0x55b), pcpd (0x551), pcpd (0x55b), psetd (0x55b), pumaglued (0x55b), upnpd (0x551), upnpd (0x55b), voipd (0x551), voipd (0x55b), vpnd (0x55b), wland (0x1), wland (0x3), wsdd (0x55b) | 0x0, 0x1, 0x200055f, 0x3, 0x440, 0x551, 0x55b | Family | Linux |
| NETLINK_SMC | 3 | 7.29 - 7.39 | Monitoring of Shared Memory Communications over RDMA (SMC-R) and RoCE (#22) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_SOCK_DIAG | 2 | 6.88 - 7.29 | Query information about sockets of various protocol families (#4) | <kernel> (0x0) | 0x0 | Family | Linux |
| NETLINK_USERSOCK | 4 | 6.88 - 7.39 | User mode socket protocols (#2) | <kernel> (0x0), oamd (0x0) | 0x0 | Family | Linux |
| NETLINK_XFRM | 2 | 7.29 - 7.39 | Packet Transform (IPsec) (#6) | <kernel> (0x0) | 0x0 | Family | Linux |
| 18 netlink families | |||||||
Netlink-Groups[edit]
This is researchh in progress and not finished yet - rtnetkink / NETLINK_ROUTE is finished,
Daily updated index of all multicasting groups found scanning Supportdata2 probes. Last update: 2022-08-16 05:19 GMT.
The label (nlgroup) in the Netlink-Group column shows there are other objects in this wiki using this name.
The Mod column shows the amount of models using the respective group. Click the column header to sort by this number.
This list only covers netlink groups found in FRITZ!OS *so far*. This list may grow with more Supportdata2 probes.
FRITZ!OS[edit]
libnl[edit]
In fw 7.14 AVM started to add the libnl-3.so netlink socket API suite to FRITZ!OS.
It includes a set or libraries to handle different socket families, and is mainly used by third party commands.
- libnl-3.so - Netlink Core API
- libnl-cli-3.so - Command Line Interface API
- libnl-genl-3.so - Generic Netlink - NETLINK_GENERIC
- libnl-idiag-3.so - Inet / Sock Diag - NETLINK_SOCK_DIAG
- libnl-nf-3.so - Netfilter - NETLINK_NETFILTER
- libnl-route-3.so - Routing Family - NETLINK_ROUTE
- libnl-xfrm-3.so - Packet Transform (IPsec) - NETLINK_XFRM
See also the Netlink Protocol Library Suite (libnl) docs.
TODO[edit]
Find more details about:
