channel.onError with 'No route to host' but other channels are also disconnected

Discussion of open issues, suggestions and bugs regarding network security and data protection solution - SecureBridge
Post Reply
ml@sen
Posts: 1
Joined: Mon 13 Aug 2012 13:05

channel.onError with 'No route to host' but other channels are also disconnected

Post by ml@sen » Wed 15 Aug 2012 12:11

Hi,

i'm open multiple channels with port forwarding on one SSHClient connection.
All channels are configured like
GatewayPorts:=True;
Remote=Direct=NonBlocking:=False;
SourcePort:=9933;
DestinationPort:=9922;
DestionationHost:=myIP[n]; //each channel has it's own ip destionation

Connecting of all the channels is fine.
One channel point to an non existing ip.
If i try to use the channel to establish a socket connection the OnError is raised:
TSSHDm.chOnError : Error on channel. Error: No route to host
All other channels are disonnected and also the socket connections.
The SSHClient.AfterDisconnect is called.

But it looks like the channels are in connected=True state but reestablishing the socket connections fails.

Questions:
Is there any possibility to handle the error of one channel independent of all other channels? The fail of one channel/socket on that channel does not lead to a disconnect of the other channels/socket connections.

Is it normal that a SSHClient.AfterDisonnect event was raised channels.connected propertie is still true?

Thanks,
Mats

AndreyZ

Re: channel.onError with 'No route to host' but other channels are also disconnected

Post by AndreyZ » Fri 17 Aug 2012 08:33

Hello,

Most probable, the connection is broken by the SSH server. That's why all channels and sockets are closed and the SSHClient.AfterDisconnect event is called. This is the behaviour of your SSH server. You can check this by using any other SSH client (like Putty).

Post Reply