FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F13.3 2023-01-26T15:50:25Z 2023-01-26T15:50:25Z Alexander V. Chernikov melifaro@FreeBSD.org 2022-12-22T14:51:36Z urn:sha1:efbf827ae461a66402acb191c036623ce1ee608f Differential Revision: https://reviews.freebsd.org/D37781 (cherry picked from commit c9313a0bad682351858e2e326cdb0f1d0bc2d1d8) 2023-01-26T15:30:25Z Gleb Smirnoff glebius@FreeBSD.org 2022-10-04T21:38:40Z urn:sha1:cbd59dcec727fc73fc49e5df1e97c303a652b03f (cherry picked from commit a87d2d1830933b81caaf30a67a4bef0a253ecd0b) 2023-01-23T19:18:08Z Alexander V. Chernikov melifaro@FreeBSD.org 2022-01-20T21:39:21Z urn:sha1:6bbfbaa6ae46f732603c2a23c7ece6dfe39c1e03 Netlinks is a communication protocol currently used in Linux kernel to modify, read and subscribe for nearly all networking state. Interfaces, addresses, routes, firewall, fibs, vnets, etc are controlled via netlink. It is async, TLV-based protocol, providing 1-1 and 1-many communications. The current implementation supports the subset of NETLINK_ROUTE family. To be more specific, the following is supported: * Dumps: - routes - nexthops / nexthop groups - interfaces - interface addresses - neighbors (arp/ndp) * Notifications: - interface arrival/departure - interface address arrival/departure - route addition/deletion * Modifications: - adding/deleting routes - adding/deleting nexthops/nexthops groups - adding/deleting neghbors - adding/deleting interfaces (basic support only) * Rtsock interaction - route events are bridged both ways The implementation also supports the NETLINK_GENERIC family framework. Implementation notes: Netlink is implemented via loadable/unloadable kernel module, not touching many kernel parts. Each netlink socket uses dedicated taskqueue to support async operations that can sleep, such as interface creation. All message processing is performed within these taskqueues. Compatibility: Most of the Netlink data models specified above maps to FreeBSD concepts nicely. Unmodified ip(8) binary correctly works with interfaces, addresses, routes, nexthops and nexthop groups. Some software such as net/bird require header-only modifications to compile and work with FreeBSD netlink. Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D36002 MFC after: 2 months (cherry picked from commit 7e5bf68495cc0a8c9793a338a8a02009a7f6dbb6)