-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to create Connection from existing socket #18
Comments
a1ien
changed the title
Add ability to crate Connection from existing socket
Add ability to create Connection from existing socket
Sep 28, 2023
MaxHearnden
added a commit
to MaxHearnden/netlink-proto
that referenced
this issue
Nov 17, 2024
This is useful when dealing with multiple network/user namespaces. Closes rust-netlink#18
MaxHearnden
added a commit
to MaxHearnden/netlink-proto
that referenced
this issue
Nov 17, 2024
This is useful when dealing with multiple network/user namespaces. Closes rust-netlink#18
MaxHearnden
added a commit
to MaxHearnden/netlink-proto
that referenced
this issue
Nov 17, 2024
This is useful when dealing with multiple network/user namespaces. Closes rust-netlink#18
MaxHearnden
added a commit
to MaxHearnden/netlink-proto
that referenced
this issue
Nov 20, 2024
This is useful when dealing with multiple network/user namespaces. Closes rust-netlink#18
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This will be useful for example if we create socket in another process and use technique like snedmsg to pass socket descriptor between process.
The expected Api probably like
new_connection_from_socket<S>(socket: S) where S: sys::AsyncSocket
...What you think about this idea?
The use case for this feature. We have application that live in different namespace. And we can create netlink socket in different namespace and pass created socket to another application.
The text was updated successfully, but these errors were encountered: