[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Question about xinetd & svn

From: Nick Hasser <nick.hasser_at_gmail.com>
Date: Tue, 13 Jan 2009 18:31:43 -0500

Robert Dailey wrote:
> On Mon, Jan 12, 2009 at 9:16 PM, Nick Hasser <nick.hasser_at_gmail.com> wrote:
>
> Thanks for your help. I am on a router so I only have 1 IP address and that
> is the one on my LAN. WAN traffic is forwarded to my LAN IP address by my
> router. Looks like I'll just have to stick with different ports. This isn't
> terrible, but I was wanting to avoid it so I didn't have to explicitly type
> the port portion of the URL in SVN (It would just use the default).

I don't know how much control you have of the forwarding on your router.

My preferred solution would be to add a second IP to your server, as
Allen suggested.

Another option might be to forward packets arriving at the router on the
standard port to a non-standard port on your server and run your
external svn config (assuming it is /etc/xinetd.d/svn) on that
non-standard port. So, you would redirect packets arriving on port 3690
on your router to 192.168.10.150:3691 (port 3691 of you server).

Your /etc/xinetd.d/svn would look like:

service svn
{
        socket_type = stream
        port = 3691
        bind = 192.168.10.150
        user = svn
        group = svn_group
        server = /usr/bin/svnserve
        server_args = -i -r /srv/svn/repo
        log_on_failure += USERID
        disable = no
}

And /etc/xinetd.d/svn_group would look like:

service svn
{
        socket_type = stream
        port = 3690
        bind = 192.168.10.150
        user = svn
        group = svn_group
        server = /usr/bin/svnserve
        server_args = -i -r /srv/svn/repo
        log_on_failure += USERID
        disable = no
}

This would allow you to keep your internal clients using the standard
port. Your external clients would also use the standard port, which
would then get redirected automatically to port 3691 by your router.
That way, neither group would have to specify the port in the URL.

The all relies on the ability of your router to support forwarding to a
different port.

> Thanks again for the help.
>

No problem. I'm not good at writing code, but I do try to share what I
can when I think I know something.

Nick

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1023131

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-14 14:12:47 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.