Skip to content

Conversation

djs55
Copy link
Collaborator

@djs55 djs55 commented Oct 6, 2018

The old protocol was needed to work around Hyper-V socket bugs, where data would be lost after a shutdown. This is no longer needed because the new multiplexing protocol doesn't call shutdown, since it multiplexes all port forwarding connections over a single connection.

This supercedes #418

Before we multiplexed all port forwards over one connection, we had
to layer our own custom shutdown protocol on top to work around
Hyper-V socket bugs. This is not needed any more because the same
work is done within the multiplexing protocol.

Note this requires an updated vpnkit-forwarder.

Signed-off-by: David Scott <[email protected]>
djs55 added 4 commits March 10, 2019 10:38
This removes the legacy shutdown protocol.

Signed-off-by: David Scott <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant