title: Subversion through a tunnel
body: <p>For work, I work in a closed network. There are a few IP addresses that we have set up that are only accessible from inside our network. There is one box, though, that we can SSH into and tunnel through to get to our respective developer boxes.</p>
  
  <p>I know I can get traffic from our developer box by using the <code>-L</code> argument of ssh. I was wondering if there was a way I could tunnel through our open box, to get into a closed box were our Subversion (SVN) repository is stored?</p>
  
  <pre><code>My computer --&gt; Open box --&gt; Developer boxes/SVN repository
  </code></pre>
  
  <p>I can't ssh into the SVN box, but is there a way to use ssh like a proxy to get access to the private Subversion box?</p>
  
  <p><strong>UPDATE:</strong></p>
  
  <p>1.1.1.1 -> Open Box
  1.1.1.2 -> SVN Box</p>
  
  <p>I can SSH into the SVN box after I tunnel through the open box:</p>
  
  <pre><code>ssh user1@1.1.1.1
  ssh user2@1.1.1.2
  </code></pre>
  
  <p>This will allow me access to the SVN box. I figure, ssh into open box, local forward port 22 of SVN box to my port 22. Thus</p>
  
  <pre><code>ssh user1@1.1.1.1 -L 22:1.1.1.2:22
  </code></pre>
  
  <p>Then using SVN in command line: </p>
  
  <pre><code>svn co svn+ssh://user2@localhost/path
  </code></pre>
  
  <p>This returns </p>
  
  <blockquote>
    <p>svn: Network connection closed unexpectedly</p>
  </blockquote>
  
  <p>Why is this happening? Does svn+ssh use another port that I am not aware of?</p>