You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Goldstein Lyor (JIRA)" <ji...@apache.org> on 2018/07/22 15:48:00 UTC

[jira] [Resolved] (SSHD-834) Missing configurable source bind address in connect method of org.apache.sshd.clientSshClient

     [ https://issues.apache.org/jira/browse/SSHD-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Goldstein Lyor resolved SSHD-834.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.1

Already in:
{code:java}
ConnectFuture connect(String username, SocketAddress targetAddress, SocketAddress localAddress) throws IOException
{code}
Note that the local address is the 2nd argument and not as the issue implies

> Missing configurable source bind address in connect method of org.apache.sshd.clientSshClient
> ---------------------------------------------------------------------------------------------
>
>                 Key: SSHD-834
>                 URL: https://issues.apache.org/jira/browse/SSHD-834
>             Project: MINA SSHD
>          Issue Type: Improvement
>    Affects Versions: 1.7.0
>            Reporter: Roberto Deandrea
>            Priority: Major
>             Fix For: 2.0.1
>
>
> On multi homed machines (2+ network interfaces) it could be very useful to be able to set the source bind address of the originating connection for SshClient(s) connecting to remote SSH servers.
> If not set explicitly, the source bind address is chosen between one of the available addresses on the machine.
> Sometimes firewalls block/reject  TCP connections originating from particular ip addresses but with this new parameter this issue could be bypassed.
> Is it possible to add and implement the following method in the ClientSessionCreator interface ?
> ConnectFuture connect(String username, SocketAddress local, SocketAddress remote) throws IOException;
> The new parameter "local" represents the local source bind address.
>  
> Bye.
> Roberto
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)