Previous versions of SSH.NET did not wait for the forwarded ports to stop.
In the latest beta we attempt to do a clean stop which might mean waiting for the server to signal EOF or close the channel.
Should a forwarded port not stop normally within Connection.Timeout, then we'll just continue on.
Try subscribing to the ForwardedPort.Exception event to find out if any exceptions occur in the forwarded ports.
Note that you also no longer have to explicitly stop the forwarded ports.
This is done automatically when disconnecting or disposing the SshClient.
In the latest beta we attempt to do a clean stop which might mean waiting for the server to signal EOF or close the channel.
Should a forwarded port not stop normally within Connection.Timeout, then we'll just continue on.
Try subscribing to the ForwardedPort.Exception event to find out if any exceptions occur in the forwarded ports.
Note that you also no longer have to explicitly stop the forwarded ports.
This is done automatically when disconnecting or disposing the SshClient.