You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run the following example, I see that instances of nc (netcat) continue to run on the bastion server after the connection has been closed. If I run this example multiple times, then many instances of nc continue to run.
While this issue should be fixed, I do also see that I can avoid it entirely if I specify hoppingTool: 'native' as a config option. I was hoping you would explain why native is not the default option and what the tradeoffs are between these approaches. Thanks!
When I run the following example, I see that instances of
nc
(netcat) continue to run on the bastion server after the connection has been closed. If I run this example multiple times, then many instances ofnc
continue to run.While this issue should be fixed, I do also see that I can avoid it entirely if I specify
hoppingTool: 'native'
as a config option. I was hoping you would explain whynative
is not the default option and what the tradeoffs are between these approaches. Thanks!The text was updated successfully, but these errors were encountered: