You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Érico <er...@gmail.com> on 2006/11/16 22:03:34 UTC

accessing svn through internet

Hi everybody

I'm using svn in my office network and everything is fine

I would like to access svn from home

Searching for documentation on the web I configured permission in my 
firewall to access port 3690

so i tried : svn://myhost:3690 or  svn://myhost_ip:3690 and wasn't able 
to connect to my server

I'm searching in documentation how to configure this feature

Does any one can give me some help about this

Thanks



Re: accessing svn through internet

Posted by Andy Levy <an...@gmail.com>.
On 11/16/06, Érico <er...@gmail.com> wrote:
>
>  Ryan Schmidt wrote:
> On Nov 16, 2006, at 16:03, Érico wrote:
>
>
> I'm using svn in my office network and everything is fine
>
>  I would like to access svn from home
>
>  Searching for documentation on the web I configured permission in my
> firewall to access port 3690
>
>  so i tried : svn://myhost:3690 or  svn://myhost_ip:3690 and wasn't able to
> connect to my server
>
>  I'm searching in documentation how to configure this feature
>
>  Does any one can give me some help about this
>
>  Are you running svnserve?
>
>  You need to be, if you expect to be able to access the repository over the
> svn:// protocol.
>
>  The book explains how to set up svnserve, or the Apache server, which is
> another option.
>
>  http://svnbook.red-bean.com/en/1.2/svn.serverconfig.html
>
>
>
>
>  I'm running svn as service in a windows 2003 server

Does your office firewall allow outbound connections on that port?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


Re: accessing svn through internet

Posted by Érico <er...@gmail.com>.
Ryan Schmidt wrote:
> On Nov 16, 2006, at 16:03, Érico wrote:
>
>> I'm using svn in my office network and everything is fine
>>
>> I would like to access svn from home
>>
>> Searching for documentation on the web I configured permission in my 
>> firewall to access port 3690
>>
>> so i tried : svn://myhost:3690 or  svn://myhost_ip:3690 and wasn't 
>> able to connect to my server
>>
>> I'm searching in documentation how to configure this feature
>>
>> Does any one can give me some help about this
>
> Are you running svnserve?
>
> You need to be, if you expect to be able to access the repository over 
> the svn:// protocol.
>
> The book explains how to set up svnserve, or the Apache server, which 
> is another option.
>
> http://svnbook.red-bean.com/en/1.2/svn.serverconfig.html
>
>
>
>
I'm running svn as service in a windows 2003 server

I used a setup( Svn1ClickSetup-1.3.3.exe ) witch  already  configured 
svn as service


Re: accessing svn through internet

Posted by Geoffrey Myers <ge...@serioustechnology.com>.
Duncan Murdoch wrote:
> On 11/16/2006 6:51 PM, Ryan Schmidt wrote:
>> On Nov 16, 2006, at 16:03, Érico wrote:
>>
>>> I'm using svn in my office network and everything is fine
>>>
>>> I would like to access svn from home
>>>
>>> Searching for documentation on the web I configured permission in  my 
>>> firewall to access port 3690
>>>
>>> so i tried : svn://myhost:3690 or  svn://myhost_ip:3690 and wasn't  
>>> able to connect to my server
>>>
>>> I'm searching in documentation how to configure this feature
>>>
>>> Does any one can give me some help about this
>>
>> Are you running svnserve?
>>
>> You need to be, if you expect to be able to access the repository  
>> over the svn:// protocol.
>>
>> The book explains how to set up svnserve, or the Apache server, which  
>> is another option.
>>
>> http://svnbook.red-bean.com/en/1.2/svn.serverconfig.html
> 
> I've found it easier to set up svn+ssh access.  No server needed (except 
> the sshd server, of course, but it was running for other reasons).

And more secure, I suspect.  Unless svn is doing some encryption I'm not 
aware of.

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: accessing svn through internet

Posted by Edward Peckham <ed...@peckham.me.uk>.
Duncan Murdoch wrote:
> On 11/16/2006 6:51 PM, Ryan Schmidt wrote:
>> On Nov 16, 2006, at 16:03, Érico wrote:
>>
>>> I'm using svn in my office network and everything is fine
>>>
>>> I would like to access svn from home
>>>
>>> Searching for documentation on the web I configured permission in  
>>> my firewall to access port 3690
>>>
>>> so i tried : svn://myhost:3690 or  svn://myhost_ip:3690 and wasn't  
>>> able to connect to my server
>>>
>>> I'm searching in documentation how to configure this feature
>>>
>>> Does any one can give me some help about this
>>
>> Are you running svnserve?
>>
>> You need to be, if you expect to be able to access the repository  
>> over the svn:// protocol.
>>
>> The book explains how to set up svnserve, or the Apache server, 
>> which  is another option.
>>
>> http://svnbook.red-bean.com/en/1.2/svn.serverconfig.html
>
> I've found it easier to set up svn+ssh access.  No server needed 
> (except the sshd server, of course, but it was running for other 
> reasons).
>
Another way of using ssh, that I like, is using port forwarding:
You need to be running svnserve and sshd on the remote network for this.

On your client run

ssh -L 3690:remote_network_svn_server_ip:3690 -n username@sshd_server_name &

This will tunnel the port 3690 on your svn server machine to port 3690 
on your local machine.
If your sshd server and svnserve are on the same machine then 
remote_network_svn_server_ip
will just be localhost.
Then you can access your repository using your usual tools using the 
following url:

svn://localhost/repository_name

If you already have a working copy on your client machine that you 
checked out locally, then
you'll need to do an svn switch --relocate on it.
This port forwarding method never seems to get mentioned much, but it 
works well for me.
Does anyone else use ssh with svn in this way?

Cheers,
Edward

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: accessing svn through internet (svn+ssh)

Posted by Geoffrey Myers <ge...@serioustechnology.com>.
Robert Graf-Waczenski wrote:

> HOWEVER: My big problem is that access via svn+ssh is *substantially*
> slower than access via plain svn, even if the client computer lives
> in the same local LAN as the server. So i'm quite reluctant to tell
> remote users to use svn+ssh with such a slow performance.
> (I find this result rather embarassing given that SVN is supposed
> to behave good on slow networks... Well, this probably only tells
> me that the problem exists between keyboard and chair...)
> Others have reported this already, but those who replied only explained
> this with pointing out that windows clients tend to be a lot slower
> than linux/unix clients. Even though i sometimes enjoy to join
> M$ bashfests, this type of reply does not help much in my setup
> because i can not tell the users "go use linux instead of windows".
> So, maybe someone else has observed the same problem and/or has
> solved it and is willing to share the fix?

I don't know that you'll find a solution.  Understand that ssh is going 
to encrypt all the data, so much of your slowness could well be 
attributed to that.  You might look your client hardware.  encryption is 
going to be cpu intensive, thus upgrading hardware on both sides might 
make a difference.

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: accessing svn through internet (svn+ssh)

Posted by Duncan Murdoch <mu...@stats.uwo.ca>.
On 11/17/2006 6:04 AM, Robert Graf-Waczenski wrote:
> I'm currently also evaluating svn+ssh as method for remote access.
> 
> Our setup:
> 
> Server:
> - Windows XP 64 bit Professional
> - copSSH 1.4.1 (Windows port of OpenSSH 4.5p1 with security fix)
> - Subversion 1.4.2 32 bit
> 
> Client:
> - Windows 2000 Professional
> - TortoiseSVN 1.4.1
> - PuTTY 0.5.8 (installed together with puttygen.exe and pageant.exe)
> 
> After jumping through a few intellectual hoops in configuring the
> SSH server command that is executed on behalf of the incoming requests
> correctly, this setup worked, i.e. i was able to establish an SSH
> tunnel from the client to the server once the private key file was
> imported at the client side.
> 
> HOWEVER: My big problem is that access via svn+ssh is *substantially*
> slower than access via plain svn, even if the client computer lives
> in the same local LAN as the server. So i'm quite reluctant to tell
> remote users to use svn+ssh with such a slow performance.
> (I find this result rather embarassing given that SVN is supposed
> to behave good on slow networks... Well, this probably only tells
> me that the problem exists between keyboard and chair...)
> Others have reported this already, but those who replied only explained
> this with pointing out that windows clients tend to be a lot slower
> than linux/unix clients. Even though i sometimes enjoy to join
> M$ bashfests, this type of reply does not help much in my setup
> because i can not tell the users "go use linux instead of windows".
> So, maybe someone else has observed the same problem and/or has
> solved it and is willing to share the fix?

I can't help you to fix it, but maybe to diagnose it.  Each svn command 
usually leads to multiple ssh sessions.  If those are slow to start up, 
then svn will be slow.

You might want to run an ssh connection in debug mode, to see if it's 
trying the successful connection method first; you don't want to wait 
through failures.

Or you might investigate other ssh clients or servers, just to see if 
they establish connections faster than the combination you're using.

Duncan Murdoch

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: accessing svn through internet (svn+ssh)

Posted by Robert Graf-Waczenski <rg...@lsoft.com>.
I'm currently also evaluating svn+ssh as method for remote access.

Our setup:

Server:
- Windows XP 64 bit Professional
- copSSH 1.4.1 (Windows port of OpenSSH 4.5p1 with security fix)
- Subversion 1.4.2 32 bit

Client:
- Windows 2000 Professional
- TortoiseSVN 1.4.1
- PuTTY 0.5.8 (installed together with puttygen.exe and pageant.exe)

After jumping through a few intellectual hoops in configuring the
SSH server command that is executed on behalf of the incoming requests
correctly, this setup worked, i.e. i was able to establish an SSH
tunnel from the client to the server once the private key file was
imported at the client side.

HOWEVER: My big problem is that access via svn+ssh is *substantially*
slower than access via plain svn, even if the client computer lives
in the same local LAN as the server. So i'm quite reluctant to tell
remote users to use svn+ssh with such a slow performance.
(I find this result rather embarassing given that SVN is supposed
to behave good on slow networks... Well, this probably only tells
me that the problem exists between keyboard and chair...)
Others have reported this already, but those who replied only explained
this with pointing out that windows clients tend to be a lot slower
than linux/unix clients. Even though i sometimes enjoy to join
M$ bashfests, this type of reply does not help much in my setup
because i can not tell the users "go use linux instead of windows".
So, maybe someone else has observed the same problem and/or has
solved it and is willing to share the fix?

Robert

> -----Original Message-----
> From: Duncan Murdoch [mailto:murdoch@stats.uwo.ca]
> Sent: Freitag, 17. November 2006 11:28
> To: Thomas Harold
> Cc: users@subversion.tigris.org
> Subject: Re: accessing svn through internet (svn+ssh)
>
>
> On 11/16/2006 10:44 PM, Thomas Harold wrote:
> > Duncan Murdoch wrote:
> >> I've found it easier to set up svn+ssh access.  No server
> needed (except
> >> the sshd server, of course, but it was running for other reasons).
> >>
> >
> > I prefer the svn+ssh method as well... not sure how well it would work
> > with a Windows host though.  I guess one could use Cygwin's SSHD?
>
> I do use Cygwin's sshd for other things, and it works fine.  However, I
> don't have any svn repositories on Windows machines so I can't say for
> sure that would work:  I just can't think of any reason why it wouldn't.
>
> Duncan Murdoch
> >
> > (We waited until we could install some Linux servers before migrating
> > away from SOS+VSS.)
> >
> > The nicest part about the svn+ssh method is the use of public-keys for
> > authentication which are limited to running the "svnserve -t" command.
> > Which means I can drastically limit who gets command line access to the
> > server and I don't worry as much about private keys that don't have
> > passwords.  We even have our web server pushing their log files to
> > individual SVN repositories (one per server for security) using public
> > key authentication.
> >
> > The only downside of svn+ssh is that (at least for TortoiseSVN or maybe
> > it's a PLink issue) some client tools don't play well with using
> > alternate ports for the SSH tunnel.  So we were forced to pipe
> 22/tcp to
> > our internal SVN server instead of using an out of the way port
> like 28022.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: accessing svn through internet (svn+ssh)

Posted by Duncan Murdoch <mu...@stats.uwo.ca>.
On 11/16/2006 10:44 PM, Thomas Harold wrote:
> Duncan Murdoch wrote:
>> I've found it easier to set up svn+ssh access.  No server needed (except 
>> the sshd server, of course, but it was running for other reasons).
>>
> 
> I prefer the svn+ssh method as well... not sure how well it would work 
> with a Windows host though.  I guess one could use Cygwin's SSHD?

I do use Cygwin's sshd for other things, and it works fine.  However, I 
don't have any svn repositories on Windows machines so I can't say for 
sure that would work:  I just can't think of any reason why it wouldn't.

Duncan Murdoch
> 
> (We waited until we could install some Linux servers before migrating 
> away from SOS+VSS.)
> 
> The nicest part about the svn+ssh method is the use of public-keys for 
> authentication which are limited to running the "svnserve -t" command. 
> Which means I can drastically limit who gets command line access to the 
> server and I don't worry as much about private keys that don't have 
> passwords.  We even have our web server pushing their log files to 
> individual SVN repositories (one per server for security) using public 
> key authentication.
> 
> The only downside of svn+ssh is that (at least for TortoiseSVN or maybe 
> it's a PLink issue) some client tools don't play well with using 
> alternate ports for the SSH tunnel.  So we were forced to pipe 22/tcp to 
> our internal SVN server instead of using an out of the way port like 28022.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: accessing svn through internet (svn+ssh)

Posted by Thomas Harold <tg...@tgharold.com>.
Duncan Murdoch wrote:
> 
> I've found it easier to set up svn+ssh access.  No server needed (except 
> the sshd server, of course, but it was running for other reasons).
> 

I prefer the svn+ssh method as well... not sure how well it would work 
with a Windows host though.  I guess one could use Cygwin's SSHD?

(We waited until we could install some Linux servers before migrating 
away from SOS+VSS.)

The nicest part about the svn+ssh method is the use of public-keys for 
authentication which are limited to running the "svnserve -t" command. 
Which means I can drastically limit who gets command line access to the 
server and I don't worry as much about private keys that don't have 
passwords.  We even have our web server pushing their log files to 
individual SVN repositories (one per server for security) using public 
key authentication.

The only downside of svn+ssh is that (at least for TortoiseSVN or maybe 
it's a PLink issue) some client tools don't play well with using 
alternate ports for the SSH tunnel.  So we were forced to pipe 22/tcp to 
our internal SVN server instead of using an out of the way port like 28022.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: accessing svn through internet

Posted by Duncan Murdoch <mu...@stats.uwo.ca>.
On 11/16/2006 6:51 PM, Ryan Schmidt wrote:
> On Nov 16, 2006, at 16:03, Érico wrote:
> 
>> I'm using svn in my office network and everything is fine
>>
>> I would like to access svn from home
>>
>> Searching for documentation on the web I configured permission in  
>> my firewall to access port 3690
>>
>> so i tried : svn://myhost:3690 or  svn://myhost_ip:3690 and wasn't  
>> able to connect to my server
>>
>> I'm searching in documentation how to configure this feature
>>
>> Does any one can give me some help about this
> 
> Are you running svnserve?
> 
> You need to be, if you expect to be able to access the repository  
> over the svn:// protocol.
> 
> The book explains how to set up svnserve, or the Apache server, which  
> is another option.
> 
> http://svnbook.red-bean.com/en/1.2/svn.serverconfig.html

I've found it easier to set up svn+ssh access.  No server needed (except 
the sshd server, of course, but it was running for other reasons).

Duncan Murdoch

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: accessing svn through internet

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 16, 2006, at 16:03, Érico wrote:

> I'm using svn in my office network and everything is fine
>
> I would like to access svn from home
>
> Searching for documentation on the web I configured permission in  
> my firewall to access port 3690
>
> so i tried : svn://myhost:3690 or  svn://myhost_ip:3690 and wasn't  
> able to connect to my server
>
> I'm searching in documentation how to configure this feature
>
> Does any one can give me some help about this

Are you running svnserve?

You need to be, if you expect to be able to access the repository  
over the svn:// protocol.

The book explains how to set up svnserve, or the Apache server, which  
is another option.

http://svnbook.red-bean.com/en/1.2/svn.serverconfig.html



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org