-
Notifications
You must be signed in to change notification settings - Fork 20
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
Emulate dualstack sockets in userspace #1
Comments
@badeend in your assessment, do you think this needs to be part of an MVP? Given that not all OSs support this, maybe we can punt on it and let the emulation happen entirely in userspace, even above libc? |
I suggest saying it's "nondeterministic" whether dual-stack is enabled by default or not. This effectively represents the reality most portable socket code today faces, where dual-stack support may or may not be enabled in ways that are outside the application's control or visibility. Beyond that, it'd be nice (but not necessarily critical for an MVP) to have a way to set |
@tschneidereit You're correct in that it doesn't need to be part of the MVP. It currently isn't. @sunfishcode That's certainly the most pragmatic option. Let me start by saying that I too am on the fence on this one. The things that made me swing slightly towards IPv6-only by default versus just choosing the underlying platform's default:
|
That also sounds reasonable to me. |
In #13 I've added the option to get and set the |
The underlying commercial operating systems use "prefer IPv6, fail-over to IPv4 by default". The current security best practices with many security teams is "prefer IPv4, fail-over to IPv4 by default". So how does this impact existing software? |
…off of wit-bindgen - previous ones fail (#1) Signed-off-by: danbugs <[email protected]> Signed-off-by: danbugs <[email protected]>
Dualstack support per platform according to the internet: (Not verified)
On the *BSD's: Can dualstack sockets be emulated efficiently and transparently in userspace by creating two sockets?
The text was updated successfully, but these errors were encountered: