Libnetstack - revision history

Dank: /* rtnetlink */

2021-11-05T20:18:48Z

rtnetlink

← Older revision		Revision as of 20:18, 5 November 2021
Line 4:		Line 4:

	==rtnetlink==		==rtnetlink==
	<tt>rtnetlink(7)</tt> (originally implemented AFAIK by Alexey Kuznetsov, the Mad Russian, whom I haven't seen post to [[LKML]] in many years, and miss) provides the <tt>NETLINK_ROUTE</tt> protocol for the <tt>AF_NETLINK</tt> family of sockets. According to <tt>netlink(7)</tt>,<blockquote>Netlink is a datagram-oriented service. Both <tt>SOCK_RAW</tt> and <tt>SOCK_DGRAM</tt> are valid values for socket_type. However, the netlink protocol does not distinguish between datagram and raw sockets."—<tt>netlink(7)</tt>, Linux man pages 5.03</blockquote> Creating and using such a socket does not require any special permissions, though <tt>CAP_NET_ADMIN</tt> is needed for many control messages (verified kernel-side, of course). Once established,		<tt>rtnetlink(7)</tt> (originally implemented AFAIK by Alexey Kuznetsov, the Mad Russian, whom I haven't seen post to [[LKML]] in many years, and miss) provides the <tt>NETLINK_ROUTE</tt> protocol for the <tt>AF_NETLINK</tt> family of sockets. According to <tt>netlink(7)</tt>,<blockquote>Netlink is a datagram-oriented service. Both <tt>SOCK_RAW</tt> and <tt>SOCK_DGRAM</tt> are valid values for socket_type. However, the netlink protocol does not distinguish between datagram and raw sockets."—<tt>netlink(7)</tt>, Linux man pages 5.03</blockquote> Creating and using such a socket does not require any special permissions, though <tt>CAP_NET_ADMIN</tt> is needed for many control messages (verified kernel-side, of course). Once established, we can directly request dumps of networking stack state with the <tt>RTM_GET*</tt> set of messages, and/or simply subscribe to the appropriate multicast groups, sit back, and let new events roll to us.
	We can directly request dumps of networking stack state with the <tt>RTM_GET*</tt> set of messages, and/or simply subscribe to the appropriate multicast groups, sit back, and let new events roll to us.

	{\|class="wikitable"		{\|class="wikitable"

Dank at 22:24, 4 November 2019

2019-11-04T22:24:05Z

@@ Line 4: / Line 4: @@
 ==rtnetlink==
-<tt>rtnetlink(7)</tt> (originally implemented AFAIK by Alexey Kuznetsov, the Mad Russian, whom I haven't seen post to [[LKML]] in many years, and miss) provides the <tt>NETLINK_ROUTE</tt> protocol for the <tt>AF_NETLINK</tt> family of sockets. According to <tt>netlink(7)</tt>,<blockquote>Netlink  is  a datagram-oriented service. Both <tt>SOCK_RAW</tt> and <tt>SOCK_DGRAM</tt> are valid values for socket_type. However, the netlink  protocol  does not distinguish between datagram and raw sockets."—<tt>netlink(7)</tt>, Linux man pages 5.03</blockquote> Creating and using such a socket does not require any special permissions, though <tt>CAP_NET_ADMIN</tt> is needed for many control messages (verified kernel-side, of course).
+<tt>rtnetlink(7)</tt> (originally implemented AFAIK by Alexey Kuznetsov, the Mad Russian, whom I haven't seen post to [[LKML]] in many years, and miss) provides the <tt>NETLINK_ROUTE</tt> protocol for the <tt>AF_NETLINK</tt> family of sockets. According to <tt>netlink(7)</tt>,<blockquote>Netlink  is  a datagram-oriented service. Both <tt>SOCK_RAW</tt> and <tt>SOCK_DGRAM</tt> are valid values for socket_type. However, the netlink  protocol  does not distinguish between datagram and raw sockets."—<tt>netlink(7)</tt>, Linux man pages 5.03</blockquote> Creating and using such a socket does not require any special permissions, though <tt>CAP_NET_ADMIN</tt> is needed for many control messages (verified kernel-side, of course). Once established,
 {{#github:README.md|dankamongmen/libnetstack}}

Dank at 22:07, 4 November 2019

2019-11-04T22:07:50Z

← Older revision		Revision as of 22:07, 4 November 2019
Line 3:		Line 3:
	Code lives at https://github.com/dankamongmen/libnetstack.		Code lives at https://github.com/dankamongmen/libnetstack.

	{{#github:README.md\|dankamongmen/libnetstack}}.		==rtnetlink==
			<tt>rtnetlink(7)</tt> (originally implemented AFAIK by Alexey Kuznetsov, the Mad Russian, whom I haven't seen post to [[LKML]] in many years, and miss) provides the <tt>NETLINK_ROUTE</tt> protocol for the <tt>AF_NETLINK</tt> family of sockets. According to <tt>netlink(7)</tt>,<blockquote>Netlink is a datagram-oriented service. Both <tt>SOCK_RAW</tt> and <tt>SOCK_DGRAM</tt> are valid values for socket_type. However, the netlink protocol does not distinguish between datagram and raw sockets."—<tt>netlink(7)</tt>, Linux man pages 5.03</blockquote> Creating and using such a socket does not require any special permissions, though <tt>CAP_NET_ADMIN</tt> is needed for many control messages (verified kernel-side, of course).


			{{#github:README.md\|dankamongmen/libnetstack}}

			==See also==
			* "[https://inai.de/documents/Netlink_Protocol.pdf The Netlink protocol: Mysteries Uncovered]", Jan Engelhardt 2010-10-30

	[[CATEGORY: Projects]]		[[CATEGORY: Projects]]

Dank at 23:09, 1 November 2019

2019-11-01T23:09:45Z

← Older revision		Revision as of 23:09, 1 November 2019
Line 2:		Line 2:

	Code lives at https://github.com/dankamongmen/libnetstack.		Code lives at https://github.com/dankamongmen/libnetstack.

			{{#github:README.md\|dankamongmen/libnetstack}}.

	[[CATEGORY: Projects]]		[[CATEGORY: Projects]]

Dank: Created page with "`AF_NETLINK` sockets allow one to enumerate networking stack elements, and subscribe to events regarding changes, additions, and deletions thereof. Netlink is kind..."

2019-11-01T16:59:56Z

Created page with "<tt>AF_NETLINK</tt> sockets allow one to enumerate networking stack elements, and subscribe to events regarding changes, additions, and deletions thereof. Netlink is kind..."

New page

<tt>AF_NETLINK</tt> sockets allow one to enumerate networking stack elements, and subscribe to events regarding changes, additions, and deletions thereof. [[Netlink]] is kind of a pain in the ass to work with directly, though. My [https://github.com/dankamongmen/libnetstack libnetlink] enumerates all existing networking stack elements, subscribes to events, and makes all of this available to the user via queries and/or realtime callbacks. libnetstack has been designed to provide responsive service even in the presence of millions of routes with rapid churning of the route tables.

Code lives at https://github.com/dankamongmen/libnetstack.

[[CATEGORY: Projects]]

Libnetstack - revision history

Dank: /* rtnetlink */

Dank at 22:24, 4 November 2019

Dank at 22:07, 4 November 2019

Dank at 23:09, 1 November 2019

Dank: Created page with "AF_NETLINK sockets allow one to enumerate networking stack elements, and subscribe to events regarding changes, additions, and deletions thereof. Netlink is kind..."

Dank: Created page with "`AF_NETLINK` sockets allow one to enumerate networking stack elements, and subscribe to events regarding changes, additions, and deletions thereof. Netlink is kind..."