sshsubversiontcp
I have configured SSH to be on port 20000. When I try:
svn co svn+ssh://server.com:20000/home/svn/proj1 proj1 --username jm
I get
svn: To better debug SSH connection problems, remove the -q option
from 'ssh' in the [tunnels] section of your Subversion configuration
file. svn: Network connection closed unexpectedly
I think I need to tell SVN to use port 20000 also?
I am on Ubuntu 11.10
Conditions of the message
According this part of the OpenSSH portable source code, two conditions are needed to print this message:
Solution to suppress the message
-o LogLevel=QUIET to your ssh command line.LogLevel QUIET under relevant Host blocks.For example, I use this line in a sh script connecting to several servers to run Docker commands, some potentially interactive:
SSH = "ssh -t -o LogLevel=QUIET"
Warning: any error is discarded
A drawback of this method is this also suppresses SSH fatal errors.
$ ssh -t -o LogLevel=QUIET notexisting.notld ssh anotherone.notld
$
Alternative: log stderr output instead of printing it
If stderr is still considered important to get, an alternative is to redirect stderr to syslog instead, with ssh -t -y (but then you'd flood your log with all those Shared connection to <host> closed messages).
It looks like you should be using local port-forwarding instead of remote port-forwarding. You may want to refer to the following helpful blog post by Dirk Loss:
It includes the following illustrative diagram:
In order to read the diagram you need to know that it describes the relationships between 4 different roles involved in creating and utilizing an SSH tunnel:
ssh - the OpenSSH command-line client) used to establish the tunnel;sshd - the OpenSSH server daemon) used to maintain the other end of the tunnel;It's also important to understand that the two different types of forwarding correspond to two different use cases:
Local Forwarding: where the application client connects via the ssh client
Remote Forwarding: where the application client connects via the ssh server
Remote forwarding is so called because the forwarding is performed remotely (at the ssh server) rather than locally (at the ssh client). I also find "remote forwarding = reverse forwarding" to be a useful mnemonic.
So as you can see, in order to initiate a connection from an ssh client at the origin host through an sshd server on a proxy jumphost to a third target host you would have to use local port-forwarding. Remote port-forwarding is for the case in which you want the entry point to the tunnel to be located at the host running the sshd server rather than at the host running the ssh client.
In the man page the local port-forwarding syntax is written as follows:
ssh -L [bind_address:]port:host:hostport user@remote
This can be written more intuitively as the following:
ssh -L [local_bind_address:]local_port:remote_host:remote_host_port user@proxy_host
Or, using your naming conventions:
ssh -L [origin_bind_address:]origin_port:target_host:target_host_port user@jump_host
If we modify your command to use local port-forwarding instead then we end up with the following:
user@origin:~$ ssh -L *:1234:target:22 myusername@jumphost
Best Answer
You can define a new 'tunnel' in your Subversion configuration (
~/.subversion/config). Find the section[tunnels]there and define something like:Afterwards you can contact your repository via the URL
svn+foo://server.com/home/svn/proj1 proj1.