Handling of network namespace IDs

Andreas Fett andreas.fett at secunet.com
Mon May 15 08:30:49 PDT 2017


Hi list,

There is a socket option NETLINK_LISTEN_ALL_NSID which can be set on a
listening netlink socket to receive events from other network namespaces
than the current one (ie /proc/self/ns/net).

For this to work the other namespace(s) must be known by a network
namespace id, which is a separate entity from the file descriptor that
is used to enter that namespace.

The ID can therefore only be used for a limited set of operations, most
notably the monitoring of events as mentioned above. In addition there
are messages to resolve a file descriptor to such an id and and to add
an id given the file descriptor for a namespace.

My Questions are:
* Is there any ongoing work to integrate this into libnl?
* Would there be interest to integrate this if I could provide patches?
* How would an API to integrate this look like?

Thanks,
Andreas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/libnl/attachments/20170515/c4f1ef49/attachment.sig>


More information about the libnl mailing list