Thank you all for your help. I have solved the problem and would like to
share it with you. Might help somebody else.
1. The ip adress of the server over vpn is 10.8.0.1 - not .6 That would
be the client
2. On the susefirewall I had to add svnserve as a service allowed
3. the --listen directive seems not to have an influence on my goals
3. The cisco firewall stays blocked for subversion. Only allow vpn.
Result: svn is now available exclusivly over VPN-tunnel!
Thank you all for your help.
Stefan Sperling wrote:
> On Wed, Mar 18, 2009 at 01:59:33PM +0100, Merlin Morgenstern wrote:
>> Hi there,
>> I am trying to get svn running over a vpn tunnel. Unvortunatelly there
>> seems to be something I am missing. The tunnel is up an running, ping
>> works. Subversion is set up and running as stand alone version.
>> After I do a checkout:
>> Subversion answers:
>> Checkout from svn://10.8.0.6/test, revision HEAD, Fully recursive,
>> Externals included Can't connect to host '10.8.0.6': Es konnte keine
>> Verbindung hergestellt
>> werden, da der Zielcomputer die Verbindung verweigerte.
> Please report error messages in English, not everyone here understands
> $ export LANG=en_US
> $ svn checkout ...
> (FYI the error is essentially saying "connection refused").
>> Do I have to configure subversion somehow to listen to that port 1149
>> of vpn and the ip adress?
> svnserve can only listen on a single interface/port.
> You should not need to specify a port.
> If you need access to the svn repository via multiple
> IP addresses at the same time, use apache instead of svnserve.
> But did you try connecting to the IP address that svnserve normally
> listens on? Given that routing is set up appropriately on your client box,
> it should try to connect to that IP through the VPN tunnel.
> This is the most appropriate solution since VPNs are supposed to be
> transparent to applications. Whether or not your computer sends packets
> to some destination through the VPN tunnel is none of Subversion's business.
> You didn't say what operating system your client is running and what kind
> of VPN software you are using, so it's hard to give more concrete advice.
> Or you can try: svnserve --listen-host 10.8.0.6
> But this would mean that everyone else using the server will have
> to switch to that IP, too, and it must be reachable by them, so it
> may not be ideal.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-18 18:26:20 CET