-
Notifications
You must be signed in to change notification settings - Fork 721
portfwd: support HostSocket
#4008
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
portfwd: support HostSocket
#4008
Conversation
277bbce to
141e02e
Compare
64a2088 to
991e95f
Compare
|
Dropped closing |
991e95f to
935aa20
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, can we cover this in test-port-forwarding ?
935aa20 to
e7a9d6b
Compare
|
added a test to |
bedf7de to
7ef6404
Compare
|
I give up on making hostSocket tests pass on Windows, since I don't have any Windows environments for debugging. |
|
Afaik there is no AF_UNIX interop between WSL2 and Windows; it only worked for WSL, but has never been implemented for WSL2. |
8c60f68 to
5ec1a53
Compare
b80fe85 to
37c46c8
Compare
Signed-off-by: Norio Nomura <[email protected]> portfwd: remove "unixgram" forwarding code because that does not work Signed-off-by: Norio Nomura <[email protected]> portfwd: do not use `listenConfig` param on Unix domain sockets Signed-off-by: Norio Nomura <[email protected]>
Signed-off-by: Norio Nomura <[email protected]> hack/test-port-forwarding.pl: use platform-independent path on hostSocket Signed-off-by: Norio Nomura <[email protected]> hack/test-port-forwarding.pl: Skip hostSocket test on Windows host Signed-off-by: Norio Nomura <[email protected]>
37c46c8 to
ef88218
Compare
I didn’t give up, even though I said I had. But this time, I truly gave up. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
|
With the introduction of ssh-over-vsock, which port forwarder works best for host sockets? |
|
Thanks! 🙏🏻
If it's just the transfer speed, the port forwarder by SSH over VSOCK was fast, but the stability is still unknown. If the cause of the gRPC forwarder's issue is caused by VSOCK, which is the transporting path, SSH over VSOCK may be affected in the same way. |
| "github.com/sirupsen/logrus" | ||
| ) | ||
|
|
||
| func Listen(ctx context.Context, listenConfig net.ListenConfig, hostAddress string) (net.Listener, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The function seems called only from forwardTCP()?
How does this function work with unix sockets?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GRPC port forwarder does not support guest-side Unix sockets.
forwardTCP()'s TCP indicates "guest side is TCP".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, got it
Add missing
hostSocketsupport to GRPC port forwarder.HostPortRangeifHostSocketis used.edit: dropped closing
ClosableListenerson exit