netlink: move NETLINK define to opt_global.hMove the NETLINK define into opt_global.h so we can rely on it beingset correctly, without having to remember to include opt_netlink.h.This ensures tha
netlink: move NETLINK define to opt_global.hMove the NETLINK define into opt_global.h so we can rely on it beingset correctly, without having to remember to include opt_netlink.h.This ensures that the NETLINK define is correctly set. If not wemay end up with unloadable modules, due to missing symbols (such asnlmsg_get_group_writer).PR: 274306Reviewed by: imp, markjMFC after: 3 daysDifferential Revision: https://reviews.freebsd.org/D42179(cherry picked from commit ab393e9548f8cc0ee28499c411963b798ebb38a5)
show more ...
netlink: add netlink KPI to the kernel by defaultThis change does the following:Base Netlink KPIs (ability to register the family, parse and/or write a Netlink message) are always present in the
netlink: add netlink KPI to the kernel by defaultThis change does the following:Base Netlink KPIs (ability to register the family, parse and/or write a Netlink message) are always present in the kernel. Specifically,* Implementation of genetlink family/group registration/removal, some base accessors (netlink_generic_kpi.c, 260 LoC) are compiled in unconditionally.* Basic TLV parser functions (netlink_message_parser.c, 507 LoC) are compiled in unconditionally.* Glue functions (netlink<>rtsock), malloc/core sysctl definitions (netlink_glue.c, 259 LoC) are compiled in unconditionally.* The rest of the KPI _functions_ are defined in the netlink_glue.c, but their implementation calls a pointer to either the stub function or the actual function, depending on whether the module is loaded or not.This approach allows to have only 1k LoC out of ~3.7k LoC (current sys/netlink implementation) in the kernel, which will not grow further.It also allows for the generic netlink kernel customers to load successfully without requiring Netlink module and operate correctly once Netlink module is loaded.Reviewed by: impMFC after: 2 weeksDifferential Revision: https://reviews.freebsd.org/D39269
netlink: allow netlink to be build in the kernelDifferential Revision: https://reviews.freebsd.org/D37781
netlink: fix standalone module build
netlink: add netlink supportNetlinks is a communication protocol currently used in Linux kernel to modify, read and subscribe for nearly all networking state. Interfaces, addresses, routes, firew
netlink: add netlink supportNetlinks 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_ROUTEfamily. 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 waysThe 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 withinterfaces, addresses, routes, nexthops and nexthop groups. Somesoftware such as net/bird require header-only modifications to compileand work with FreeBSD netlink.Reviewed by: impDifferential Revision: https://reviews.freebsd.org/D36002MFC after: 2 months