Hello,
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
When I do this, I always get connected to the router itself, and not
forwarded to the repository (It took me a while to figure out that was
what was happening, because it appeared like an authentication issue).
It seems like the port specification is simply ignored.
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.
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?
Any insight would be greatly appreciated.
Kind regards,
Rico Huijbers
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Oct 14 21:13:21 2004