Remove the "shutdown" protocol used for forwarding ports over Hyper-V sockets #418
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously we used a custom protocol on top of Hyper-V sockets because they didn't support
shutdown
. With modern Windows and modern Linux theshutdown
works (at least when the connections are initiated from the host) and therefore the Golinuxkit/virtsock
library has dropped the custom protocol. Since we're talking tovpnkit-forwarder
usinglinuxkit/virtsock
we must drop the custom protocol too.This uses an experimental version of
mirage/ocaml-hvsock
with support for syscall-basedshutdown
.