[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: void pointer <rcdailey_at_gmail.com>
Date: Wed, 14 Jan 2009 09:31:08 -0600

On Tue, Jan 13, 2009 at 5:31 PM, Nick Hasser <nick.hasser_at_gmail.com> wrote:
> 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 (port 3691 of you server).
> Your /etc/xinetd.d/svn would look like:
> <snip>
> 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.

I'm not sure how to add a second IP to the server, nor am I sure if doing so
would work. My understanding of LAN networking is that you have your LAN IP
which is used to give other network clients access to that machine. I'm not
sure how having 2 LAN IP's would affect this. Would my router have to issue
2 IP's to my linux machine? How does this work?

Also, the port forwarding idea is great and I"m going to do that for now. I
can't believe I didn't think of this earlier! Thanks a lot!
Received on 2009-01-14 16:32:12 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.