Rico Huijbers wrote:
> I am having a problem accessing an SVN repository that is located behind
> a NAT router, and I was wondering about the cause.
>
> The situation:
> --------------
> I have a SVN repository on a box that is located behind a NAT router. I
> use svn+ssh authentication. On the LAN, everything works fine. For
> access outside the LAN, I have forwarded port 2223 on the router to port
> 22 on the box with the repository. This works fine for regular SSH shells.
>
> The problem:
> ------------
> However, I have problems accessing the box with TortoiseSVN. The problem
> seems to lie in the fact that the port is non-standard. I remember
> reading somewhere that I can specify port numbers in the SVN URI (can't
> find a link right now, but it probably was the Subversion
> documentation), so I tried a URI like:
>
> svn+ssh://user@router:2223/path/to/repos
That would work for svn:// urls, but it won't work for svn+ssh:// url.
You have to understand here the difference between those two. The svn://
access is handled by Subversion, but the svn+ssh:// access is handled by
your ssh setup. And that doesn't understand port numbers in the URI. You
have to change your SSH setup and tell that the port it should use.
> I can fix this by specifying the port to use to Plink (-P 2223), but
> that's a suboptimal solution. If I wanted to access repositories other
> than my own, I would repeatedly have to remove and add the extra
> parameters. I would prefer getting the URI solution to work, since it is
> much more elegant.
As you've figured out already, you have to change the settings in Plink.
And I'm sorry, but that's the only way to handle this kind of situation.
> The question:
> -------------
> What is the cause of this problem? Is it simply that the port number
> specification is not implemented in TortoiseSVN? Or am I doing something
> wrong? And if it is an implementation issue, will it get implemented
> someday?
It's not an implementation issue of TSVN or Subversion. Once you use
SSH, the only thing Subversion is responsible for is the data sent and
received. _How_ that data is transferred is completely up to the SSH
setup. Subversion has no way to interfere with that.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Oct 16 18:19:57 2004